Public bug reported: Binary package hint: mountall
I'm remotely co-administering a laptop (a Fujitsu-Siemens Esprimo U9200) running Karmic, upgraded from Jaunty. The setup for the sole hard drive in the machine has a separate partition for the owner's home directory. A couple of times since the upgrade, the machine has failed to mount the user's home directory partition, resulting in seemingly reset settings of Gnome and everything else normally saved on that partition. On the next boot, or the one after that, the mounting again works, but apparently some of the automatically re-created settings under the home directory now interfere with the user's actual settings (i.e. those he has created himself), resulting in further complications. We've fixed this a couple of times now by removing the re-created settings, and recreating a blank home directory for mounting the separate partition to, but this is just a laborious work-around, needless to say. Mounting the directory at boot should Just Work. I have yet to configure ssh access for myself on the machine, so I'm not providing hard data (such as fstab or lspci listings) in this initial report, but I hope to be able to soon, and will update the report once I have more insight into what's actually going on during the boot. There are other obstacles as well, such as the recovery menu failing (have to resort to REISUB), and the usual removing of 'quiet' and 'splash' boot parameters not helping in seeing the boot messages ('splash' isn't even there, so don't know how to disable it, and so the messages flash by too quickly to see). Of the possible duplicates suggested by Launchpad, #447649 seemed most likely. There are a couple of sshfs mount points inside the user's home directory, mounted by a script run from under /etc/network/if-up.d/. #447649 soon gets a bit too technical for my understanding however, and it's marked as being fixed anyway, so in theory it shouldn't affect this issue. As I said, I'll be updating this as I find out more, but I figured I might as well report what's known so far, so if there's some insight on the issue as such already, it'll get posted here too. And as I'll gain the ssh access, I'll be happy to provide any data requested. Feel free to suggest what's useful. Oh, and the choice of 'mountall' for reporting this against was just a wild guess, since I truly have no clue of the real culprit yet. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu-boot -- Mounting home directory fails upon boot https://bugs.launchpad.net/bugs/481190 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs