mrmachine Posted August 5, 2011 Share Posted August 5, 2011 I haven't rebooted the machine yet. I've captured the syslog (attached). Anyone have any idea about this? Is my USB stick fried? I've only had it about 6 months. If I reboot, will I be able to recover anything off the USB stick? There were some script files I was working on there that I don't have a backup of. What can/should I do next? Here's an extract from the log, at the point where I think all the trouble started. Aug 5 20:26:35 unraid kernel: usb 1-6: USB disconnect, device number 2 Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: Device offlined - not ready after error recovery Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] Unhandled error code Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00 Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 55 58 b0 00 00 01 00 Aug 5 20:26:57 unraid kernel: end_request: I/O error, dev sda, sector 5593264 Aug 5 20:26:57 unraid kernel: Buffer I/O error on device sda1, logical block 5593216 Aug 5 20:26:57 unraid kernel: lost page write due to I/O error on sda1 Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] Unhandled error code Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00 Aug 5 20:26:57 unraid kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 31 00 00 01 00 Aug 5 20:26:57 unraid kernel: end_request: I/O error, dev sda, sector 49 Aug 5 20:26:57 unraid kernel: Buffer I/O error on device sda1, logical block 1 Aug 5 20:26:57 unraid kernel: lost page write due to I/O error on sda1 Aug 5 20:26:57 unraid kernel: FAT: FAT read failed (blocknr 694) Aug 5 20:26:57 unraid kernel: usb 1-6: new high speed USB device number 3 using ehci_hcd Aug 5 20:26:58 unraid kernel: scsi5 : usb-storage 1-6:1.0 Aug 5 20:26:59 unraid kernel: dib0700: tx buffer length is larger than 4. Not supported. Aug 5 20:26:59 unraid tvheadend[16618]: TS: DiBcom 7000PC/Network TEN: 219,500 kHz/TEN Digital: MPEG2VIDEO @ #512: Continuity counter error Aug 5 20:26:59 unraid kernel: scsi 5:0:0:0: Direct-Access Lexar JD FireFly 1100 PQ: 0 ANSI: 0 CCS Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB) Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Write Protect is off Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Mode Sense: 43 00 00 00 Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Assuming drive cache: write through Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Assuming drive cache: write through Aug 5 20:26:59 unraid kernel: sdg: sdg1 Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Assuming drive cache: write through Aug 5 20:26:59 unraid kernel: sd 5:0:0:0: [sdg] Attached SCSI removable disk Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15304) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15305) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15306) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15307) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15308) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15309) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15310) failed Aug 5 20:27:01 unraid kernel: FAT: Directory bread(block 15311) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615896) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615897) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615898) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615899) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615900) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615901) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615902) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615903) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615896) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615897) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615898) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615899) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615900) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615901) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615902) failed Aug 5 20:27:12 unraid kernel: FAT: Directory bread(block 6615903) failed Aug 5 20:27:12 unraid kernel: FAT: FAT read failed (blocknr 694) syslog.txt.zip Quote Link to comment
Joe L. Posted August 5, 2011 Share Posted August 5, 2011 A reboot will probably get them back. Apparently, your USB device disconnected, so all reads of it fail. (You could try un-plugging and re-inserting the USB flash drive, but it might not work if the port has been disabled by the OS) Quote Link to comment
mrmachine Posted August 5, 2011 Author Share Posted August 5, 2011 Rebooted, and it came back up and started a correcting parity check. Is unRAID supposed to do that? Shouldn't it do a non-correcting parity check, and at least require me to confirm that I want to correct parity before making any changes? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.