Bug 124694
Summary: | cannot boot with firewire drive defined in /etc/fstab with kernel > 2.6.6-1.379 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Graydon Saunders <oak> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.8-1.541 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-10-26 09:21:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Graydon Saunders
2004-05-28 15:30:47 UTC
With kernel-2.6.6-1.403 (also kernel-2.6.6-1.391), it's not having the firewire partition defined in /etc/fstab which is doing me in, it's having the firewire enclosure *connected*. (the definition in /etc/fstab then does me in because the boot sequence can't find the device and drops me into the repair shell.) With the enclosure connected and powered on, the boot sequence gets to 'mounting the root filesystem in read/write' mode and hangs. Similarly, 'shutdown now -r" gets to 'umounting filesystems' and hangs. Power it off, and the boot sequence proceeds normally. Power it back on after the machine has finished booting, and after May 30 22:23:17 grithr ieee1394.agent[3106]: ... no drivers for IEEE1394 product 0x/0x/0x May 30 22:23:17 grithr ieee1394.agent[3092]: ... no drivers for IEEE1394 product 0x/0x/0x May 30 22:23:17 grithr kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices May 30 22:23:18 grithr kernel: ieee1394: sbp2: Logged into SBP-2 device May 30 22:23:18 grithr kernel: Vendor: WDC WD80 Model: 0JB-00ETA0 Rev: May 30 22:23:18 grithr kernel: Type: Direct-Access ANSI SCSI revision: 06 May 30 22:23:18 grithr kernel: SCSI device sdb: 268435455 512-byte hdwr sectors (137439 MB) May 30 22:23:18 grithr kernel: sdb: asking for cache data failed May 30 22:23:18 grithr kernel: sdb: assuming drive cache: write through May 30 22:23:18 grithr kernel: sdb:SCSI error : <1 0 0 0> return code = 0x8000002 May 30 22:23:18 grithr kernel: Current sdb: sense key Aborted Command May 30 22:23:18 grithr kernel: end_request: I/O error, dev sdb, sector 268435448 May 30 22:23:18 grithr kernel: Buffer I/O error on device sdb, logical block 268435448 with the I/O errors repeating for that same logical block. I get an entirely live and sensible firewire external drive; e2fsck -f /dev/sdb1 gives the drive a clean bill of health, despite the buffer I/O errors. I'm not getting any log messages from the hang events, but the box will sit there for fifteen minutes without doing anything, not even blinking lights, until manually reset or powered off. any luck with the errata kernel ? Whups! I didn't keep proper track, but by kernel-2.6.8-1.541 this is certainly ok. (And it's still ok in kernel-2.6.9-1.640.) |