Jump to content

Issue with my controllers and green drives


Recommended Posts

I suddenly had unraid v6.2.1 say 2 of my WD Greens are failing, but when checking SMART, I see no errors logged. It doesn't look like they are failing and preclear on them went fine a few days prior. The errors logged on the webui main tab happened when copying data to them.

 

You can see what the 2TB HDDs show as here:

http://imgur.com/a/BMjcE

 

This is a small snippet from the system log:

 

[Mon Nov  7 15:56:08 2016] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
[Mon Nov  7 15:56:08 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.
[Mon Nov  7 15:56:08 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.
[Mon Nov  7 15:56:09 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.

To check the errors were not coming from unraid, I tried this command and got the following:

 

watch -n 5 "dmesg -T| tail -n $((LINES-6))"

 

[Mon Nov  7 16:07:09 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85.                                       
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08                                   
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 Sense Key : 0x5 [current]                                                               
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 ASC=0x20 ASCQ=0x0                                                                       
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00                        
[Mon Nov  7 16:07:09 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85.                                       
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08                                   
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 Sense Key : 0x5 [current]                                                               
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 ASC=0x20 ASCQ=0x0                                                                       
[Mon Nov  7 16:07:09 2016] sd 1:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00                        
[Mon Nov  7 16:07:09 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.                                                    
[Mon Nov  7 16:07:09 2016] 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.

 

The last line gets repeated over and over, so this is only a snippet.

 

I have since reset the server as when trying to stop the array, the webgui locked up and could not kill and restart it. The HDDs still came up with the red x.

 

Now both those drives are on my RocketRaid r750 controller on the same port multiplier channel.

 

I also have a 3ware 9650SE-8LPML controller as well. No drives in the pool are on it yet though.

 

I have many more EADS and EARS green HDDS still to add. All my drives have been set to never spin down, and unraid is also set to never spin them down. I do notice for some reason, unraid is still spinning them down as if I try to access them after awhile of inactivity, they take about 15 seconds to respond. I recently came from FlexRaid and never had this initial sluggishness with these green drives as I do now.

 

I'm not sure if there is an issue with the driver used for my controllers and/or with WD Green drives in general on unraid. But not sure what to do next.

 

I noticed one other oddity, when hovering over the X, it says the drives were being emulated, but I have not even computed parity yet, so not sure how it could emulate them. This seems like a bug.

 

Ful hardware list can be found here:

http://pcpartpicker.com/list/kRdHRG

Link to comment

So I was able to get rid of these errors:

3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.

 

All I did was move the one drive on that controller onto my r750. The 3ware bios no longer gets installed on boot because no drives are attached to it. So I take it the error is related to the controller and not any issues with the drive. Just sucks if I use that controller, I'll have that error flood my log and don't know how to fix it.

 

My log is still constantly flooded with these though:

Nov 9 05:06:02 Storinator kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

 

I still have yet to figure out the issue with my WD Green drives.

Link to comment
  • 1 month later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...