iSCSI ***ERROR*** LU1: LUN0: Auto size error

[berrick]

Evening all.

I started to receive the following error in the daily output

status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.​

The disk in question is part of a mirrored pair configured as an iSCSI target. Used in Windows, formatted as NTFS.

In FreeNAS all ZFS were healthy and disk showed OK.

I shut down FreeNAS and checked the "faulty" disk quickly in windows and all appeared OK. Reinstalled it in FeeNAS and rebooted.

I then got the following message

istgt_lu.c:1604:istgt_lu_add_unit: ***ERROR*** LU1: LUN0: Auto size error
​

Looking around the forum it appears as though this was a bug and apparently fixed in 911 and was due to using auto for the Extent size?

I changed the Extent size from 0 to 940GB (the storage size) and rebooted. Everything looked OK and the iSCSI target connected. The problem now is Windows see's it as an un allocated disk :(

As part of my learning curve can someone explain the correct way I should have followed to try and correct this problem and if I can recover the data on the disks?

TYIA
see sig for more system info :)

 

[DrKK]

Let's see...

I have some questions:

1. Why are you a zillion versions behind on FreeNAS
2. Why are you using iSCSI? HAve you virtualized FreeNAS?
3. Why have you not told us your motherboard make and model, nor the make/model of your hard-drives, and so on?

 

[berrick]

1. Why are you a zillion versions behind on FreeNAS
   I'm a couple of versions behind but what I have just works. FreeNAS for me started out of curiosity then ended up being stable and useful from the outset. I don't have any jails, plugins or other stuff configured just file storage.
   
   
2. Why are you using iSCSI? HAve you virtualized FreeNAS?
   No I haven't virtualized FreeNAS. iSCSI, again started out of curiosity to see how difficult it was to setup and how reliable it could be using bare minimum spec. For me, with the hardware I had to hand it has just worked. I have continued to use it as it meant I could include the drive in windows search on my server without all the mucking about I would have to go through to achieve the same thing without iSCSI.
   
   
3. Why have you not told us your motherboard make and model, nor the make/model of your hard-drives, and so on?
   This isn't used in a enterprise or business environment. The hardware I use is what I had lying around and has worked well and lends itself to my education. I accept there is a greater chance of things not performing as they should or going wrong. That's how we learn. Consequently I do take backups of the data stored in FreeNAS.
   
   The motherboard is an ASUS P5WD2 Premium, All hard drives are Seagate. The mirrored pair are 1TB each, The Raid are 3 x 2TG

So,

• what is the correct way I should have followed to try and correct this problem
• might it be possible to recover the data on the disks
• why does FreeNAS show everything as OK but the "faulty" disk in question show
  
  Feb 28 10:56:51 FreeNAS smartd[3708]: Device: /dev/ada0, 6 Currently unreadable (pending) sectors
  Feb 28 10:56:51 FreeNAS smartd[3708]: Device: /dev/ada0, 6 Offline uncorrectable sectors

All disk are configured, Always On, Advance Power disabled, Acoustic Level Disabled, SMART Enabled

Many thanks

 

[Mirfster]

No I haven't virtualized FreeNAS. iSCSI, again started out of curiosity to see how difficult it was to setup and how reliable it could be using bare minimum spec. For me, with the hardware I had to hand it has just worked. I have continued to use it as it meant I could include the drive in windows search on my server without all the mucking about I would have to go through to achieve the same thing without iSCSI.

I am no iSCSI expert, but from my understanding trying to run iSCSI with just 8 GB of RAM is not a good decision at all. If this is all the hardware you have, then I would suggest you forget iSCSI and use CIFS. There are other ways to include networked folders in Windows Search (but I don't have a reference right now)

Feb 28 10:56:51 FreeNAS smartd[3708]: Device: /dev/ada0, 6 Currently unreadable (pending) sectors
Feb 28 10:56:51 FreeNAS smartd[3708]: Device: /dev/ada0, 6 Offline uncorrectable sectors

When is the last time you performed a SMART Long test on this drive (or any for that matter)?

All hard drives are Seagate

Sorry to hear about that... ;)

If you are hard-set on using iSCSI, then I would recommend that you have a looksy at jgreco's "Why iSCSI often requires more resources for the same result"

 

[Mirfster]

Just an add on..

Per your Motherboard Specs, it supports both ECC and Non-ECC Ram. Since you have not really told use what RAM you have there is a chance you are running Non-ECC.

Same goes for your processor, you simply state "Intel Dual Core Processor 3GHz". In order to support ECC RAM, the CPU must also support it.

As part of my learning curve can someone explain the correct way I should have followed to try and correct this problem and if I can recover the data on the disks?

FreeNAS for me started out of curiosity then ended up being stable and useful from the outset.

This is seen quite often, where an "Experiment" ends up being converted to "Production". If you really intend to use FreeNas as designed and house important data, please take the appropriate time to do things the correct way (not saying you didn't; but your hardware specs are "questionable"). I understand that you have backups (which is great), so perhaps more effort should be put into getting a solid foundation built instead? If this is still just an "Experiment", then data loss should not be a major concern.

Last note, it appears to me that you have been running this "Experiment" for quite some time (UFS raid degraded - help please) maybe; just maybe it is not such an experiment any longer? ;)

 

