Hello;)
on my WD-ShareSpace (4x1TB) my HDD4 is dead (definitly)!
From its death, I carefully remove it from the raid array (using the web-interface)
and, maybe it’s my mistake, as it is a SATA-disk, I physically hot-removed and hot-added it:
1st mistake : hot switch
2nd mistake : re-added it
Since, every 22 minutes (between 21min 50s and 22min to be precise) I got this error in the log:
Jan 25 12:53:34 My_Awesome_NAS daemon.alert wixEvent[994]: HDD Status - HDD 4 is absent.
Jan 25 12:59:13 My_Awesome_NAS daemon.info wixEvent[994]: HDD Status - HDD 4 is found.
Jan 25 12:59:15 My_Awesome_NAS daemon.alert wixEvent[994]: Hot Swap - Volume ‘DataVolume’ resync failed.
Jan 25 13:06:42 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Jan 25 13:28:33 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Jan 25 13:50:22 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Jan 25 13:50:31 My_Awesome_NAS daemon.alert wixEvent[994]: HDD SMART - HDD 4 SMART Health Status: Failed.
Jan 25 14:12:27 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Jan 25 14:34:22 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
-----// snap (trust me every 22minutes) // ----
Jan 25 22:13:10 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Jan 25 22:34:59 My_Awesome_NAS daemon.alert wixEvent[1013]: hdd_thread - SCSI ioctl error !
Of course, my array is in a “degraded state”
Of course, as my backup is not done yet, I carefully did NOT do any shutdown or reboot; there are a lot of really precious files (wedding pictures, my regretful ferret, my daugters and so on…) and I don’t want to bet/jeopardize those files
To my investigations it seems :
- the other disks are okay
“smartctl -a /dev/sdX” on the 3 remaining disks I see a source of worry:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
4 Start_Stop_Count 0x0032 090 090 000 Old_age Always - 10415
----- // snap // ------
9 Power_On_Hours 0x0032 061 061 000 Old_age Always - 28626
----- // snap // -----
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 40
40 power cycles seems correct to me (I didn’t reboot it very often)
~30000 hours seems correct (more than 3 years 24/7)
what is worrying me is the start_stop_count above 10000… this means I got the buggy series of green caviar disks…
(I wish I see this before), well I’m still far from from the 30000 cycles, but I don’t like this.
- the arrays seemed to working, in “degraded mode” but should work
‘cat /proc/mdstat’ and ‘mdadm --detail /dev/md2’
- the lvm as obviously an error (strange fact indeed)
pvs, vgs, lvs, pvdisplay, vgdisplay and lvdisplay show the expected info, but :
$ pvdisplay
/dev/sda: open failed: No such device or address
/dev/sda3: open failed: No such device or address
— Physical volume —
PV Name /dev/md2
VG Name vg0
PV Size 2.72 TB / not usable 2.00 TB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 714218
- from a media player (RaspBMC using KODI) every ~22minutes, I got a freeze, then a “go-home”
nothing interresting in the log
Do I need to worry (not usable 2.00TB), or is this caused by the missing sda drive (never check this before)?
BTW : All my files are still presents and readable
)