[Expired for mountall (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mountall (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, all
Hello, mr Scott (I figure you're the mantainer of mountall programm)
this bug is affecting me too NOW !
I did a fresh (may 15th) amd64 dist-upgrade from karmic to lucid on a HP
Pavillion dv 6000 notebook (intel core-duo, nvidia go 8300) and after reboot I
was not more able to boot
I tried this on clean Xubuntu 10.04 dekstop amd64, and couldnt replicate the
problem i have had. I tried all what i have had done with RC and it just boot
fine. xubuntu isnt entering maintrance mode and just mount all hdds I
connected,defined udev rule and added them to fstab.
Dont know if
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/45985767/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/45985768/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/45985769/Dependencies.txt
**
Seems that udev costum rule isnt attached. So here it is:
#lsidisk0
KERNEL==sd*[!0-9], ENV{ID_SERIAL_SHORT}==S1UYJ1CZ30XXX9,
SYMLINK+=disk/by-me/lsidisk0
KERNEL==sd*[0-9], ENV{ID_SERIAL_SHORT}==S1UYJ1CZ30XXX9,
SYMLINK+=disk/by-me/lsidisk0part%n
#lsidisk1
KERNEL==sd*[!0-9],
Could you modify /etc/init/mountall.conf, change the exec line, adding
--debug at the end. Uncomment those two lines in your /etc/fstab, and
reboot.
Let me know everything you see during boot; you should be given the
opportunity to skip the two filesystems, do so.
Then after booting attach
