JonathanM

There is no widely used hot spare option. Anything like that would need to be set up yourself. The whole point of the current set up is that writes to the USB drive are few and far between, so regular backups are a better option than a hot mirror. If something screws up the USB, you would be better off with the last known good backup instead of mirroring whatever corruption occurred to screw up the USB. Unraid the OS runs pretty much entirely from RAM, and is "reinstalled" fresh every boot anyway. Any customizations will need to be configured to be redone at boot, typically called from the go file.

However, testing the drive in another system uncovers drive errors only. This can be good or bad, depending. If you have a controller, RAM, or PSU issue in the server it can effect preclear results as well. Ideally you should get a clean preclear cycle in the exact circumstances that the drive will be used in the server.

The ability to safely launch it from MyMain would be great. I use a combination of the email notifications and the MyMain page to check preclear status currently.

Are you planning on working with Joe to integrate this with his work, or are you going to rewrite the whole thing to be your supported version? There have been a whole lot of people wanting a browser integrated plug in version of preclear for a long time.

Does this new method reduce the amount of work that the drive is asked to do? I was under the impression that the slowness of the preclear was on purpose to thoroughly test all parts of the drive possible in a reasonable period of time. Pseudo random seeks and other stuff to really work it hard. Here is a quote directly from Joe.

And here is the issue. UNRAID AUTOMATICALLY STARTS A CORRECTING PARITY CHECK AFTER A CRASH. It doesn't give you the option to evaluate the situation before it starts writing data to the parity disk.

I have personally lost data because of a correcting parity check. I have tried to stress the importance of NOT writing ANYTHING to the disks if you suspect there is a problem until you know the nature of the problem. I really wish there was a way to boot the array to a diagnostic mode that there would be no writes of any sort, read only for all data. This topic has been debated to death in the past, and suffice it to say, in an ideal world where the disks and controllers behave as designed when an error is detected, a correcting parity check is the correct action. If something isn't behaving as it should, you can easily get into a situation where you really don't want to write to a drive without running further diagnostics.

Just be sure you can only plug safe loads into it. You wouldn't want a power drill, vacuum cleaner, hair dryer, etc killing your UPS... This UPS can handle it. It's a Powerware Prestige 9 2KVA, and the output is 16 Amps. It has no problem with laser printers, etc. Yes, it will handle a Dyson vacuum cleaner.

Heh, I ran the outlet in my study to a iec male socket in the server room instead of the breaker box, and just used a standard PC power cord from the UPS to the iec socket. That way all the battery backups are in one room with the server, and I have a battery backup protected outlet without the bulk and noise in the main area of the house.

Just want to remind people thinking about doing this to remember to put your ethernet switch and router on battery backup as well.

Depends. dnsmasq can provide several different services. If you don't enable conflicting overlapping services, you should be fine.

The manual says it should be there, Legacy LAN as a boot option. Perhaps you may have to use the other network port?

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

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

Yes.

Any location other than /boot/* or /mnt/* in a stock unraid install is on a RAM drive.

If you are only using it for short periods, power consumption isn't a concern. Just throw together the cheapest box you can, use your castoff smaller hard drives, whatever gets you a current backup. Do it sooner rather than later. I deal with people on a regular basis that all say, I was planning on backing it up, but I never got around to it. Data recovery is VERY expensive in some cases, you could put together a very nice 20TB unraid server for the average price of an expedited clean room recovery.

Darn, there goes your streak of sub 1 hour response times.

So basically you create an account and add all of the storage resources you wish to make accessible from the interface (even drobbox accounts) when you install the client on your computer I'm trying to be diplomatic here, but it really sounds like xlordnashx is a salesman from this sme place. He doesn't even listen to the valid point made here, in that sme would have to have all your account details from your other existing accounts that you want to use. Sounds like a security nightmare waiting to happen. I'm genuinely curious here, xlordnashx, what unraid version are you currently running?

If you use the official lime logo and unraid text, you may be violating trademark. Not saying you can't get them made, just that it's not nice, and may not be legal where you live. You really need to get Tom's permission before doing it.

If you did add the preclear signature without clearing the disk, you would definitely corrupt any subsequent disk rebuilds until a full correcting parity check was run. Is the data on your other disks important to you?

You can't just cut the power on the unraid server, i assume you're using a UPS in this scenario, which will do a clean powerdown when you cut power. Besides the fact that you are abusing the UPS this way, there is a bigger risk. Normally, in case of a power loss, you not only want to powerdown the unraid server in a clean way ASAP, but after that is done, also shutdown the UPS. If you don't, in case the power returns for like a minute or a few seconds and powers down AGAIN, you will be in the middel of starting up your unraid server again (because your using 'resume on powerloss') and you can't do a nice powerdown since the UPS probably is empty or near empty... this is why you do NOT want to resume on powerloss. Just stay off. So, do not use the UPS as a handy on/off switch... it's an emergency device, treat it as such. While I fully agree with what you said regarding a UPS, that is not what was being recommended. Nowhere in the original post was UPS mentioned, but it should have been. The timer use case would be directly on the server power cord, on the OUTPUT of the UPS, not the wall side of the UPS. I agree that a UPS should always be used with a server, and the original suggestion should have made clear which SIDE of the UPS the timer should be controlling. With a properly sized and controlled UPS, resume on powerloss can be applied with minimal risk.

If you have a PCI ethernet card, I'd try that and turn off the motherboard ports. Realtek ethernet support seems to be spotty at best. Intel based cards usually work better.

The link in http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246 this post works fine for me. Which post are you referring to?