ATA error count increased, device experienced unrecoverable error

[koberulz]

Woke up to both of these:

Pool MainStorage state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

Device: /dev/sde [SAT], ATA error count increased from 0 to 1.

SMART results from sde:

Code:

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD201KFGX-68BKJN0
Serial Number:    2LGA639K
LU WWN Device Id: 5 000cca 2b3c4a2a2
Firmware Version: 83.00A83
User Capacity:    20,000,588,955,648 bytes [20.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-5 (minor revision not indicated)
SATA Version is:  SATA >3.3 (10), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Sep  7 13:18:36 2023 AWST
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  101) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (2220) minutes.
SCT capabilities:              (0x003d) 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     0x000b   094   094   001    Pre-fail  Always       -       39452672
  2 Throughput_Performance  0x0004   148   148   054    Old_age   Offline      -       50
  3 Spin_Up_Time            0x0007   083   083   001    Pre-fail  Always       -       359 (Average 356)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       41
  5 Reallocated_Sector_Ct   0x0033   100   100   001    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000a   100   100   001    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0004   140   140   020    Old_age   Offline      -       15
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       8195
 10 Spin_Retry_Count        0x0012   100   100   001    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       41
 22 Unknown_Attribute       0x0023   100   100   025    Pre-fail  Always       -       6553700
 90 Unknown_Attribute       0x0031   100   100   001    Pre-fail  Offline      -       231928233984
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       381
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       381
194 Temperature_Celsius     0x0002   049   049   000    Old_age   Always       -       45 (Min/Max 18/60)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
        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 1 occurred at disk power-on lifetime: 8186 hours (341 days + 2 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 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 80 50 c0 a3 8e 40 08  40d+03:56:53.569  READ FPDMA QUEUED
  61 20 60 e8 96 a6 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 08 58 d8 96 a6 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 30 08 d0 c6 83 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 18 38 20 ce e2 40 08  40d+03:56:51.018  WRITE FPDMA QUEUED

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%      8181         -
# 2  Short offline       Completed without error       00%      8157         -
# 3  Short offline       Completed without error       00%      8133         -
# 4  Short offline       Completed without error       00%      8110         -
# 5  Short offline       Completed without error       00%      8085         -
# 6  Short offline       Completed without error       00%      8061         -
# 7  Short offline       Completed without error       00%      8037         -
# 8  Short offline       Completed without error       00%      8013         -
# 9  Short offline       Completed without error       00%      7989         -
#10  Short offline       Completed without error       00%      7965         -
#11  Short offline       Completed without error       00%      7941         -
#12  Short offline       Completed without error       00%      7917         -
#13  Short offline       Completed without error       00%      7893         -
#14  Short offline       Completed without error       00%      7869         -
#15  Short offline       Completed without error       00%      7845         -
#16  Short offline       Completed without error       00%      7821         -
#17  Short offline       Completed without error       00%      7797         -
#18  Short offline       Completed without error       00%      7773         -
#19  Short offline       Completed without error       00%      7749         -
#20  Short offline       Completed without error       00%      7725         -
#21  Short offline       Completed without error       00%      7701         -

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.

I don't really know how to read that, but from what I can find via Googling it seems okay?

It's part of a 4-disk RAIDZ2 pool, I have an additional 2-disk mirrored pool. WD Red 20TBs all 'round, running off an ASUS Prime B660M-A motherboard, intel Core i3 12100, Cooler Master MWE 1250W power supply, 16GB DDR4 RAM, and a couple of LSI 9211-8i cards. Not sure what other info might be pertinent.

 

[Jailer]

Run a long test on that drive and report back with the results.

 

[koberulz]

Well that's going to take a couple of days to finish, but I just got another alert...

Device: /dev/sde [SAT], 8 Currently unreadable (pending) sectors.

Device: /dev/sde [SAT], Self-Test Log error count increased from 0 to 1.

That...doesn't seem good.

It's set to long-test on the first of each month, so I assume it had a clean bill of health then, right? It hasn't been hiding this issue?

 

[koberulz]

So in terms of replacing...I have to send it back before getting a new one, but I assume that's no big deal since it's not functioning anyway? Is there anything I need to keep in mind in terms of replacing it? How does it know which drive is which in the array, do I need to make sure I plug it in with the same SATA cable?

 

[Etorix]

That...doesn't seem good.

Indeed… You can run a long SMART test now, even while the drive is in use in the pool.
smartctl -t long /dev/sde from any console (including the web UI console).

So in terms of replacing...I have to send it back before getting a new one, but I assume that's no big deal since it's not functioning anyway? Is there anything I need to keep in mind in terms of replacing it? How does it know which drive is which in the array, do I need to make sure I plug it in with the same SATA cable?

This depends on how WD handles the RMA. Results from the SMART test may help justifying the RMA, and WD might (but need not) agree to send the replacement in advance.
Where and to which cable drives are connected is irrelevant.

 

[joeschmuck]

Device: /dev/sde [SAT], Self-Test Log error count increased from 0 to 1.

Nope that is not good. Try to run smartctl -a /dev/sde and if the test has already stopped, it will display the full output (like above) and look in the testing section to see if the long test failed. If it did, RMA the drive, that alone is a solid failure. If the test has not completed then wait until it does and get the report.

It doesn't look like you run routine SMART Long tests. I recommend weekly Long tests and daily Short tests. Too many users are finding out they are having bad drives only when data errors start showing up.

 

[koberulz]

It doesn't look like you run routine SMART Long tests.

As above:

It's set to long-test on the first of each month, so I assume it had a clean bill of health then, right? It hasn't been hiding this issue?

 

[joeschmuck]

In my book, monthly Long tests are not enough, but that is my opinion. Everyone has an opinion. Whatever works best for you is what counts, but you now know my opinion.

 

[koberulz]

In my book, monthly Long tests are not enough, but that is my opinion. Everyone has an opinion. Whatever works best for you is what counts, but you now know my opinion.

Well in this circumstance, the monthly test finished less than a week before the issue cropped up, so it makes no difference.

Given it takes two days to test one disc, testing six discs weekly seems excessive, no? It'd be running tests 24/7.

 

[koberulz]

No idea how to tell if the test is still running - it did want until tomorrow morning when I set it up - but here's the smartctl output at present:

Code:

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD201KFGX-68BKJN0
Serial Number:    2LGA639K
LU WWN Device Id: 5 000cca 2b3c4a2a2
Firmware Version: 83.00A83
User Capacity:    20,000,588,955,648 bytes [20.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-5 (minor revision not indicated)
SATA Version is:  SATA >3.3 (10), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Sep  8 18:05:35 2023 AWST
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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (  101) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (2220) minutes.
SCT capabilities:              (0x003d) 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     0x000b   095   095   001    Pre-fail  Always       -       10486084
  2 Throughput_Performance  0x0004   148   148   054    Old_age   Offline      -       50
  3 Spin_Up_Time            0x0007   083   083   001    Pre-fail  Always       -       359 (Average 356)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       41
  5 Reallocated_Sector_Ct   0x0033   100   100   001    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000a   100   100   001    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0004   140   140   020    Old_age   Offline      -       15
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       8223
 10 Spin_Retry_Count        0x0012   100   100   001    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       41
 22 Unknown_Attribute       0x0023   100   100   025    Pre-fail  Always       -       6553700
 90 Unknown_Attribute       0x0031   100   100   001    Pre-fail  Offline      -       231928233984
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       382
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       382
194 Temperature_Celsius     0x0002   046   046   000    Old_age   Always       -       47 (Min/Max 18/60)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 1
        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 1 occurred at disk power-on lifetime: 8186 hours (341 days + 2 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 43 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  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 80 50 c0 a3 8e 40 08  40d+03:56:53.569  READ FPDMA QUEUED
  61 20 60 e8 96 a6 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 08 58 d8 96 a6 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 30 08 d0 c6 83 40 08  40d+03:56:51.019  WRITE FPDMA QUEUED
  61 18 38 20 ce e2 40 08  40d+03:56:51.018  WRITE FPDMA QUEUED

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%      8205         -
# 2  Extended offline    Completed: read failure       90%      8200         4500928
# 3  Short offline       Completed without error       00%      8181         -
# 4  Short offline       Completed without error       00%      8157         -
# 5  Short offline       Completed without error       00%      8133         -
# 6  Short offline       Completed without error       00%      8110         -
# 7  Short offline       Completed without error       00%      8085         -
# 8  Short offline       Completed without error       00%      8061         -
# 9  Short offline       Completed without error       00%      8037         -
#10  Short offline       Completed without error       00%      8013         -
#11  Short offline       Completed without error       00%      7989         -
#12  Short offline       Completed without error       00%      7965         -
#13  Short offline       Completed without error       00%      7941         -
#14  Short offline       Completed without error       00%      7917         -
#15  Short offline       Completed without error       00%      7893         -
#16  Short offline       Completed without error       00%      7869         -
#17  Short offline       Completed without error       00%      7845         -
#18  Short offline       Completed without error       00%      7821         -
#19  Short offline       Completed without error       00%      7797         -
#20  Short offline       Completed without error       00%      7773         -
#21  Short offline       Completed without error       00%      7749         -

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.

 

[Jailer]

You had a read failure on your long smart test. That's enough to get an RMA started. I'd get on it sooner rather than later.

 

[koberulz]

You had a read failure on your long smart test. That's enough to get an RMA started. I'd get on it sooner rather than later.

Was already onto it last night after that first alert. Which brings me back to my earlier questions about the actual physical process of removing and replacing the disk.

 

[Etorix]

Hopefully your earlier questions have been answered above ;)
Being able to replace a drive on short notice is why it is advised to have some burnt-in cold spare(s) at hand—in which case the replacement drive would become the next cold spare and it does not matter whether WD would agree to send the replacement drive ahead.

 

[koberulz]

Sorry, I somehow missed your earlier post.

Unfortunately my budget doesn't even really stretch to the drives I already have, to be honest, never mind hot spares (or cold spares, or any other spares). And yeah, WD wants the drive back before they'll send a replacement.

 

[joeschmuck]

WD offers an Advance Replacement program I believe, but they need a credit card to charge in case you do not ship back the failed drive. I like the Advanced RMA a lot. i assume they still have it, I haven't needed it in several years.

 

[joeschmuck]

Given it takes two days to test one disc, testing six discs weekly seems excessive, no? It'd be running tests 24/7.

I guess it's perspective. My advice is to test each drive daily for the Short and weekly for the Long tests, that is just my opinion and friendly advice. Others may have different opinions and that if perfectly fine. But as you can see, the Long test found the problem during the test vice during a Scrub or data request.

If you test all the drives at once then you will be completed in 2 days (~37 hours actually). You could setup to run one disk each night (Mon, Tue, Wed, Thu, Fri, Sat) to reduce some heat build up, and to make your pool more responsive to data transfer. But a SMART test should stop during a data request and then keep going once the request is complete. This means that the test time overall will take longer due to the pauses.

If you want shorter test times, you would need to install smaller capacity drives, but most people would not do that since they already purchased the drives. Sounds reasonable to me.

Which brings me back to my earlier questions about the actual physical process of removing and replacing the disk.

Read the TrueNAS User Guide, it is very good on this topic, much better that us retyping it all.

 

[koberulz]

WD offers an Advance Replacement program I believe, but they need a credit card to charge in case you do not ship back the failed drive. I like the Advanced RMA a lot. i assume they still have it, I haven't needed it in several years.

Might be different in Australia, but they've clearly stated they require the drive back.

Read the TrueNAS User Guide, it is very good on this topic, much better that us retyping it all.

The guide assumes the new disk is in hand, which it isn't, and assumes the pool is degraded, which it isn't. But I'm assuming it's all the same: offline sde, remove the disk, send it back, get the new disk, plug it in (anywhere?) and then do the replacement. Should be okay to continue using the NAS in the meantime? It's Z2, so I do still have a redundancy in place.

But as you can see, the Long test found the problem during the test vice during a Scrub or data request.

Is "vice" a typo here? I don't understand what you're saying.

I already had daily Shorts set. I've switched the Longs to weekly. Although again, unless it failed the previous SMART and just didn't notify me, I discovered the issue within five days of a passed Long, so it would've made no difference in this case.

 

[joeschmuck]

"vice" meaning instead of.

I would not remove the suspect drive until you have a replacement drive in hand. I understand that can be a problem for many people due money or availability of the parts. But it is best practice. Did you ever state the configuration of your pool? This is very important because for argument let's say you have a Stripe (I don't think you do but it's the easiest example), and you remove the failing drive, well all your data is gone. If you have a RAIDZ1, pull the drive, run the system and another drive fails, there goes your data. So keep that in mind, and you may already know this stuff.

If you feel your data could be at risk, Back it up first! At least the stuff that is really important to you. This is always a smart thing to do before replacing a drive for most of our home users due to the high probability of an unfortunate incident like pulling the wrong drive. It happens all too often which is why we say, Use the Serial Number always.

I already had daily Shorts set. I've switched the Longs to weekly. Although again, unless it failed the previous SMART and just didn't notify me, I discovered the issue within five days of a passed Long, so it would've made no difference in this case.

SMART was an attempt to create a algorithm that would project that the drive will likely fail within the next 24 hours, meaning it could be in a few minutes or 24 hours. It's not perfect but it's what we have. The best test in SMART is the Long test because it does check the basics just like the short test but it also include a complete non-destructive scan of the entire hard drive surface.

SMART overall-health self-assessment test result: PASSED

Do not believe this for one second that this is the true status indicator of your drive. This only says that the electronics, motor, platters, and heads completed a basic test during power up. Some drives will test periodically as well but I have never seen a bad drive that didn't still say "PASSED".

Some failures are motor control circuits in which you might hear a constant head ticking as the drive motor may be spinning the platters but it doesn't keep the speed at the correct RPM. Or the motor doesn't spin at all. These are usually occur during a power on event.

The best defence here is to test the drives often. If you sleep your drives then yo need to figure out the least impact to your system. For example if you spin your drives down over the weekend, then I would not schedule a test for the weekend. I would test when the drives are operational/expected to be spinning. Some people sleep the drives all week long until the create a computer backup and this it all comes to life. If you know the backup take XX hours and your drives don't sleep until 5 hours of inactivity, then you can schedule the test while the drive is still spinning to mitigate spinning up events.

Sorry for getting long in the tooth, I can get that way at night. I hope something here has helped you in some way. Good luck.

 

[koberulz]

Did you ever state the configuration of your pool? This is very important because for argument let's say you have a Stripe (I don't think you do but it's the easiest example), and you remove the failing drive, well all your data is gone. If you have a RAIDZ1, pull the drive, run the system and another drive fails, there goes your data. So keep that in mind, and you may already know this stuff.

It's Z2, so I do still have a redundancy in place.

Do not believe this for one second that this is the true status indicator of your drive. This only says that the electronics, motor, platters, and heads completed a basic test during power up. Some drives will test periodically as well but I have never seen a bad drive that didn't still say "PASSED".

I'm not sure where this fits into the bigger picture.

The best defence here is to test the drives often. If you sleep your drives then yo need to figure out the least impact to your system. For example if you spin your drives down over the weekend, then I would not schedule a test for the weekend. I would test when the drives are operational/expected to be spinning. Some people sleep the drives all week long until the create a computer backup and this it all comes to life. If you know the backup take XX hours and your drives don't sleep until 5 hours of inactivity, then you can schedule the test while the drive is still spinning to mitigate spinning up events.

It's a media server, I have it running 24/7 more or less.

As I said, I've now switched the Longs to run weekly.

 

[koberulz]

I've tried offlining the disk, but nothing happens. I get a spinning circle for a couple of seconds, then it disappears. No change in disk status, no error message, nothing.