*New 12.1 series Release:
2019-11-08: XigmaNAS 12.1.0.4.7091 - released!

*New 11.3 series Release:
2019-10-19: XigmaNAS 11.3.0.4.7014 - released


We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

SMART error (FailedOpenDevice) detected on host

Hard disks, HDD, RAID Hardware, disk controllers, SATA, PATA, SCSI, IDE, On Board, USB, Firewire, CF (Compact Flash)
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
User avatar
RAJOD
experienced User
experienced User
Posts: 85
Joined: 26 Mar 2013 22:23
Status: Offline

SMART error (FailedOpenDevice) detected on host

#1

Post by RAJOD » 10 Dec 2015 08:09

I got a message that one of my drives went offline. Its a ZFS mirror. (2 drives)

Question is:
Do i need to do anything when I reboot the system?

The drive went offline but when I rebooted it was backonline and everything seems fine so far.
I know that I added 1 folder to the single drive (not knowing one was offline). Is it smart enough to auto mirror back to the drive that came back online? Normally I thought it would have to do an entire remirror to the drive that was offline.

I my dell server with a RAID card, If I pull drive for a minute and then plug it back in it will just assume that drive is out of date and remirror from the working drive to the one I plugged back in. Even if no data changed.

On ZFS what did it do when the drive came back on? Did it auto copy the new folder I made to the drive that came back on? (I had to reboot it to get it to come back on)

Or do I have to rescan the drives or do a scrub?

I am doing a scrub but it seemed to be working fine doing nothing.

I guess this situation is different from a failed drive. On a failed drive you actually put a new blank drive in the system. You would need to add that drive.
In this case nothing was added it was the same drive that for what ever reason went offline. It could be a bad cable or maybe a controller issue. Don't know yet.
NAS1 9.1.0.1-Sandstorm(847)- Intel G1610 @2.6Ghz / MB - Gigabyte B75M-3DH Ram - 8 gigs / HD - WD RED 2TB x 2 in Raid 1 ZFS
NAS2 9.3.0.2-Nayla(1771)- Quad Xeon(R) CPU 5150@2.66GHz x 2 / MB-Dell 490 8Gb ECC HD - Toshiba 5TB x 2 in Raid 1 ZFS
NAS3 10.2.0.2-Prester(1855) - LENOVO ThinkServer TS140 i3-4130 CPU@3.40GHz, Ram - 4GbECC / HD - WD RED 2TBx2 in Raid1 ZFS

User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2458
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#2

Post by b0ssman » 10 Dec 2015 11:51

well a drive disconnecting is normally a sign of a dying drive.
post the smart values of all your drives.
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.

User avatar
RAJOD
experienced User
experienced User
Posts: 85
Joined: 26 Mar 2013 22:23
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#3

Post by RAJOD » 11 Dec 2015 00:34

Even if failing I was wondering what nas4free did when I restarted it. It did not do a full re-mirror, it was all normal as if it did not happen. I know it copied the new folder I made back to the restarted drive but it was fast so could not have been a full re-mirror.

This system is pretty new less than 6 months so would be warranty if one drive is going.
Here is the smart info.

Device /dev/ada0 - Western Digital Red
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD20EFRX-68EUZN0
Serial Number: WD-WCC4MP2ATL9Z
LU WWN Device Id: 5 0014ee 25fc3657f
Firmware Version: 80.00A80
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Dec 10 17:42:43 2015 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