[berrick]

@Mirfster

There are other ways to include networked folders in Windows Search

I would be interested in your suggestion. All ways I have tried didn't work for my particular requirements. Whereas iSCSI as a disk in server 2008R2 and shared works great.

If you are hard-set on using iSCSI, then I would recommend that you have a looksy at jgreco's "Why iSCSI often requires more resources for the same result"

I'm not hard set on using iSCSI I read this and other info in the forum and understand I'm not really using enough RAM etc. But as I have said so far it has worked really well and is fast enough for the environment it is being used. That being said I would rather not use iSCSI given the lack of resource and the info imparted in such posts.

Anyways, might someone offer meaningful answers to the following?

• when setting up iSCSI in FreeNAS is it still the case that using auto for the Extent size is a no no
• might it be possible to recover the data on the disk in windows
• why does FreeNAS show everything as OK but the "faulty" disk in the cli

 

[berrick]

This is the results of the last smart test today.

Not sure how to read the data it contains but I guess it confirms a dodgy read at the sector and cylinder shown in the Error output?

smartctl 6.1 2013-03-16 r3800 [FreeBSD 9.1-STABLE amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.12
Device Model:     ST31000524AS
Serial Number:    5VPCMQ98
LU WWN Device Id: 5 000c50 0532d095b
Firmware Version: JC4A
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Feb 28 18:00:15 2016 GMT
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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      ( 115) The previous self-test completed having
                                        the read element of the test failed.
Total time to complete Offline
data collection:                (  609) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 171) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
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   108   099   006    Pre-fail  Always       -       18857382
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       151
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       65022904
  9 Power_On_Hours          0x0032   066   066   000    Old_age   Always       -       30531
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       147
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   079   079   000    Old_age   Always       -       21
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       2
189 High_Fly_Writes         0x003a   099   099   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0022   083   049   045    Old_age   Always       -       17 (Min/Max 11/18)
194 Temperature_Celsius     0x0022   017   051   000    Old_age   Always       -       17 (0 7 0 0 0)
195 Hardware_ECC_Recovered  0x001a   027   022   000    Old_age   Always       -       18857382
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       6
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       147424752466062
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1615732789
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       4207406589

SMART Error Log Version: 1
ATA Error Count: 11 (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 11 occurred at disk power-on lifetime: 30412 hours (1267 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  26d+04:25:09.096  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:09.095  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:09.094  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:09.093  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:09.093  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 30412 hours (1267 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00  26d+04:25:06.174  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:06.174  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:06.174  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:06.174  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:06.174  READ FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 30412 hours (1267 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00  26d+04:25:03.285  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:03.285  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:03.285  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:03.285  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:03.285  READ FPDMA QUEUED

Error 8 occurred at disk power-on lifetime: 30412 hours (1267 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00  26d+04:25:00.350  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:00.350  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:00.350  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:00.350  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:25:00.350  READ FPDMA QUEUED

Error 7 occurred at disk power-on lifetime: 30412 hours (1267 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
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 10 ff ff ff 4f 00  26d+04:24:57.466  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:24:57.465  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:24:57.465  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:24:57.465  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  26d+04:24:57.465  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       30%     30530         1478076070
# 2  Short offline       Completed without error       00%     10483         -
# 3  Short offline       Completed without error       00%     10481         -
# 4  Short offline       Completed without error       00%     10479         -
# 5  Short offline       Completed without error       00%     10477         -
# 6  Short offline       Completed without error       00%     10475         -
# 7  Short offline       Completed without error       00%     10473         -
# 8  Short offline       Completed without error       00%     10468         -
# 9  Short offline       Completed without error       00%     10466         -
#10  Short offline       Completed without error       00%     10464         -
#11  Short offline       Completed without error       00%     10462         -
#12  Short offline       Completed without error       00%     10460         -
#13  Short offline       Completed without error       00%     10458         -
#14  Short offline       Completed without error       00%     10456         -
#15  Short offline       Completed without error       00%     10454         -
#16  Short offline       Completed without error       00%     10452         -
#17  Short offline       Completed without error       00%     10450         -
#18  Short offline       Completed without error       00%     10448         -
#19  Short offline       Completed without error       00%     10446         -
#20  Short offline       Completed without error       00%     10444         -
#21  Short offline       Completed without error       00%     10442         -

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.

 

[Mirfster]

Reference: https://en.wikipedia.org/wiki/S.M.A.R.T.

I think you are showing potential issues due to:

Code:

187 Reported_Uncorrect      0x0032   079   079   000    Old_age   Always       -       21
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       6

However, I will defer to those who are more versed in SMART results...

 

[DrKK]

Reference: https://en.wikipedia.org/wiki/S.M.A.R.T.

I think you are showing potential issues due to:

Code:

187 Reported_Uncorrect      0x0032   079   079   000    Old_age   Always       -       21
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       6

However, I will defer to those who are more versed in SMART results...

non-zero values for 187, 197, and 198 are often indicative of early failure modes.

Personally, if I have any number but zero in any of those attributes, I immediately replace the drive.

 

[DrKK]

Oh, Seagate Barracuda. Should be considered broken out of the box.