Jump to content

Disk status inconsistency


Freddie

Recommended Posts

I had a data disk and cache disk drop out. I'm comfortable with the steps needed to recover the array, but I wanted to document a couple of inconsistencies I'm seeing with the data disc status. I'm running version 6.0-rc3.

 

The unRAID webGUI Main tab shows disk7 with a gray triangle. The tooltip legend/key suggests a triangle means "Content Being Reconstructed" and the gray means the disk is spun down. All other indications are that disk7 has been disabled so I would expect to see a red square, according to the legend/key.

 

The disks.ini file shows:

["disk7"]
idx="7"
name="disk7"
device="sdf"
id="SPCC_Solid_State_Disk_D70207470B6B00621416"
rotational="0"
size="234431032"
status="DISK_DSBL"
temp="*"
numReads="97767"
numWrites="38725"
numErrors="4"
format="MBR: 4K-aligned"
type="Data"
color="red-blink"
fsStatus="Mounted"
fsError=""
fsType="xfs"
fsSize="234316564"
fsFree="38380468"
spindownDelay="15"
spinupGroup="host5"
deviceSb="md7"
idSb="SPCC_Solid_State_Disk_D70207470B6B00621416"
sizeSb="234431032"

 

From the discussion of status icons "red-blink" means the disk is disabled and in standby (or spun down). The file at

/usr/local/emhttp/plugins/dynamix/images/red-blink.png is actually a gray triangle. That is why I'm seeing a gray triangle and I expect that was a mistake and it should be a square. I'd argue that it should be a red square, because I don't care if my disabled disk is in standby or not. After all the discussions of status icons, I'm hoping this is already fixed in rc4.

 

That leads me to wonder: Why does unRAID think my disabled disk is in standby?

 

disk in standby:

root@uwer:~# smartctl -i -n standby /dev/sdd
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

Device is in STANDBY mode, exit(2)
root@uwer:~# echo $?
2
root@uwer:~# hdparm -C /dev/sdd

/dev/sdd:
drive state is:  standby

 

disabled disk:

root@uwer:~# smartctl -i /dev/sdf
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:               /5:0:0:0
Product:              
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
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.
root@uwer:~# echo $?
2
root@uwer:~# hdparm -C /dev/sdf

/dev/sdf:
drive state is:  unknown

 

If unRAID is using the exit code of smartctl -n standby to determine the power state, that would explain why it thinks my disabled disk is in standby. Maybe there is a more robust way to check the power state.

 

I think I'll try to upgrade to rc4 before rebuilding disk7 so I can see if the disabled disk status is presented differently.

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...