ID ATTRIBUTE NAME RAW VALUE DESCRIPTION
1 Raw_Read_Error_Rate 0 (Vendor specific raw value.) Stores data related to the rate of hardware read errors that occurred when reading data from a disk surface. The raw value has different structure for different vendors and is often not meaningful as a decimal number.
3 Spin_Up_Time 0 Average time of spindle spin up (from zero RPM to fully operational).
4 Start_Stop_Count 4 A tally of spindle start/stop cycles. The spindle turns on, and hence the count is increased, both when the hard disk is turned on after having before been turned entirely off (disconnected from power source) and when the hard disk returns from having previously been put to sleep mode.
5 Reallocated_Sector_Ct 0 Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as 'reallocated' and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called 'remaps'. The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future. While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. If sequential access speed is critical, the remapped sectors can be manually marked as bad blocks in the file system in order to prevent their use.
7 Seek_Error_Rate 0 (Vendor specific raw value.) Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. The raw value has different structure for different vendors and is often not meaningful as a decimal number.
9 Power_On_Hours 2340 Count of hours in power-on state. The raw value of this attribute shows total count of hours (or minutes, or seconds, depending on manufacturer) in power-on state.
10 Spin_Retry_Count 0 Count of retry of spin start attempts. This attribute stores a total count of the spin start attempts to reach the fully operational speed (under the condition that the first attempt was unsuccessful). An increase of this attribute value is a sign of problems in the hard disk mechanical subsystem.
11 Calibration_Retry_Count 0 This attribute indicates the count that recalibration was requested (under the condition that the first attempt was unsuccessful). An increase of this attribute value is a sign of problems in the hard disk mechanical subsystem.
12 Power_Cycle_Count 4 This attribute indicates the count of full hard disk power on/off cycles.
192 Power-Off_Retract_Count 2 Count of times the heads are loaded off the media. Heads can be unloaded without actually powering off.
193 Load_Cycle_Count 897 Count of load/unload cycles into head landing zone position.
194 Temperature_Celsius 30 Current internal temperature.
196 Reallocated_Event_Count 0 Count of remap operations. The raw value of this attribute shows the total count of attempts to transfer data from reallocated sectors to a spare area. Both successful & unsuccessful attempts are counted.
197 Current_Pending_Sector 0 Count of 'unstable' sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written. However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the 'Reallocation Event Count' (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.
198 Offline_Uncorrectable 0 The total count of uncorrectable errors when reading/writing a sector. A rise in the value of this attribute indicates defects of the disk surface and/or problems in the mechanical subsystem.
199 UDMA_CRC_Error_Count 0 The count of errors in data transfer via the interface cable as determined by ICRC (Interface Cyclic Redundancy Check).
200 Multi_Zone_Error_Rate 0 The total count of errors when writing a sector.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (26280) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 266) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2340
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 897
194 Temperature_Celsius 0x0022 117 111 000 Old_age Always - 30
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2335 -
# 2 Extended offline Completed without error 00% 2335 -
# 3 Extended offline Interrupted (host reset) 70% 2328 -
# 4 Short offline Completed without error 00% 2288 -
# 5 Short offline Completed without error 00% 2264 -
# 6 Short offline Completed without error 00% 2240 -
# 7 Short offline Completed without error 00% 2216 -
# 8 Short offline Completed without error 00% 2192 -
# 9 Short offline Completed without error 00% 2168 -
#10 Short offline Completed without error 00% 2144 -
#11 Short offline Completed without error 00% 2120 -
#12 Short offline Completed without error 00% 2096 -
#13 Short offline Completed without error 00% 2072 -
#14 Short offline Completed without error 00% 2048 -
#15 Short offline Completed without error 00% 2024 -
#16 Short offline Completed without error 00% 2000 -
#17 Short offline Completed without error 00% 1976 -
#18 Short offline Completed without error 00% 1952 -
#19 Short offline Completed without error 00% 1928 -
#20 Short offline Completed without error 00% 1904 -
#21 Short offline Completed without error 00% 1880 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Device /dev/ada1 - Western Digital Red
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD20EFRX-68EUZN0
Serial Number: WD-WCC4MKE5AUFU
LU WWN Device Id: 5 0014ee 20a6e1579
Firmware Version: 80.00A80
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 (minor revision not indicated)
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Thu Dec 10 17:42:43 2015 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled


