[Bug 471382] External USB disk (reiserfs) gets corrupted and becomes read-only.

https://bugzilla.novell.com/show_bug.cgi?id=471382 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=471382#c7 --- Comment #7 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-25 17:56:35 MST --- *** It is a software issue. *** I'm attempting to use the disk tonight, in 11.1, following the procedure of plugin the USB cable after powering up the device. After mounting two partition I noticed this message in the log: Feb 25 23:40:32 nimrodel kernel: REISERFS (device dm-4): Using r5 hash to sort names Feb 25 23:40:52 nimrodel kernel: sd 0:0:0:0: [sda] Sense Key : No Sense [current] Feb 25 23:40:52 nimrodel kernel: Info fld=0x0 Feb 25 23:40:52 nimrodel kernel: sd 0:0:0:0: [sda] Add. Sense: No additional sense information Feb 25 23:40:56 nimrodel kernel: sd 0:0:0:0: [sda] Sense Key : No Sense [current] Feb 25 23:40:56 nimrodel kernel: Info fld=0x0 So I umounted, unplugged, replugged, several times. The message came up again, fast: Feb 25 23:59:33 nimrodel kernel: sda: sda1 sda2 sda3 sda4 Feb 25 23:59:33 nimrodel kernel: sd 1:0:0:0: [sda] Attached SCSI disk Feb 25 23:59:33 nimrodel kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Feb 25 23:59:33 nimrodel kernel: usb-storage: device scan complete Feb 25 23:59:36 nimrodel kernel: sd 1:0:0:0: [sda] Sense Key : No Sense [current] Feb 25 23:59:36 nimrodel kernel: Info fld=0x0 Feb 25 23:59:36 nimrodel kernel: sd 1:0:0:0: [sda] Add. Sense: No additional sense information Feb 25 23:59:44 nimrodel kernel: usb 1-3: USB disconnect, address 5 Feb 25 23:59:44 nimrodel kernel: usb 1-3.4: USB disconnect, address 6 At one point the USB bus locked and the disk was not detected: Feb 26 00:03:59 nimrodel kernel: usb 1-3: new high speed USB device using ehci_hcd and address 7 Feb 26 00:03:59 nimrodel kernel: usb 1-3: configuration #1 chosen from 1 choice Feb 26 00:03:59 nimrodel kernel: hub 1-3:1.0: USB hub found Feb 26 00:03:59 nimrodel kernel: hub 1-3:1.0: 4 ports detected Feb 26 00:03:59 nimrodel kernel: usb 1-3: New USB device found, idVendor=0424, idProduct=2504 Feb 26 00:03:59 nimrodel kernel: usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 So I had to plug into another port, and this time it worked, with no error message. And finally, to try if the previous port was broken, I connected another usb device, which seemed to work fine. Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: new high speed USB device using ehci_hcd and address 11 Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: configuration #1 chosen from 1 choice Feb 26 00:07:03 nimrodel kernel: scsi3 : SCSI emulation for USB Mass Storage devices Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: New USB device found, idVendor=13fd, idProduct=1650 Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: Product: ST3320620AS Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: Manufacturer: Initio Feb 26 00:07:03 nimrodel kernel: usb 1-4.4: SerialNumber: 0010101650000DDEW Feb 26 00:07:03 nimrodel kernel: usb-storage: device found at 11 Feb 26 00:07:03 nimrodel kernel: usb-storage: waiting for device to settle before scanning Feb 26 00:07:04 nimrodel kernel: scsi 3:0:0:0: Direct-Access Initio ST3320620AS 4.36 PQ: 0 ANSI: 0 Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Write Protect is off Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Mode Sense: 00 00 00 00 Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Assuming drive cache: write through Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] 625142448 512-byte hardware sectors (320073 MB) Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Write Protect is off Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Mode Sense: 00 00 00 00 Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Assuming drive cache: write through Feb 26 00:07:04 nimrodel kernel: sda: sda1 sda2 sda3 sda4 Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: [sda] Attached SCSI disk Feb 26 00:07:04 nimrodel kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0 Feb 26 00:07:04 nimrodel kernel: usb-storage: device scan complete Feb 26 00:09:54 nimrodel kernel: usb 1-3: USB disconnect, address 7 Feb 26 00:09:54 nimrodel kernel: hub 1-0:1.0: unable to enumerate USB device on port 3 Feb 26 00:09:54 nimrodel kernel: usb 5-1: new full speed USB device using uhci_hcd and address 2 Feb 26 00:09:54 nimrodel kernel: usb 5-1: configuration #1 chosen from 1 choice Feb 26 00:09:54 nimrodel kernel: usb 5-1: New USB device found, idVendor=067b, idProduct=2303 Feb 26 00:09:54 nimrodel kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 26 00:09:54 nimrodel kernel: usb 5-1: Product: USB-Serial Controller C Feb 26 00:09:54 nimrodel kernel: usb 5-1: Manufacturer: Prolific Technology Inc. Feb 26 00:09:54 nimrodel kernel: usbcore: registered new interface driver usbserial Feb 26 00:09:54 nimrodel kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for generic Feb 26 00:09:54 nimrodel kernel: usbcore: registered new interface driver usbserial_generic Feb 26 00:09:54 nimrodel kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core Feb 26 00:09:54 nimrodel kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303 Feb 26 00:09:54 nimrodel kernel: pl2303 5-1:1.0: pl2303 converter detected Feb 26 00:09:54 nimrodel kernel: usb 5-1: pl2303 converter now attached to ttyUSB0 Feb 26 00:09:54 nimrodel kernel: usbcore: registered new interface driver pl2303 Feb 26 00:09:54 nimrodel kernel: drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver Feb 26 00:10:00 nimrodel kernel: usb 5-1: USB disconnect, address 2 Feb 26 00:10:00 nimrodel kernel: pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 Feb 26 00:10:00 nimrodel kernel: pl2303 5-1:1.0: device disconnected So my previous hypothesis of the connection order being related to this problem, is doubtful. What I'll do from now on, is to watch the log for that error, and if it happens, I'll replug. [...] During the write operation, errors have appeared which will require an fsck - again :-/ Feb 26 01:21:13 nimrodel kernel: sd 3:0:0:0: [sda] Sense Key : No Sense [current] Feb 26 01:21:13 nimrodel kernel: Info fld=0x0 Feb 26 01:21:13 nimrodel kernel: sd 3:0:0:0: [sda] Add. Sense: No additional sense information Feb 26 01:21:13 nimrodel kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 46044 does not match to the expected one 1 Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-5150 search_by_key: invalid format found in block 19496961. Fsck? Feb 26 01:21:13 nimrodel kernel: REISERFS (device dm-4): Remounting filesystem read-only Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [321 485 0x0 SD] Feb 26 01:21:13 nimrodel kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 46044 does not match to the expected one 1 Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-5150 search_by_key: invalid format found in block 19496961. Fsck? Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [321 485 0x0 SD] Feb 26 01:21:13 nimrodel kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 46044 does not match to the expected one 1 Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-5150 search_by_key: invalid format found in block 19496961. Fsck? Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [321 485 0x0 SD] Feb 26 01:21:13 nimrodel kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 46044 does not match to the expected one 1 Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-5150 search_by_key: invalid format found in block 19496961. Fsck? Feb 26 01:21:13 nimrodel kernel: REISERFS error (device dm-4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [321 485 0x0 SD] Feb 26 01:27:29 nimrodel kernel: sd 3:0:0:0: [sda] Sense Key : No Sense [current] Feb 26 01:27:29 nimrodel kernel: Info fld=0x0 Feb 26 01:27:29 nimrodel kernel: sd 3:0:0:0: [sda] Add. Sense: No additional sense information There is no way to know if the error was provoked today, or previously; ie, by 11.0 or 11.1. We know nothing - except that the cable connection procedure is not related. It is a software issue :-/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.