dgaschk

2016.12.24 works. Sent from my iPad using Tapatalk

I'm getting failure too. I tried using 1.15 and it reports "sdo" in use and fails immediately. I updated and am running again. Sent from my iPad using Tapatalk

There are several documents you can find on the internet. For example this one Does the manufacturer of the example drive provide this type of document? The whole point with value and threshold is that a notification is only needed when the value is equal or below the threshold. A decreasing value as such doesn't mean there is an issue. There are several things that can be watched. The FAILED column and the overall health. SMART overall-health: Passed Watches on the RAW values that RobJ mentioned would be nice. Allowing the User to select attributes for RAW value watch could be helpful. We could notify when a normalized VALUE has decreased by more than a configurable percentage over a configurable amount of time or present the amount of the time over which the drop occurred. This config should be available each attribute.

Do you have a reference for this? How does this prevent notification on the change of a value? I'd expect those 100 VALUES to decrease as the drive ages. The vendor is free to implement SMART as they see fit.

Yes. The VALUES should decrease as the the drive ages. If any one of them reaches zero SMART will FAIL. Note that there is a worst column because the VALUE may decrease or increase at any time.

reiserfsck --rebuild-tree /dev/md9

This is possible.

What makes you say this? A threshold of 00 if means that the threshold is zero. Most attributes have a 0 threshold since the scale is arbitrary. As long as the normalized VALUE is above the THRESH the attribute PASSes.

Need help? Read me first!

Collect a diagnostics file before a system reset. Attach to zip file. See here: Need help? Read me first!

The drive is dead. You may be able to recover a portion of its contents. Do not use this drive for any other purpose. It has failed and only appears to be a hard drive. It is no longer a hard drive. Do not attempt to to use it as one.

Restore the origional go file and unMENU will disabled.

It will likely be slow than doing them in sequence if writes are involved. But shouldn't be an issue.

It changes the parity update algorithm so that writes are faster but all array disks are accessed during a write. This trades power consumption for improved write performance. The standard method only accesses the target data drive and the parity drive, albeit each one twice.

Select SAFE-mode from the boot menu.

It's been a while since there's been a coupon code. The last one was a discount for 2 keys. Lime should make a plugin that gives a key code on occasion or if certain conditions are met.

New file writes can go to the cache. Existing files are modified in place.

If you add a video card,I think Jon P has made some tutorials on unraid w/openelec.

Stop array. Un-assign disk. Start array. Stop array. Assign disk. Start array.

The copy will fail if the drive fills in the middle of a file transfer. If the min free space has been exceeded before the file transfer starts then the cache will be bypassed.

See check disk file systems in my sig. Replace the red drive if you have a spare. Post a smart report for the current red drive.

Select Safe-mode from the boot menu. Does the issue persist?

See console commands in my sig.

Tools->Diagnostics. Attach zip file.

Make user specific shares. Each user can write only in one share but can read all of the others.