JonathanM

Uninstall (not just disable) your security suite temporarily. I have seen multiple instances of aggressive firewalls blocking web servers that are inside the LAN.

Three rows of 5 holes each. Serial ports have two rows.

So jump on the $30 for an extra key, and when you have time / money build another box. Drive sizes and media accumulation for many users mean you need the equivalent of a new server every few years anyway, so leave your current server intact and build a new one from scratch the way you want it.

Best guess is the share settings are still set to cache only.

I'm just very glad that the power supply refused to run with the wrong cables, I was afraid you had sent 12V to the 5V line on your drives and fried the hard drive controller boards. It's great that everything turned out ok.

The power thing isn't really an unraid issue, but we'll still be glad to help. The general support forum is fine for this kind of stuff. First, unless you really did fry your hard drives, you will be able to read them in any system that can read reiserfs. The easiest way to do that is to set up another machine to temporarily boot unraid and set it up as a server with only unraid data disks. As long as you don't assign any disks to the parity slot, you can read them as disk shares without fear of wiping the contents out. Just make sure you unplug any disks that weren't part of your unraid array. As to what's going on with your current case, motherboard and PSU, I would go back to the basics to troubleshoot. You say you have a modular supply, so you haven't been unplugging the disk end. Not all modular supplies use the same setup, cables that work on one may not work on another. I think you need to unplug ALL the disk and fan connections, and start over using the new power supply and matching cables with just a single drive, and see if it powers up. If so, add another drive, etc, until you find the culprit. I would pull the unraid USB key and set it aside, just see if you can get the system to give you a boot screen. If you can get all your drives to spin, then put the USB back and let it come up all the way.

I would be worried, but only if the reallocated sectors is ramping up. If that drive has had those 33 sectors for many months with no increase, then I'd feel a little better. If the 33 just showed up in the last month or so, I'd replace the drive. The raw numbers aren't as meaningful without a rate of increase included.

Since the array is stopped, and you have access to unmenu, I'd try restarting the machine using unmenu.

According to this post, the O is supposed to be gone, but apparently there are side effects, such as what you are seeing.

Maybe this bug (or a variant) is back?

Are you sure about that?

As long as the server itself doesn't need access, I'm cool with that. As it is right now, you can do the whole license thing with a smart phone, as long as you can write a binary file from the phone to external media of some sort.

You need to set up a VPN, as unraid is not secured to be exposed to the internet.

That is not the case at all. Worst case scenario in a usb key failure is either waiting a few hours to get a new key from Tom, or just use the free version to access a couple drives at a time in a non-protected temp array. Your drives are still accessible, and the machine is still usable. You are blowing the USB key limitation way out of proportion.

It's not static buildup in the air, it's an EMP event. Any length of wire that passes through a magnetic field or a magnetic field passes through it will have a voltage generated along it. That is how transformers, and generators work. In the case of a lighting strike, a huge "wire" is momentarily created from the cloud to the ground, the electricity gets dumped along that wire, and as it passes, a huge magnetic field is created and dies. Any wire nearby will have a voltage generated on it. If one end of that wire isn't grounded, the voltage will seek the easiest way to get to ground, usually frying anything in its path. Most telephone and cable modem lightning damage occurs because the lightning hit a power pole and travelled alongside the telephone or cable conductor until it got to ground. The telephone or cable line rarely takes a direct hit, it's almost always induced current.

I think you may have a winner. The ballast in that old lamp is a BIG coil transformer type affair. The surge created from turning it on and off is not well isolated from the PC, since it's on the same surge protector. Try running that lamp straight to the wall outlet and see if it still interferes, if so, get rid of it, or leave it on all the time. Most modern fluorescent lamps are much better behaved, they use electronic ballasts that don't use huge magnetic coils.

Unraid will not move already existing files. Does the drive that the file is currently on have plenty of space left?

It's slow BECAUSE the drive is failing.

I'm betting that it would be faster to remove the drive and run at risk. I'm not recommending that, just stating an opinion. What I'm recommending is replace that drive ASAP. If you have another drive fail right now, you will probably lose data. Since unraid can only deal with 1 drive failure at a time without losing data, it is a really bad idea to continue to run with a questionable drive. Drives can fail without warning, at least this one is giving you time to deal with it.

Don't forget the follow on parity check to confirm the parity sync worked as expected.

If you are advanced to the level that prefers using the CLI, it's simple to install nano yourself. Why raise a huge stink about something that takes 5 minutes, max? If it gets installed by default, fine, if you have to install it yourself, that's fine too. No need to get all worked up about it.

Correct. As long as you don't assign a disk to the parity slot, you should be ok. If you show more than one unformatted, stop, get a syslog, and post it.

My money is on the grounding issue. I worked on one network where if the machine was unplugged from the wall power, but plugged into the network, you would get a pretty good shock from the case. Turns out the other end of the network cable was connected to a switch with a different grounding point, and the difference in ground potential was enough to shock you. Needless to say, the network communicated very poorly over that link.

I find it hard to believe any normal software usage, even if extreme amounts, would cause outright failure. The only causes I can think of are electrical, or software attacking the firmware. Different vendors and cards would seem to rule out the firmware issue, so I can only go back to electrical. Could you please describe your wiring, both high and low voltage? What I'm asking for is the physical layout, as in, workstation in one room on a surge protector, network plugged into a patch cord plugged into a wall outlet that runs to a patch panel in the server room, with a patch cord plugged into a 16 port netgear gige switch powered by a battery backup.

Yes