ID ATTRIBUTE NAME RAW VALUE DESCRIPTION
1 Raw_Read_Error_Rate 0 (Vendor specific raw value.) Stores data related to the rate of hardware read errors that occurred when reading data from a disk surface. The raw value has different structure for different vendors and is often not meaningful as a decimal number.
3 Spin_Up_Time 4475 Average time of spindle spin up (from zero RPM to fully operational).
4 Start_Stop_Count 63 A tally of spindle start/stop cycles. The spindle turns on, and hence the count is increased, both when the hard disk is turned on after having before been turned entirely off (disconnected from power source) and when the hard disk returns from having previously been put to sleep mode.
5 Reallocated_Sector_Ct 0 Count of reallocated sectors. When the hard drive finds a read/write/verification error, it marks that sector as 'reallocated' and transfers data to a special reserved area (spare area). This process is also known as remapping, and reallocated sectors are called 'remaps'. The raw value normally represents a count of the bad sectors that have been found and remapped. Thus, the higher the attribute value, the more sectors the drive has had to reallocate. This allows a drive with bad sectors to continue operation; however, a drive which has had any reallocations at all is significantly more likely to fail in the near future. While primarily used as a metric of the life expectancy of the drive, this number also affects performance. As the count of reallocated sectors increases, the read/write speed tends to become worse because the drive head is forced to seek to the reserved area whenever a remap is accessed. If sequential access speed is critical, the remapped sectors can be manually marked as bad blocks in the file system in order to prevent their use.
7 Seek_Error_Rate 0 (Vendor specific raw value.) Rate of seek errors of the magnetic heads. If there is a partial failure in the mechanical positioning system, then seek errors will arise. Such a failure may be due to numerous factors, such as damage to a servo, or thermal widening of the hard disk. The raw value has different structure for different vendors and is often not meaningful as a decimal number.
9 Power_On_Hours 3523 Count of hours in power-on state. The raw value of this attribute shows total count of hours (or minutes, or seconds, depending on manufacturer) in power-on state.
10 Spin_Retry_Count 0 Count of retry of spin start attempts. This attribute stores a total count of the spin start attempts to reach the fully operational speed (under the condition that the first attempt was unsuccessful). An increase of this attribute value is a sign of problems in the hard disk mechanical subsystem.
11 Calibration_Retry_Count 0 This attribute indicates the count that recalibration was requested (under the condition that the first attempt was unsuccessful). An increase of this attribute value is a sign of problems in the hard disk mechanical subsystem.
12 Power_Cycle_Count 63 This attribute indicates the count of full hard disk power on/off cycles.
192 Power-Off_Retract_Count 60 Count of times the heads are loaded off the media. Heads can be unloaded without actually powering off.
193 Load_Cycle_Count 1178 Count of load/unload cycles into head landing zone position.
194 Temperature_Celsius 32 Current internal temperature.
196 Reallocated_Event_Count 0 Count of remap operations. The raw value of this attribute shows the total count of attempts to transfer data from reallocated sectors to a spare area. Both successful & unsuccessful attempts are counted.
197 Current_Pending_Sector 0 Count of 'unstable' sectors (waiting to be remapped, because of unrecoverable read errors). If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later); instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written. However some drives will not immediately remap such sectors when written; instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the 'Reallocation Event Count' (0xC4) will not be increased). This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors.
198 Offline_Uncorrectable 0 The total count of uncorrectable errors when reading/writing a sector. A rise in the value of this attribute indicates defects of the disk surface and/or problems in the mechanical subsystem.
199 UDMA_CRC_Error_Count 0 The count of errors in data transfer via the interface cable as determined by ICRC (Interface Cyclic Redundancy Check).
200 Multi_Zone_Error_Rate 0 The total count of errors when writing a sector.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (25620) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 259) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 170 167 021 Pre-fail Always - 4475
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 63
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3523
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 63
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 60
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1178
194 Temperature_Celsius 0x0022 115 109 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 3518 -
# 2 Extended offline Completed without error 00% 3517 -
# 3 Short offline Completed without error 00% 3494 -
# 4 Short offline Completed without error 00% 3470 -
# 5 Short offline Completed without error 00% 3446 -
# 6 Short offline Completed without error 00% 3422 -
# 7 Short offline Completed without error 00% 3398 -
# 8 Short offline Completed without error 00% 3374 -
# 9 Short offline Completed without error 00% 3350 -
#10 Short offline Completed without error 00% 3326 -
#11 Short offline Completed without error 00% 3302 -
#12 Short offline Completed without error 00% 3278 -
#13 Short offline Completed without error 00% 3254 -
#14 Short offline Completed without error 00% 3230 -
#15 Short offline Completed without error 00% 3206 -
#16 Short offline Completed without error 00% 3182 -
#17 Short offline Completed without error 00% 3158 -
#18 Short offline Completed without error 00% 3134 -
#19 Short offline Completed without error 00% 3110 -
#20 Short offline Completed without error 00% 3086 -
#21 Short offline Completed without error 00% 3062 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
NAS1 9.1.0.1-Sandstorm(847)- Intel G1610 @2.6Ghz / MB - Gigabyte B75M-3DH Ram - 8 gigs / HD - WD RED 2TB x 2 in Raid 1 ZFS
NAS2 9.3.0.2-Nayla(1771)- Quad Xeon(R) CPU 5150@2.66GHz x 2 / MB-Dell 490 8Gb ECC HD - Toshiba 5TB x 2 in Raid 1 ZFS
NAS3 10.2.0.2-Prester(1855) - LENOVO ThinkServer TS140 i3-4130 CPU@3.40GHz, Ram - 4GbECC / HD - WD RED 2TBx2 in Raid1 ZFS

User avatar
RAJOD
experienced User
experienced User
Posts: 85
Joined: 26 Mar 2013 22:23
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#4

