Disk type UNKNOWN

[InfiniteAlienMonkeyc0de]

My server crashed the other day and when in came back on one of my drives says unknown under type and the pool is offline since that drive is in that pool. I have this alert (see attachment) which I'm pretty sure as something to do with the smart test. But I really don't know where to begin. I do not have raid set up. I built this cheaply just for streaming movies in my home. If anyone could help me to see if my data is lost or if there is something I can do. Thank you

 

[joeschmuck]

You could check out the Hard Drive Troubleshooting Guide in my signature, see what the drive SMART data has to say. Also if you could post the output of zpool status, and of course the customary basic information we always ask for per the forum rules or we are basically flying blind here.

 

[InfiniteAlienMonkeyc0de]

You could check out the Hard Drive Troubleshooting Guide in my signature, see what the drive SMART data has to say. Also if you could post the output of zpool status, and of course the customary basic information we always ask for per the forum rules or we are basically flying blind here.

Sorry about that. Here is everything you requested. I am running SMART test now and will look at the troubleshooting guide. I have a bunch of stuff unplugged as I just bought four new 8TB HDD's to add RAID and replace two of my current pools but trying to get this pool back up so I can transfer the data first.


TrueNAS 12.0
GIGABYTE GA0Z68XP-UD3 MOTEHRBOARD (Award BIOS -F10 update)
INTEL i5-2500k 3.3ghz
32gb DDR3 1600 G.SKILL RIPJAWS X
I have 7 HDD's currently plugged in.
I have HDD controller but its not plugged in at them moment.

OS: SAMSUNG SSD PM830 mSATA 32GB

Pools:

FreeNas = (2 x 4TB WD Red) Running
FreeNas_2 = (2 x 1TB Seagate barracuda + 1 x 2TB Seagate Barracuda + 1 x 750GB WD Green) "WD Green is the one reporting as TYPE UNKNOWN"
FreeNAS_3 = (2 x 2TB WD Red + 1 x 1TB Seagate barracuda) "Not Plugged in"

Code:

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@freenas[~]# zpool status
  pool: FreeNas
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
  scan: scrub repaired 0B in 15:04:37 with 0 errors on Sun Oct  4 15:04:40 2020
config:

        NAME                                                                         STATE     READ WRITE CKSUM
        FreeNas                                                                    ONLINE         0       0         0
          gptid/8ff78ff8-ff3e-11e5-8497-50e549b8a47b     ONLINE         0       0         0
          gptid/9119e3d9-ff3e-11e5-8497-50e549b8a47b  ONLINE         0       0        0

errors: No known data errors

  pool: freenas-boot
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(5) for details.
scan: scrub repaired 0B in 00:01:20 with 0 errors on Thu Oct 29 03:46:20 2020
config:
 
         NAME                                                                         STATE     READ WRITE CKSUM
         freenas-boot                                                               ONLINE         0       0         0
             ada6p2                                                                    ONLINE         0       0         0

 

[joeschmuck]

Well when you are done with everything, if you need some help then toss out another message, someone will offer assistance. As for the drive with the unknown type, run the SMART command smartctl -a /dev/adax (where adax is the drive identifier) and post that output. Maybe it has just had a major electrical failure and will refuse to work. I'd also connect it to a different SATA port in your system.

Good Luck

 

[InfiniteAlienMonkeyc0de]

Well when you are done with everything, if you need some help then toss out another message, someone will offer assistance. As for the drive with the unknown type, run the SMART command smartctl -a /dev/adax (where adax is the drive identifier) and post that output. Maybe it has just had a major electrical failure and will refuse to work. I'd also connect it to a different SATA port in your system.

Good Luck

root@freenas[~]# smartctl -a /dev/ada3
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-PRERELEASE amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Blue (SATA)
Device Model: WDC WD7500AAKS-00RBA0
Serial Number: WD-WCAPT0122907
LU WWN Device Id: 5 0014ee 2aaf96ec3
Firmware Version: 30.04G30
User Capacity: 750,156,374,016 bytes [750 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 (minor revision not indicated)
Local Time is: Thu Jan 6 08:58:42 2011 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
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: (15960) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off supp ort.
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: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 6) minutes.
SCT capabilities: (0x303f) 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 0x000f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0003 182 182 021 Pre-fail Always - 7883
4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5726
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0
9 Power_On_Hours 0x0032 001 001 000 Old_age Always - 102909
10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1609
192 Power-Off_Retract_Count 0x0032 199 199 000 Old_age Always - 1260
193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6078
194 Temperature_Celsius 0x0022 109 101 000 Old_age Always - 43
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 51418
200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0

SMART Error Log Version: 1
ATA Error Count: 11664 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 11664 occurred at disk power-on lifetime: 37372 hours (1557 days + 4 hours )
When the command that caused the error occurred, the device was active or idle .

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 e0 20 64 54 40 Error: ABRT 224 sectors at LBA = 0x00546420 = 5530656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 e0 20 64 54 57 00 00:01:55.543 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.543 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT

