July 26, 201510 yr I recently replaced a 900Gb 2.5" SAS drive with a WD Red 1Tb 2.5" drive as my parity drive. I'd had a couple errors over the past couple of days, due to this new parity disk returning errors during initialization parity check. I never thought to try and get the errors. I work up this morning to see the following message on my unraid server. smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: /1:0:3:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes Physical block size: 1903784304 bytes Lowest aligned LBA: 14896 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I'm hoping I have to just log into the server via telnet and modify some smart settings, or changing it to never spin down, and that will be the end of it. Does anyone have any thoughts on the matter? This is the first time I've run into any kind of errors like this.
July 26, 201510 yr Seems more likely a smartctl compatibility issue. I don't remember how myself, but there's a way to update the smartctl database, try searching it. What disk controller is it connected to? Anything exotic, like an unusual SAS controller, or an Areca?
Archived
This topic is now archived and is closed to further replies.