Pro Business unit with failed drive, not rebuilding?

[lurkermike]

Hey guys, quick question...

I have a failed drive in my Pro Business unit. The unit has (6) ST31500341AS 1.5TB drives in it. I replaced the failed drive with a ST33000650NS 3TB drive. When I pop the drive in, I hear it spin up, but the array doesn't go into any sort of rebuild process. In Frontview it still shows the status of disk 2 (the failed disk) as "Dead".

I'm going to try another ST33000650NS drive to be sure this isn't a drive issue, but these drives are brand new.

I see this in my syslog:

Code: Select all

Jun 14 10:43:11 mp-naspro kernel: sd 1:0:0:0: [sdb] Unhandled error code
Jun 14 10:43:11 mp-naspro kernel: sd 1:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 14 10:43:11 mp-naspro kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Jun 14 10:43:11 mp-naspro kernel: end_request: I/O error, dev sdb, sector 0
Jun 14 10:43:11 mp-naspro kernel: Buffer I/O error on device sdb, logical block 0
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb] Unhandled error code
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 04 00 00 20 00
Jun 14 10:43:12 mp-naspro kernel: end_request: I/O error, dev sdb, sector 4
Jun 14 10:43:12 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 0
Jun 14 10:43:12 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 1
Jun 14 10:43:12 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 2
Jun 14 10:43:12 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 3
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb] Unhandled error code
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 14 10:43:12 mp-naspro kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 04 00 00 08 00
Jun 14 10:43:12 mp-naspro kernel: end_request: I/O error, dev sdb, sector 4
Jun 14 10:43:12 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 0
Jun 14 10:43:23 mp-naspro kernel: sd 1:0:0:0: [sdb] Unhandled error code
Jun 14 10:43:23 mp-naspro kernel: sd 1:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 14 10:43:23 mp-naspro kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 04 00 00 08 00
Jun 14 10:43:23 mp-naspro kernel: end_request: I/O error, dev sdb, sector 4
Jun 14 10:43:23 mp-naspro kernel: Buffer I/O error on device sdb1, logical block 0
Jun 14 10:44:08 mp-naspro kernel: sd 1:0:0:0: [sdb] Unhandled error code
Jun 14 10:44:08 mp-naspro kernel: sd 1:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 14 10:44:08 mp-naspro kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
Jun 14 10:44:08 mp-naspro kernel: end_request: I/O error, dev sdb, sector 0
Jun 14 10:44:08 mp-naspro kernel: Buffer I/O error on device sdb, logical block 0


Any suggestions?

[mdgm]

What version of RAIDiator?

Have you tested the new drive using SeaTools?

[lurkermike]

What version of RAIDiator?

Have you tested the new drive using SeaTools?

RAIDiator 4.2.18

I have not tested with SeaTools. I have tried with a second drive, however, and have the same symptoms (drive isn't updated in FrontView and array doesn't start rebuilding when I insert it.)

[lurkermike]

Update: A reboot seems to have fixed the problem.

I removed the disk and rebooted the NAS. Inserted the disk and this time it was detected and started rebuilding!

Code: Select all

Jun 14 11:15:03 mp-naspro RAIDiator: New disk detected.  If multiple disks have been added, they will be processed one at a time.  Please do not remove any added disk(s) during this time. [Disk  2]


[chirpa]