Post by RAJOD » 11 Dec 2015 16:00

b0ssman wrote:well a drive disconnecting is normally a sign of a dying drive.
post the smart values of all your drives.
I ran the "LONG" smart test on both drives and both came back ok. Is it possible some glitch of smart software kicked it offline? It does have a offline feature.
NAS1 9.1.0.1-Sandstorm(847)- Intel G1610 @2.6Ghz / MB - Gigabyte B75M-3DH Ram - 8 gigs / HD - WD RED 2TB x 2 in Raid 1 ZFS
NAS2 9.3.0.2-Nayla(1771)- Quad Xeon(R) CPU 5150@2.66GHz x 2 / MB-Dell 490 8Gb ECC HD - Toshiba 5TB x 2 in Raid 1 ZFS
NAS3 10.2.0.2-Prester(1855) - LENOVO ThinkServer TS140 i3-4130 CPU@3.40GHz, Ram - 4GbECC / HD - WD RED 2TBx2 in Raid1 ZFS

User avatar
b0ssman
Forum Moderator
Forum Moderator
Posts: 2458
Joined: 14 Feb 2013 08:34
Location: Munich, Germany
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#5

Post by b0ssman » 11 Dec 2015 17:10

drives seem fine. then it might be the raid card.

raid cards and zfs are sub optimal anyway. which card is it?
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.

User avatar
RAJOD
experienced User
experienced User
Posts: 85
Joined: 26 Mar 2013 22:23
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#6

Post by RAJOD » 11 Dec 2015 17:50

b0ssman wrote:drives seem fine. then it might be the raid card.

raid cards and zfs are sub optimal anyway. which card is it?
Raid card? Where did you get the idea I have a raid card in it?

Its a brand new Lenovo Think server. Using onboard SATA ports and its just a mirror. Two drives.

So to me it could be a faulty cable, maybe a dying drive or maybe a smart firmware glitch where it pulled the good drive offline.

I guess I'll not worry about unless it happens again. But its nice to know why it happened vs just saying oh well it was the gremlins.
NAS1 9.1.0.1-Sandstorm(847)- Intel G1610 @2.6Ghz / MB - Gigabyte B75M-3DH Ram - 8 gigs / HD - WD RED 2TB x 2 in Raid 1 ZFS
NAS2 9.3.0.2-Nayla(1771)- Quad Xeon(R) CPU 5150@2.66GHz x 2 / MB-Dell 490 8Gb ECC HD - Toshiba 5TB x 2 in Raid 1 ZFS
NAS3 10.2.0.2-Prester(1855) - LENOVO ThinkServer TS140 i3-4130 CPU@3.40GHz, Ram - 4GbECC / HD - WD RED 2TBx2 in Raid1 ZFS

User avatar
RAJOD
experienced User
experienced User
Posts: 85
Joined: 26 Mar 2013 22:23
Status: Offline

Re: SMART error (FailedOpenDevice) detected on host

#7

Post by RAJOD » 11 Dec 2015 17:52

RAJOD wrote:
b0ssman wrote:drives seem fine. then it might be the raid card.

raid cards and zfs are sub optimal anyway. which card is it?
Raid card? Where did you get the idea I have a raid card in it?

Its a brand new Lenovo Think server. Using onboard SATA ports and its just a mirror. Two drives.

So to me it could be a faulty cable, maybe a dying drive or maybe a smart firmware glitch where it pulled the good drive offline.

I guess I'll not worry about unless it happens again. But its nice to know why it happened vs just saying oh well it was the gremlins.

Oh I think you might have gotten confused as I did try to get a raid card working on other posts. That would have been a 5th NAS that I gave up on. I still have two new SAS drives and a bunch of raid cards sitting in a box doing nothing.
NAS1 9.1.0.1-Sandstorm(847)- Intel G1610 @2.6Ghz / MB - Gigabyte B75M-3DH Ram - 8 gigs / HD - WD RED 2TB x 2 in Raid 1 ZFS
NAS2 9.3.0.2-Nayla(1771)- Quad Xeon(R) CPU 5150@2.66GHz x 2 / MB-Dell 490 8Gb ECC HD - Toshiba 5TB x 2 in Raid 1 ZFS
NAS3 10.2.0.2-Prester(1855) - LENOVO ThinkServer TS140 i3-4130 CPU@3.40GHz, Ram - 4GbECC / HD - WD RED 2TBx2 in Raid1 ZFS

Post Reply

Return to “Hard disk & controller”