Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDebian-8 /home not mounted resulting in no display :0 #3398
Comments
niccokunzmann
changed the title from
Debian-8 /home mount issue
to
Debian-8 /home not mounted resulting in no display :0
Dec 14, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
unman
Dec 14, 2017
Member
Interesting, I've not seen this.
Have you made any changes to the template? If so, if you change back to the vanilla debian-8 template, does the appVM start with mounted /home then?
If you create a new appVM based on the same template does it show the same behaviour?
Is there anything relevant in the logs? Particularly relating to mount-dirs.sh?
|
Interesting, I've not seen this. Is there anything relevant in the logs? Particularly relating to mount-dirs.sh? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
niccokunzmann
Dec 14, 2017
Contributor
Have you made any changes to the template?
Yes, I have. I installed some software and added new users in the
template vm.
If so, if you change back to the vanilla debian-8 template, does the
appVM start with mounted /home then?
Yes, it should.
If you create a new appVM based on the same template does it show the
same behaviour?
If I create a new app vm with a plain private storage, everything seems
to work fine. So, no not the same behavior.
Is there anything relevant in the logs? Particularly relating to
mount-dirs.sh?
Where can I see the logs?
|
Have you made any changes to the template?
Yes, I have. I installed some software and added new users in the
template vm.
If so, if you change back to the vanilla debian-8 template, does the
appVM start with mounted /home then?
Yes, it should.
If you create a new appVM based on the same template does it show the
same behaviour?
If I create a new app vm with a plain private storage, everything seems
to work fine. So, no not the same behavior.
Is there anything relevant in the logs? Particularly relating to
mount-dirs.sh?
Where can I see the logs?
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
unman
Dec 14, 2017
Member
If so, if you change back to the vanilla debian-8 template, does the
appVM start with mounted /home then?
Yes, it should.
Yes, but does it?
Where can I see the logs?
journalctl -b
Yes, but does it?
|
andrewdavidwong
added
bug
C: Debian
labels
Dec 15, 2017
andrewdavidwong
added this to the Release 3.2 updates milestone
Dec 15, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
niccokunzmann
Dec 23, 2017
Contributor
The solution for me is to put these commands in /etc/rc.local, since this is executed after mount:
mount /home
systemctl restart qubes-gui-agent.service
So, we can close the issue from my side.
|
The solution for me is to put these commands in /etc/rc.local, since this is executed after mount: So, we can close the issue from my side. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
niccokunzmann
Dec 23, 2017
Contributor
Here are logs:
user@my-new-vm-test:~$ sudo journalctl -b | grep mount
Dec 23 09:44:56 localhost kernel: EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
Dec 23 09:44:56 localhost kernel: EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
Dec 23 09:44:56 localhost kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Dec 23 09:44:56 localhost kernel: EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem
Dec 23 09:44:56 localhost kernel: EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null)
Dec 23 09:44:56 localhost systemd[1]: Starting Initialize and mount /rw and /home...
Dec 23 09:44:56 localhost mount-dirs.sh[321]: Private device management: checking /dev/xvdb
Dec 23 09:44:56 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
Dec 23 09:44:58 localhost kernel: EXT4-fs (dm-0): re-mounted. Opts: (null)
Dec 23 09:44:58 localhost systemd[1]: Started Remount Root and Kernel File Systems.
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Private device management: fsck.ext4 of /dev/xvdb succeeded
Dec 23 09:44:59 localhost kernel: EXT4-fs (xvdb): mounted filesystem with ordered data mode. Opts: discard
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Checking /rw
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Private device size management: enlarging /dev/xvdb
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Private device size management: resize2fs of /dev/xvdb succeeded
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Finished checking /rw
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Mounting /rw/home onto /home
Dec 23 09:44:59 localhost mount-dirs.sh[321]: Initializing /rw/bind-dirs with files from /var/spool/cron
Dec 23 09:45:00 localhost mount-dirs.sh[321]: Bind mounting /rw/bind-dirs/var/spool/cron onto /var/spool/cron
Dec 23 09:45:00 localhost systemd[1]: Started Initialize and mount /rw and /home.
user@personal-3:~$ sudo journalctl -b | grep mount
Dec 23 09:41:19 localhost kernel: EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
Dec 23 09:41:19 localhost kernel: EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
Dec 23 09:41:19 localhost kernel: EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Dec 23 09:41:19 localhost kernel: EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem
Dec 23 09:41:19 localhost kernel: EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null)
Dec 23 09:41:21 localhost systemd[1]: Starting Initialize and mount /rw and /home...
Dec 23 09:41:21 localhost mount-dirs.sh[335]: Private device management: checking /dev/xvdb
Dec 23 09:41:21 localhost mount-dirs.sh[335]: Private device management: fsck.ext4 of /dev/xvdb succeeded
Dec 23 09:41:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
Dec 23 09:41:21 localhost kernel: EXT4-fs (dm-0): re-mounted. Opts: (null)
Dec 23 09:41:21 localhost systemd[1]: Started Remount Root and Kernel File Systems.
Dec 23 09:41:21 localhost kernel: EXT4-fs (xvdb): mounted filesystem with ordered data mode. Opts: discard
Dec 23 09:41:22 localhost mount-dirs.sh[335]: Checking /rw
Dec 23 09:41:22 localhost mount-dirs.sh[335]: Private device size management: enlarging /dev/xvdb
Dec 23 09:41:22 localhost mount-dirs.sh[335]: Private device size management: resize2fs of /dev/xvdb succeeded
Dec 23 09:41:22 localhost mount-dirs.sh[335]: Finished checking /rw
Dec 23 09:41:22 localhost mount-dirs.sh[335]: initialize_home: adjusting groupship on /rw/home/firefox to 1001
Dec 23 09:41:30 localhost mount-dirs.sh[335]: chgrp: cannot dereference ‘/rw/home/firefox/Desktop/Link to Downloads’: No such file or directory
Dec 23 09:41:30 localhost mount-dirs.sh[335]: chgrp: cannot dereference ‘/rw/home/firefox/.config/pulse/ee823d6681314a808e7249a5de64fdc9-runtime’: No such file or directory
Dec 23 09:41:30 localhost systemd[1]: qubes-mount-dirs.service: main process exited, code=exited, status=123/n/a
Dec 23 09:41:30 localhost systemd[1]: Failed to start Initialize and mount /rw and /home.
Dec 23 09:41:30 localhost systemd[1]: Unit qubes-mount-dirs.service entered failed state.
I created new users within the vm and gave them a home directory.
It seems that caused a problem. We can now assume that this error will not occur for other people except they create an other user with a new home directory.
Thus, I conclude: We can close the issue from my side. I am satisfied and found a solution.
If you think, it should be kept open, please re-open it or comment.
Should it only do chgrp to /home/user?
niccokunzmann
commented
Dec 23, 2017
•
edited
Edited 5 times
-
niccokunzmann
edited Dec 23, 2017 (most recent)
-
niccokunzmann
edited
Dec 23, 2017
-
niccokunzmann
edited
Dec 23, 2017
-
niccokunzmann
edited
Dec 23, 2017
-
niccokunzmann
edited
Dec 23, 2017
edited
Edited 5 times
-
Dec 23, 2017 (most recent) -
Dec 23, 2017 -
Dec 23, 2017 -
Dec 23, 2017 -
Dec 23, 2017
|
Here are logs: I created new users within the vm and gave them a home directory. Thus, I conclude: We can close the issue from my side. I am satisfied and found a solution. Should it only do chgrp to /home/user? |
niccokunzmann
closed this
Dec 23, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
niccokunzmann commentedDec 14, 2017
•
edited
Edited 2 times
-
niccokunzmann
edited Dec 14, 2017 (most recent)
-
niccokunzmann
edited Dec 14, 2017
Qubes OS version: R3.2
Affected TemplateVMs:
debian-8 but this only affects my app VM and not the corresponding template.
Steps to reproduce the behavior:
I start a debian-8 app vm "personal-3" .
Then, I try to open a program.
Resulting in
Also,
shows an empty home directory
Expected behavior:
Actual behavior:
When I type
I can see
I log in as user without password. And run:
This is the service producing the failure message.
I note that:
/rwhas successfully been mounted. Among other folders, it contains the/homefolder./homehas not been mounted. It is empty.General notes:
To fix this problem, I can do two things:
/homeusingsudo mount /home- it was prepared before and the command works to populate/homesudo systemctl restart qubes-gui-agent.serviceNow,
/homeis mounted and I can open programs like firefox and xterm.Related issues: