JonathanM

What do you get when you browse to the address that works on your Surface using your main PC?

See if you can get in to the BIOS and check the boot order. Soiunds like you disturbed something when you were in the case.

Rebalance from RAID1 to Single. Keep in mind if either drive has an error, you will lose the content of the entire pool. It defaults to RAID1 for data redundancy.

Yes. Set the secondary storage to array, and the mover direction from array to cache.

Honestly, at this point it would be good for you to just have a play. If you start the array with the failed disk unavailable, then the next disk that is assigned to that slot will be used for the rebuild. The emulated failed drive data should be available any time the array is started. A larger drive will automatically expand during the rebuild, and for reasons that are obvious when you know how parity works, it's impossible to use a smaller drive to rebuild. The replacement drive can be any size from equal to the failed drive, up to and including the size of the smallest parity drive.

Nope, I was answering your question. /mnt/user = array + pools /mnt/user0 = array only

array + pools or array only

The biggest issue tends to be when it comes time to migrate to different hardware, Unraid identifies the drives with hardware identification, which RAID controllers don't pass intact. One of the biggest benefits of Unraid is the ability to move the drives to almost any plain vanilla platform, as long as the disk controller is a plain HBA the drives will be detected and used without any changes needed at all. Sometimes RAID controllers alter the drive's geometry, which can put the partition at a location that isn't compatible when the drive is moved to different hardware, causing unmountable drives. USB instead of SATA or SAS is very hit or miss, typically miss. The USB bus resets can and do cause writes to fail, and Unraid will drop the drive when a write fails. Another issue for many people (not for you, you seem to have this taken care of) is that Unraid's ability to monitor and report on disk health is disabled by many RAID controllers. If a drive is failing, you want to investigate, and possibly replace the drive sooner rather than later. Unraid (like most RAID) requires the entire capacity of all the data drives and the parity drive to rebuild a failed drive. The reason it's super important with Unraid compared to other RAID setups, is that in the Unraid parity array disks are allowed to spin down when not accessed, which means a drive can possibly go months without being touched, but when another drive fails the spun down drives are all required to be read perfectly. As long as you keep good backups you will be fine. The issue is simply that you are bypassing or hamstringing many of the features and safeguards built into Unraid to help protect your data. People tend to get upset when they lose data, so we try to mitigate as many causes as possible.

That will only show the reserved space, not what's actually occupied.

Depends on how you check the size. At the command line use "ls -l -s" That's LS -L -S lowercase. That will show you both actual space used and the allocation limit.

Probably won't change anything, but in general the min-max memory doesn't work like you think it should, and probably should be set to the same amount.

Another thing to investigate would be a client machine that has access to the files could be infected with ransomware. I've seen behaviour where the original file was renamed, and an encrypted copy written with the original name. The end result would be the deletion of the randomly named files, but maybe not all the actions are able to happen over a remote share.

This is the correct place. Support should be handled publicly, so that if someone else has the same issue the answer is available without having to be rehashed over and over. Private support should be an absolute last resort, and since it only benefits one individual, it's more fair if it's paid support. This is just a general statement, individual authors are free to handle it how they wish.

I believe what he meant was... If you are not running ich777's template, then this is not the proper thread to ask for support. If you click on the container in the Unraid GUI, there will be a popup with a "Support" link.

Good call. Until the RAM is trustworthy, any data written or read is possibly corrupt.

That would imply a hardware issue. Perhaps try to reset the CMOS, or if the motherboard has a speaker connection see if you get any beep codes. Also maybe try removing the RAM, attempt a boot and see if you get error beeps at all.

ReiserFS file systems, especially mature ones that have lots of use, are very slow, deletion can take ages. Moving files is worse than copying, because you have writes on both the source and destination, which are competing for writes to the parity drive. It's quicker to use a copy function, then format the source drive after you are sure all the files have been copied successfully. This also has the advantage of being able to verify the copy is correct and complete before you delete the source.

🤣

Yep, that's fine. The possible issue happens when the cord is pulled and the ground leg is disconnected. As long as the cord stays in the outlet you are good.

Highly recommend doing a test run by throwing the breaker to kill power and see how the system reacts. DON'T yank the UPS power cord out of the wall, bad things can happen.

Wrong thread?

Sorry, I have no experience working with docker folders instead of the image file, the folders option seems to have much more issues. Theoretically everything in either the folders or the image file is easily recreated, so the normal advice is to blow it away and redownload the containers with the previous apps function.

Is the docker service disabled? As in, no docker tab available in the GUI?

Probably in the mover tuning plugin support thread. It seems like there is a lot of activity there, many fixes and issues. If you remove the mover tuning plugin and still have issues, post back here in general support.

I have no experience with synology, so you will need to research whether there is an apcupsd or NUT package available for synology. If there is, it's relatively straight forward to configure apcupsd or NUT as a slave, and configure it to shut down completely before the master starts the shutdown process. However, in order for that to work, the network must remain up, so all routers and switches involved must be on battery backup as well. This brings up another issue, I seriously doubt that particular UPS is big enough for both servers and all your network equipment, it's only rated for 330 watts, and at that output it can run for about 3 minutes, which is barely enough time to get shut down in the best of unattended shutdown scenarios. You need to get a real world watt consumption figure on each piece of equipment that needs battery backup, and see if this model is capable enough. Keep in mind that you need to use maximum instantaneous power figures, not idle power, because during shutdown everything gets ramped up to close all the open files and programs, and save any data that's still in RAM before it can safely shut down.