Martin Michlmayr schrieb:
Eeek. I installed the new image, changed the /boot/vmlinux symlink and rebooted to see if it works. Well, it did work. Before doing anything on the newly installed kernel, I figured I should do a back up of my data on the external disk... While copying the data (>3 GByte) over the network (2.4 kernel), however, I received the same errors I got on the 2.6 kernel (from dmesg):Can you please install linux-image-2.6.16-rc5-r5k-cobalt and check if this problem is still there.
---snip---usb.c: USB device 2 (vend/prod 0x59f/0x621) is not claimed by any active driver.
SCSI subsystem driver Revision: 1.00 Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage scsi0 : SCSI emulation for USB Mass Storage devices Vendor: SEAGATE Model: ST3250823A Rev: 3.03 Type: Direct-Access ANSI SCSI revision: 02 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 USB Mass Storage support registered. uhci.c: USB Universal Host Controller Interface driver v1.1 uhci.c: found UHCI device with no IRQ assigned. check BIOS settings! eth0: Setting full-duplex based on MII#1 link partner capability of 45e1. Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) /dev/scsi/host0/bus0/target0/lun0: p1 kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067064 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067072 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067080 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067088 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067096 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067104 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067112 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067120 SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000 I/O error: dev 08:01, sector 228067128 usb.c: USB disconnect on device 00:0a.2-1 address 2 Device 08:01 not ready. I/O error: dev 08:01, sector 228067136 Device 08:01 not ready. I/O error: dev 08:01, sector 228067312 Device 08:01 not ready. I/O error: dev 08:01, sector 228067064 Device 08:01 not ready. I/O error: dev 08:01, sector 228067320 Device 08:01 not ready. I/O error: dev 08:01, sector 228067568 Device 08:01 not ready. I/O error: dev 08:01, sector 228067064 ---snap--- The most interesting part, obviously, is"WARNING: USB Mass Storage data integrity not assured"... I wonder why uhci was used in the first place? Given that it's a USB2 controller and a USB2 device? According to modprobe, ehci was loaded... as always. So just to be on the safe side, keeping an eye on reproducibility... What should I do next? Just give the 2.6 a try, reformat the drive and see if the error is gone or what? Regarding the data, the loss of data means a little bit of work, but it's not like I'm storing essential data on testing device.
By the way, e2fsck on 2.6 returned (dmesg): ---snip--- Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices usbcore: registered new driver usb-storage USB Mass Storage support registered. usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning Vendor: SEAGATE Model: ST3250823A Rev: 3.03 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 53 00 00 08 sda: assuming drive cache: write through SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 53 00 00 08 sda: assuming drive cache: write through sda: sda1 sd 0:0:0:0: Attached scsi disk sda usb-storage: device scan completeEXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2
kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. usb 3-1: reset high speed USB device using ehci_hcd and address 4 usb 3-1: device not accepting address 4, error -145 usb 3-1: USB disconnect, address 4 sd 0:0:0:0: scsi: Device offlined - not ready after error recovery sd 0:0:0:0: SCSI error: return code = 0x10000 end_request: I/O error, dev sda, sector 444334223 Buffer I/O error on device sda1, logical block 222167080 sd 0:0:0:0: rejecting I/O to device being removed Buffer I/O error on device sda1, logical block 222167081 Buffer I/O error on device sda1, logical block 222167082 Buffer I/O error on device sda1, logical block 222167083 Buffer I/O error on device sda1, logical block 222167084 Buffer I/O error on device sda1, logical block 222167085 Buffer I/O error on device sda1, logical block 222167086 Buffer I/O error on device sda1, logical block 222167087 Buffer I/O error on device sda1, logical block 222167088 Buffer I/O error on device sda1, logical block 222167089 sd 0:0:0:0: rejecting I/O to device being removed usb 3-1: new high speed USB device using ehci_hcd and address 5 0:0:0:0: rejecting I/O to dead device 0:0:0:0: rejecting I/O to dead device usb 3-1: device not accepting address 5, error -145 usb 3-1: new high speed USB device using ehci_hcd and address 7 usb 3-1: device not accepting address 7, error -145 usb 3-1: new high speed USB device using ehci_hcd and address 9 usb 3-1: device not accepting address 9, error -145 usb 3-1: new high speed USB device using ehci_hcd and address 11 usb 3-1: device not accepting address 11, error -145 usb 3-1: new high speed USB device using ehci_hcd and address 13 ---snap---Could reformatting the drive on 2.6 fix that? Or is my drive physically wrecked? I don't mind swapping data around and doing all that, as long as it is of any help for you guys... So... just tell me what to do next :-)
Thanks, Daniel
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature