Khalid Aziz wrote, on 07/05/10 02:58:
On Thu, 2010-05-06 at 16:19 +0930, Arthur Marsh wrote:
After a full shut-down and reboot to the kde desktop, I found that my
/boot file-system was not mounted, despite being listed in /etc/fstab:
UUID=bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea /boot ext3 defaults
0 2
(all on one line).
I was able to mount /boot manually:
# mount /boot
# mount|grep boot
/dev/sda1 on /boot type ext3 (rw)
# blkid /dev/sda1
/dev/sda1: UUID="bfdeb6d6-0b77-4beb-a63d-bdc3e455b8ea" SEC_TYPE="ext2"
TYPE="ext3"
So it appears that the problem reported against kexec might actually be
a problem like /boot failing to mount at start-up or being un-mounted
for unknown reasons.
Arthur.
/boot failing to mount does not sound good. Did you happen to see any
error messages from mountall.sh at any time at startup?
No I didn't. I've added a -v (verbose) to the mount command in
/etc/init.d/mountall.sh
and defined VERBOSE="yes" in
/etc/init.d/umountfs
to make clear what file systems are being mounted at start-up and
un-mounted at shut-down, and will try to observe what appears on the
console at start-up and shut-down.
I'm wondering what if anything besides a corrupt /boot file-system could
cause a mount failure of /boot at start-up?
Aside from kexec, installation and upgrading of a kernel and/or
initramfs could be fouled up by /boot not being mounted when /boot
should be mounted.
Arthur.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