Error 11663 occurred at disk power-on lifetime: 37372 hours (1557 days + 4 hours )
When the command that caused the error occurred, the device was active or idle .

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 e0 20 64 54 40 Error: ABRT 224 sectors at LBA = 0x00546420 = 5530656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 e0 20 64 54 57 00 00:01:55.543 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.542 READ DMA EXT

Error 11662 occurred at disk power-on lifetime: 37372 hours (1557 days + 4 hours )
When the command that caused the error occurred, the device was active or idle .

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 e0 20 64 54 40 Error: ABRT 224 sectors at LBA = 0x00546420 = 5530656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT

Error 11661 occurred at disk power-on lifetime: 37372 hours (1557 days + 4 hours )
When the command that caused the error occurred, the device was active or idle .

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 e0 20 64 54 40 Error: ABRT 224 sectors at LBA = 0x00546420 = 5530656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT

Error 11660 occurred at disk power-on lifetime: 37372 hours (1557 days + 4 hours )
When the command that caused the error occurred, the device was active or idle .

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 e0 20 64 54 40 Error: ABRT 224 sectors at LBA = 0x00546420 = 5530656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 e0 20 64 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.542 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT
25 00 e0 20 62 54 57 00 00:01:55.541 READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

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.

 

[joeschmuck]

So you have a huge amount of hours on this hard drive and have not run a single SMART test. I highly recommend that you run a SMART Long/Extended Test on this drive and any other drives your have.

The good news is you have no known hard drive issues for this drive. You did have communications problems over 4.2 years (based on power on hours) ago but none since.

 

[InfiniteAlienMonkeyc0de]

So you have a huge amount of hours on this hard drive and have not run a single SMART test. I highly recommend that you run a SMART Long/Extended Test on this drive and any other drives your have.

The good news is you have no known hard drive issues for this drive. You did have communications problems over 4.2 years (based on power on hours) ago but none since.

Will do. Any idea why the drive shows up as type unknown? I can't get my pool to import since the drive will not show up correctly. If I run zpool import FreeNas_2. I do not get any errors. It just brings up a new root prompt like it completed but the pool is still unavailable.

 

[joeschmuck]

Did you say that the FreeNas_2 vdev was a Stripe? If the data has been damaged and it cannot read it properly then that could be your cause. But typically when I think of Unknown Type, I think it's an interface issue so maybe you could try a different SATA port. Also if you need the data off this drive then you could try to mount the two drives on Ubuntu and see if that works. Search the internet for something like "freenas mount pool ubuntu" and something I'm sure will pop up. Make sure you disconnect the other hard drives since they have no issues, while you are troubleshooting.

Good Luck

 

[InfiniteAlienMonkeyc0de]

Did you say that the FreeNas_2 vdev was a Stripe? If the data has been damaged and it cannot read it properly then that could be your cause. But typically when I think of Unknown Type, I think it's an interface issue so maybe you could try a different SATA port. Also if you need the data off this drive then you could try to mount the two drives on Ubuntu and see if that works. Search the internet for something like "freenas mount pool ubuntu" and something I'm sure will pop up. Make sure you disconnect the other hard drives since they have no issues, while you are troubleshooting.

Good Luck

Yes it a stiped pool. I have tried different sata ports and cables. I tried all that before making my first post. I will try mounting in Ubuntu. Thank you for ur help.

I have one more question.
If the drive was plugged into a different controller previously could that make a difference? I had a PCIe sata card hooked up previously and my motherboard has two different controllers on it. Could that possibly cause the issue with the drive showing up as UNKNOWN?

THANKS

 

[joeschmuck]

If the drive was plugged into a different controller previously could that make a difference?

If it was a simple SATA controller, No. If you happen to use a RAID controller and you had configured the drive as a RAID drive then yes. For normal SATA operations the system does not care which SATA port it uses, this is true for 99% of the time, and on rare occasion that 1% happens but it's doubtful you are in that predicament. I suspect your drive data is corrupt but that is why I recommended you use Ubuntu to try to mount the pool manually and using a different OS. If it works, copy all your data off and then you can work with the drives in question.

Something else you could do, if the data is something you do not care about, meaning you already have a copy of it, you could just wipe out the drives partition information and recreate the vdev/pool. But first, run that SMART long test on the drives. Make sure they drives are solid before investing too much time into them.

 

[InfiniteAlienMonkeyc0de]

I tired ubuntu but the drive still shows as unknown and won't mount. I tried to mount with sudo zpool import FreeNas_2, which tells me the pool can be mounted but to use -f but when I do sudo zpool import -f FreeNas_2 it tells me no pool with that name exists. Or something along those lines I cant remember the exact wording. Data is lost. Time to rebuild with RAID this time so that doesn't happen again. Live and learn. Thank you for all your help.

 

[joeschmuck]

Live and learn.

Hey, most of us have been down that road before. Good luck with your next pool and if you have any other vdevs that are striped, time to back them up.