Hi,

 

Been battling with my new unRAID for a few days with various problems encountered as I precleared then attempted to get the array online. Thought I had everything up and running last night only to have one of the drives spit out a bunch of errors...

 

All drives precleared without any errors etc. Re-did one disk twice on preclear as it refused to format (went red during format).

 

Any help greatly appreciated.

 

Running version 5.0-beta14

 

Mar 31 17:14:57 Tower kernel: end_request: I/O error, dev sdh, sector 3999612736 (Errors)
Mar 31 17:14:57 Tower kernel: md: disk0 read error (Errors)
Mar 31 17:14:57 Tower kernel: handle_stripe read error: 3999612672/0, count: 1 (Errors)
Mar 31 17:14:57 Tower kernel: md: disk3 read error (Errors)
Mar 31 17:14:57 Tower kernel: handle_stripe read error: 3999612672/2, count: 1 (Errors)
Mar 31 17:14:57 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:14:57 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 499951584. Fsck? (Errors)
Mar 31 17:14:57 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [92 101 0x0 SD] (Errors)
Mar 31 17:15:01 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:15:01 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 500826495. Fsck? (Errors)
Mar 31 17:15:01 Tower unmenu[1121]: ls: reading directory /mnt/disk1/TV Shows/Awake/Season 1/: Input/output error (Errors)

 

Edit: All the data on the array at the moment is purely for testing so if the best suggestion is the re-do the array please let me know the steps 

 

Edit2:

 

More code from the log, appears to be 'missing data' whenever I try to browse where the data 'was'.

 

Mar 31 17:23:23 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 243317231. Fsck? (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [454 464 0x0 SD] (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 242947237. Fsck? (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [454 463 0x0 SD] (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 240833345. Fsck? (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [454 458 0x0 SD] (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 243929516. Fsck? (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [454 466 0x0 SD] (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 2 (Minor Issues)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-5150 search_by_key: invalid format found in block 244613460. Fsck? (Errors)
Mar 31 17:23:23 Tower kernel: REISERFS error (device md1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [454 468 0x0 SD] (Errors)

syslog.zip

Adding syslog for when I took the array offline, 3 disks (parity, disk1, disk2) now state 'wrong' ?

 

syslog_taking_array_offline.txt

See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

OK,

 

/dev/md1 - superblock cannot be found - Failed to open the filesystem

/dev/md2 - superblock cannot be found - Failed to open the filesystem

/dev/md3 - superblock cannot be found - Failed to open the filesystem

 

attached new syslog.

syslog2.txt

Oddly enough now disk2 has gone offline...(red light)..Thinking of just blowing the whole thing away re-preclearing all drives?

 

Edit:

- wiped the array config file

- preclearing all disk thats were present in array

 

- Got an error presented during preclear for the 3x 3TB seagate "WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn

't support GPT. Use GNU Parted" anything to be concerned about?

Oddly enough now disk2 has gone offline...(red light)..Thinking of just blowing the whole thing away re-preclearing all drives?

 

Edit:

- wiped the array config file

- preclearing all disk thats were present in array

 

- Got an error presented during preclear for the 3x 3TB seagate "WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn

't support GPT. Use GNU Parted" anything to be concerned about?

Nothing to worry about with GPT partition on 3TB drives.  It is expected.  preclear script does not use fdisk to partition drives, only to list existing partitioning.

 

If a drive shows "red" a write to it failed.  Nothing involving pre-clearing will EVER fix that. 

You need to find and correct the reason the "write" failed.    (bad power, bad disk, bad cabling, bad connections)

Thanks for the response Joe, after searching around threads in here it could be due to my IBM M1015 (flashed to LSI IT mode), is that still an issue with this version of the Beta?

 

I've already well under way of preclearing everything then going to run it from the 8-ports on board to see if I get the errors using the normal connectors (vs the SFF-8087 from the card) etc. At least then i can isolate part of the problem.

 

Well everything went 100% with the fresh build....until

 

Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] CDB: cdb[0]=0x28: 28 00 00 00 01 40 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdh, sector 320
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 00 01 40 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdg, sector 320
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] CDB: cdb[0]=0x28: 28 00 00 00 01 48 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdh, sector 328
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 00 01 48 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdg, sector 328
Apr  3 11:29:03 BlackBox kernel: md: disk0 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 256/0, count: 1
Apr  3 11:29:03 BlackBox kernel: md: disk1 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 256/1, count: 1
Apr  3 11:29:03 BlackBox kernel: md: disk0 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 264/0, count: 1
Apr  3 11:29:03 BlackBox kernel: md: disk1 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 264/1, count: 1
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:3:0: [sdh] CDB: cdb[0]=0x28: 28 00 00 00 01 50 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdh, sector 336
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] Device not ready
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  Sense Key : 0x2 [current] 
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:03 BlackBox kernel: sd 0:0:2:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 00 01 50 00 00 08 00
Apr  3 11:29:03 BlackBox kernel: end_request: I/O error, dev sdg, sector 336
Apr  3 11:29:03 BlackBox kernel: md: disk0 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 272/0, count: 1
Apr  3 11:29:03 BlackBox kernel: md: disk1 read error
Apr  3 11:29:03 BlackBox kernel: handle_stripe read error: 272/1, count: 1
Apr  3 11:29:36 BlackBox kernel: sd 0:0:2:0: [sdg] Device not ready
Apr  3 11:29:36 BlackBox kernel: sd 0:0:2:0: [sdg]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:36 BlackBox kernel: sd 0:0:2:0: [sdg]  Sense Key : 0x2 [current] 
Apr  3 11:29:36 BlackBox kernel: sd 0:0:2:0: [sdg]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:36 BlackBox kernel: sd 0:0:2:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 01 00 d8 00 00 08 00
Apr  3 11:29:36 BlackBox kernel: end_request: I/O error, dev sdg, sector 65752
Apr  3 11:29:36 BlackBox kernel: sd 0:0:3:0: [sdh] Device not ready
Apr  3 11:29:36 BlackBox kernel: sd 0:0:3:0: [sdh]  Result: hostbyte=0x00 driverbyte=0x08
Apr  3 11:29:36 BlackBox kernel: sd 0:0:3:0: [sdh]  Sense Key : 0x2 [current] 
Apr  3 11:29:36 BlackBox kernel: sd 0:0:3:0: [sdh]  ASC=0x4 ASCQ=0x2
Apr  3 11:29:36 BlackBox kernel: sd 0:0:3:0: [sdh] CDB: cdb[0]=0x28: 28 00 00 01 00 d8 00 00 08 00
Apr  3 11:29:36 BlackBox kernel: end_request: I/O error, dev sdh, sector 65752
Apr  3 11:29:36 BlackBox kernel: md: disk0 read error
Apr  3 11:29:36 BlackBox kernel: handle_stripe read error: 65688/0, count: 1
Apr  3 11:29:36 BlackBox kernel: md: disk1 read error
Apr  3 11:29:36 BlackBox kernel: handle_stripe read error: 65688/1, count: 1

 

Up until then 0 errors throughout preclears, formatting, parity build...

The parity drive is having problems. Post a SMART report for parity.

Ok I ran the SMART reports on every drive, 0 errors on short test.

 

I switched out my M1015 and put everything through the onboard ports, all green after copying 3TB of data onto the array.

 

I have a feeling its less the M1015 and more likely the cable, does anyone have a reputable supplier of the correct SFF-8087 -> 4x SATA 36pin cable? (Australia or shipping to here)

 

Edit: Is it possible my IBM/LSI card is having issues since im running b14? I've seen in other threads people noting issues running b14 with LSI cards.