[EMAIL PROTECTED] wrote on 08.10.2007 12:32:50:
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.
Judging from the data
On Monday 08 October 2007, Peter 1 Oberparleiter wrote:
Judging from the data found in the bugtracker, this sounds more like a
setup problem:
That was my initial thought as well. However, I could reproduce the issue
without any problems during a new installation in Hercules.
I got exactly the
On Monday 08 October 2007, Peter 1 Oberparleiter wrote:
This might indicate a timing problem - the init script tries to mount a
DASD that has not yet been fully initialized by the kernel (the return
code -EBUSY that triggers the already mounted message may indicate
different problems). Try to
On Oct 8, 2007, at 10:12 AM, Frans Pop wrote:
Adding the dasd= boot parameter did not help - it seems to be
ignored in our
initrds; changing /etc/fstab to use /dev/disk/by-path devices
consistently
does result in a correct boot.
I'll consult with other Debian people how we want to resolve
4 matches
Mail list logo
