fsck during system boot fails with separate /boot partition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

We've had an installation report [1] for Debian Etch where a user set up a 
separate /boot partition. The first boot into the new system failed because 
the fsck on the /boot partition failed:
  Checking file systems...fsck 1.40-WIP (14-Nov-2006)
  /dev/dasda1 is mounted.  e2fsck: Cannot continue, aborting.

However, neither 'mount' or /proc/mounts show the /dev/dasda1 partition as 
mounted.

I've reproduced the issue and my suspicion is that either the boot loader or 
the kernel is failing to release /dev/dasda1 after the kernel and/or initrd 
have been loaded which leads to fsck concluding that it is mounted.

Cheers,
Frans Pop

Attachment: signature.asc
Description: This is a digitally signed message part.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux