JonathanM

Put in a new drive, and let unraid rebuild onto the new drive from the rest of the drives. Unraid is handling it gracefully, it's allowing you to run with one drive failed, and will rebuild the contents on the new drive when you put it in. It's possible that the drive is still ok, could be power or sata connection, but as of right now, the contents of that physical drive isn't relevant, as unraid has been emulating it using parity ever since a write to it failed. You can try rebuilding it onto itself, but if I were you, I'd put in a new tested drive, and run diagnostics on the old drive after the array is healthy again.

However... if you enable the new reconstruct-write mode discussed here, you can at least get back to single disk speed instead of being limited by the current parity overhead. Dang, ninja'd by Weebo

Just be aware that guide is rather old.

http://lime-technology.com/forum/index.php?board=31.0

Type ifconfig at the command prompt on the unraid machines console.

Read here and here for a good start.

He didn't give you a lecture, he gave you the honest downsides to not upgrading. If those downsides outweigh the upsides of no change for you, then by all means, don't upgrade. Your original question was "Is there any reason not to upgrade", and to be fair, he addressed that question by providing the cons to not upgrading, instead of the pros to upgrading that you apparently wanted him to give you. If you are asking for bona-fides before weighing peoples opinion, then mine is obviously worthless because I'm a linux / windows guy still running unraid 4.7 because it "just works". I have no experience with mac and unraid 5.x, so just ignore everything I just said.

A private tracker combined with DHT being disabled on the torrent would virtually eliminate normal attack vectors. It could be set up in such a way that only a running unraid server could be authenticated as a peer, and the authentication could be linked to the license. That way, if you choose to enable the built in torrent updater, you would only be able to connect to the limetech tracker, and only download and share limetech approved files.

Sounds like you are getting shaken down. There probably is not going to be a happy ending. Hopefully you still have the preclear reports that at least will have smart status recorded with the serial numbers. Email a copy to the buyer, and tell them "sorry, but they were shipped to you exactly as I represented in the auction".

Have you tried from different machines and / or browsers? I've seen overprotective antivirus suites block access.

What exactly did you type on the command line?

Many disk browsers access the files to determine file type and display thumbnails.

That behaviour is exactly what the drive manufacturer intended, only it's happening much too quickly. As long as there are still spare sectors available, the drive will continue to test "good". Problem is, with the rate of increase you are seeing, you may be out of spares in a matter of hours. Until a write to it fails, unraid will keep it online and green.

Before you start doing major hardware replacement troubleshooting, try preparing another usb key with the free version of unraid, just don't assign any of your current array drives. You can install and run unmenu on the new key without any array drives, and that should be a good test of whether it's the usb on the board, or your key that is causing the issues. When my 1st key died, I saw similar behaviour, where it would boot ok, but after a period of time, the usb drive basically just disappeared from the system. Unfortunately, the blank monitor symptom makes me think it may be the motherboard, CPU, or RAM, but who knows, you still could get lucky.

Hopefully it's just your USB key that's having issues, not the motherboard. Try to make a full backup of your USB key with another PC, and run a disk check on it.

http://malwaretips.com/blogs/www1-dlinksearch-com-removal/

Of which about 7% is courtesy of Joe L.

Which process shows high CPU usage when you run the top command at the console?

As long as all your drives are error free, it's no big deal. Just assign ALL the drives to data slots, MAKE SURE THERE IS NO PARITY DRIVE ASSIGNED, and start the array. All the data drives should mount just fine, and be browsable. There should be one drive that shows unformatted, that's your parity disk. Make a note of which drive should go where, stop the array, set a new config (with 4.7 it's a command line thing) and assign all the drives to the correct slots, being very sure which is the parity drive. Start the array, and it will recalculate parity and write it to the drive that you assigned. If you think you may have a failed drive, don't do this. It will eliminate any possibility of recovering it. Data drives can be assigned to any slot, it's only after the array is up and healthy with calculated parity that it becomes important not to change slots in 4.7.

If you are using Simplefeatures or the updated webgui, remove it.

Are the symptoms the same on all the client machines, or just the PC in your original post?

Long story short, don't worry about changing anything on your existing drives. Set the default to 4K aligned, and be happy. The drives will coexist just fine.

Chromecast doesn't appear to be supported yet, but people are asking for it. Here is the official list on the plex site.

Some smart TVs can connect directly to Plex, and there are several small media players as well.

Oh. I figured the first post in the thread could always change the title. Learn something new everyday.