[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: fsck failure at boot
- From: Jason Dixon <jason dixongroup net>
- To: ttsig tuxyturvy com
- Cc: "Red Hat Enterprise Linux 4 \(Nahant\) Discussion List" <nahant-list redhat com>
- Subject: Re: fsck failure at boot
- Date: Fri, 21 Apr 2006 18:31:32 -0400
On Apr 21, 2006, at 5:21 PM, Tom Sightler wrote:
The firmware looks pretty old in your Qlogic adapter, that might be a
possibility, but I doubt it.
As do I, since the LUN behaves normally outside of this issue.
We have quite a few RHEL4 systems using Qlogic 2340 adapters to
talk to
Xserve RAID systems and haven't seen anything like this at all
although
I'll admit that we use the with LVM, not simple partitions.
I just reread your first message and it actually looks like the system
is getting to the "fsck" before udev has a chance to actually make the
device node, did you rebuild your initrd after adding the Qlogic
device?
If the device is not getting loaded during the initrd process, but
rather during the "Initializing Hardware..." phase then I could see
how
that's possible.
I would normally only think this is necessary when dealing with the
root filesystem, but I see your point. I might try that on Monday.
Another possible workaround would be to simply tell the system not to
attempt to fsck that drive by changing your fstab to:
/dev/sdb1 /san ext3 defaults 1 0
This is what I'll leave it as until I can find the real cause.
Thanks,
--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]