# \[FAILED\] Failed to mount /. snapshots - “bullseye”
**URL:** https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449
**Category:** Uncategorized
**Created:** [February 22, 2021, 7:35pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449 "2021-02-22T19:35:51Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Peterc](https://discuss.freedombox.org/u/Peterc)
#### Post date: [February 22, 2021, 7:35pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/1 "2021-02-22T19:35:51Z")
Hello All and thank you !
I have just done a Debian testing “bullseye” install. The image that was down loaded was [Daily build: 2021-02-22 16:04 361M](https://cdimage.debian.org/images/daily-builds/daily/current/amd64/iso-cd/). The base install worked perfectly.
I did format the hard drive to: Btrfs on the install.
Then I installed the freedombox package:
```auto
sudo DEBIAN_FRONTEND=noninteractive apt install freedombox
```
Then I edited the interfaces file to:
```auto
auto lo
iface lo inet loopback
```
Then a reboot and the boot stops with the message:
```auto
[FAILED] Failed to mount /. snapshots
[DEPEND] Dependency failed for local file System.
You are in emergency mode.
```
It will not move post the message. I have done two installs and same problem !
Regards: peter
**Hardware:**
Laptop: LENOVO 0769ECG
Same again to day with:
2021-02-23
firmware-testing-amd64-netinst.iso
Update:
I log in at the: You are in emergency mode.
And # out the line for:
```auto
#UUID=eb9994cd-31cf-4c05-af9d-78554da15ee9 /.snapshots btrfs subvol=.snapshots 0 1
```
I can now get a full boot and get to freedombox setup page.
---
### Author:  [@Peterc](https://discuss.freedombox.org/u/Peterc)
#### Post date: [February 24, 2021, 1:59pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/2 "2021-02-24T13:59:33Z")
Hello all,
Below is a copy and paste from a grep snapper daemon.log
```auto
Feb 24 13:09:17 freedombox systemd[1]: Started Take snapper snapshot of root on boot.
Feb 24 13:09:17 freedombox systemd[1]: Starting Take snapper snapshot of root on boot...
Feb 24 13:09:17 freedombox dbus-daemon[373]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.24' (uid=0 pid=13485 comm="/usr/bin/snapper --config root create --cleanup-al")
Feb 24 13:09:17 freedombox systemd[1]: Starting DBus interface for snapper...
Feb 24 13:09:17 freedombox systemd[1]: Started DBus interface for snapper.
Feb 24 13:09:17 freedombox snapper[13485]: The config 'root' does not exist. Likely snapper is not configured.
Feb 24 13:09:17 freedombox snapper[13485]: See 'man snapper' for further instructions.
Feb 24 13:09:17 freedombox systemd[1]: snapper-boot.service: Main process exited, code=exited, status=1/FAILURE
Feb 24 13:09:17 freedombox systemd[1]: snapper-boot.service: Failed with result 'exit-code'.
Feb 24 13:09:17 freedombox systemd[1]: Failed to start Take snapper snapshot of root on boot.
Feb 24 13:09:17 freedombox systemd[1]: snapper-cleanup.service: Succeeded.
Feb 24 13:10:17 freedombox systemd[1]: snapperd.service: Succeeded.
Feb 24 13:12:55 freedombox dbus-daemon[373]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.38' (uid=0 pid=22918 comm="snapper list-configs ")
Feb 24 13:12:55 freedombox systemd[1]: Starting DBus interface for snapper...
Feb 24 13:12:55 freedombox systemd[1]: Started DBus interface for snapper.
```
These logs are from a new install. The .iso was down loaded with jigdo-lite:
```auto
firmware-testing-amd64-netinst.jigdo 2021-02-24
```
I think the lines below are of intrest ?
```auto
snapper-boot.service: Main process exited, code=exited, status=1/FAILURE
Feb 24 13:09:17 freedombox systemd[1]: snapper-boot.service: Failed with result 'exit-code'.
Feb 24 13:09:17 freedombox systemd[1]: Failed to start Take snapper snapshot of root on boot.
Feb 24 13:09:17 freedombox systemd[1]: snapper-cleanup.service: Succeeded.
```
This problem comes about after I installed freedombox.
Regards: peter
---
### Author:  [@Peterc](https://discuss.freedombox.org/u/Peterc)
#### Post date: [March 7, 2021, 6:17pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/3 "2021-03-07T18:17:30Z")
Hello All and thanks !!
It still the same issue and stated above. Today I did a apt install for testing and snapshot still stops the boot !
```auto
'Debian GNU/Linux testing "Bullseye" - Unofficial amd64 NETINST with firmware 20210306-20:51 (20210306)' (firmware-testing-amd64-netinst.iso)
```
The issue may because of the freeze on testing ?
Regards: peter
---
### Author:  [@Peterc](https://discuss.freedombox.org/u/Peterc)
#### Post date: [May 3, 2021, 4:06pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/4 "2021-05-03T16:06:37Z")
Hello All,
I just done a fresh install with the current version of Bullseye and again the same issue with snapshots is still there.
Freedombox was installed by:
```auto
sudo DEBIAN_FRONTEND=noninteractive apt install freedombox
```
Regards: peter
---
### Author:  [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)
#### Post date: [May 4, 2021, 1:06pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/5 "2021-05-04T13:06:19Z")
I am able to reproduce this issue in Virtualbox. I used the Bullseye RC1 installer at [https://cdimage.debian.org/images/bullseye\_di\_rc1/amd64/iso-cd/debian-bullseye-DI-rc1-amd64-netinst.iso](https://cdimage.debian.org/images/bullseye_di_rc1/amd64/iso-cd/debian-bullseye-DI-rc1-amd64-netinst.iso). During the Debian install, I changed the file system from ext4 to btrfs. Initial boot was fine, and installed freedombox package through the terminal. After rebooting, I get the error below, and do not get to the login prompt.
---
### Author:  [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)
#### Post date: [May 4, 2021, 2:15pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/6 "2021-05-04T14:15:52Z")
I rolled back to a (Virtualbox) snapshot before freedombox was installed. Here is more info about the system set up by Debian installer:
```auto
james@debian:~$ sudo btrfs filesystem show
Label: none uuid: 4b647c82-2690-4ef3-bdb3-b2dc363eef78
Total devices 1 FS bytes used 4.66GiB
devid 1 size 7.04GiB used 6.77GiB path /dev/sda1
```
```auto
james@debian:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=476796k,nr_inodes=119199,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=99992k,mode=755)
/dev/sda1 on / type btrfs (rw,relatime,space_cache,subvolid=256,subvol=/@rootfs)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=10648)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=99988k,nr_inodes=24997,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
```
```auto
james@debian:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
#
# / was on /dev/sda1 during installation
UUID=4b647c82-2690-4ef3-bdb3-b2dc363eef78 / btrfs defaults,subvol=@rootfs 0 0
# swap was on /dev/sda5 during installation
UUID=9020225d-8f34-4742-9332-bb590583518a none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
```
---
### Author:  [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)
#### Post date: [May 4, 2021, 2:42pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/7 "2021-05-04T14:42:52Z")
After installing freedombox package, /etc/fstab contains 2 entries for btrfs, with different subvolume names:
---
### Author:  [@jvalleroy](https://discuss.freedombox.org/u/jvalleroy)
#### Post date: [May 8, 2021, 3:17pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/8 "2021-05-08T15:17:48Z")
---
### Author:  [@fliu](https://discuss.freedombox.org/u/fliu)
#### Post date: [May 8, 2021, 9:53pm UTC](https://discuss.freedombox.org/t/failed-failed-to-mount-snapshots-bullseye/1449/9 "2021-05-08T21:53:39Z")
They found the cause of this in today’s Progress Call. Check out Issue [!2085](https://salsa.debian.org/freedombox-team/freedombox/-/issues/2085)