Ackshiel Posted December 3, 2012 Share Posted December 3, 2012 Hello, I have been using unRaid for a few years now and this summer I decided to build an ESXI system, which has been running great for a long time.... until last week!! My syslogs are riddled with the following message. my webconsole is all messed up as well, some drives are saying they are missing, when they are not. Dec 3 08:34:09 Huricane kernel: handle_stripe read error: 711034112/1, count: 1 Dec 3 08:34:09 Huricane kernel: sd 0:0:3:0: [sdf] Device not ready Dec 3 08:34:09 Huricane kernel: sd 0:0:3:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08 Dec 3 08:34:09 Huricane kernel: sd 0:0:3:0: [sdf] Sense Key : 0x2 [current] Dec 3 08:34:09 Huricane kernel: sd 0:0:3:0: [sdf] ASC=0x4 ASCQ=0x2 Dec 3 08:34:09 Huricane kernel: sd 0:0:3:0: [sdf] CDB: cdb[0]=0x28: 28 00 2a 61 85 50 00 00 18 00 Dec 3 08:34:09 Huricane kernel: end_request: I/O error, dev sdf, sector 711034192 Dec 3 08:34:09 Huricane kernel: md: disk1 read error Dec 3 08:34:09 Huricane kernel: handle_stripe read error: 711034128/1, count: 1 Dec 3 08:34:09 Huricane kernel: md: disk1 read error Dec 3 08:34:09 Huricane kernel: handle_stripe read error: 711034136/1, count: 1 Dec 3 08:34:09 Huricane kernel: md: disk1 read error Dec 3 08:34:09 Huricane kernel: handle_stripe read error: 711034144/1, count: 1 Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane kernel: sd 0:0:0:0: [sdc] Device not ready Dec 3 08:34:09 Huricane kernel: sd 0:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 Dec 3 08:34:09 Huricane kernel: sd 0:0:0:0: [sdc] Sense Key : 0x2 [current] Dec 3 08:34:09 Huricane kernel: sd 0:0:0:0: [sdc] ASC=0x4 ASCQ=0x2 Dec 3 08:34:09 Huricane kernel: sd 0:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 53 5e 75 3f 00 00 08 00 Dec 3 08:34:09 Huricane kernel: end_request: I/O error, dev sdc, sector 1398699327 Dec 3 08:34:09 Huricane kernel: md: disk4 read error Dec 3 08:34:09 Huricane kernel: handle_stripe read error: 1398699264/4, count: 1 Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS (device md4): Remounting filesystem read-only Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane shfs/user: shfs_read: read: (5) Input/output error Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? Dec 3 08:34:09 Huricane kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 65535 does not match to the expected one 2 Dec 3 08:34:09 Huricane kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 174837408. Fsck? At first I thought it was just one bad disk, but now I am seeing it on multiple disks, which makes me think it is something else. I have run smart reports on a few of the drives, and they APPEAR to be OK. I then proceeded to doing a chkdsk on the actual USB key, and it checks out OK. I checked the cabling and it looks good as well. Any assistance would be GREATLY appreciated, as I would like to be back to my storage Nirvana!! Start of syslog https://www.dropbox.com/s/wustwm5oeje72hl/syslog.1.gz Rolled over log https://www.dropbox.com/s/m7eog7ku1vel6se/syslog.gz As for system specs within the VM. 4G of RAM 2 CPU's assigned at 2.1GHz SATA card is IBM M1015 unraid 5Beta13 Power supply - OCZ 750W PC Power Thanking you in advance!! Link to comment
bcbgboy13 Posted December 4, 2012 Share Posted December 4, 2012 I believe Beta 13 and Beta 14 to be a no-go for any LSI based cards (Beta 12 and 12a were OK as is the latest RC8a with the manual SAMBA fix). This could be your problem. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.