jmbailey2000

It does for me, but what I do is run the move again without making any changes. Sometimes do it twice, but all the folders eventually get deleted. So if you do a Scatter, when it finishes, select the Scatter tab again and do Next, Next, etc. to accept the same settings that were there before.

Weird. Started array and parity check didn't start. Array drive is mounted and I see files. Never had Unraid not start a parity check after an unclean shutdown. Guess I'll move files off and then replace the drives. Bizarre. Attached is the post start diags if needed, but at this point I'm guessing I'm good. sol-diagnostics-20250115-1515.zip

Won't parity check start (because of unclean shutdown) which means the emulated disk would go away?

No previous diags unless they get saved automatically. I couldn't do anything on the server related to stored files. No drives could be accessed and most menu choices were unavailable. The only diags I was able to do was after the reboot. Guess my biggest question is related to starting the array. Right now 1 bad parity and 1 bad array drive (being emulated). With an unclean shutdown the parity check will fire up at start and will wipe out the emulated drive I assume? Can the parity check be avoided on array start so I can get the files off the emulated drive?

First, I had 2 drives "fail" about 6 weeks ago. one parity and one array. Thought is was the drive shelf, so replaced the shelf with a Dell 730xd. No issues moving to the new server, other then I replaced both drives, lost no data. Cool. Weird that neither of the "failed" drives showed any SMART errors. They also passed multiple pre-clear tests. Today, on the new server, I had both the exact same slots (same parity slot and same array slot) fail. The drives in those slots were new and somewhat new, pre-clear and tested 3 times before put in to service for the rebuild referenced above. The fact they were different drives then before but in the exact same slots is wildly odd to me. Plus, neither of these newly "failed" drives have any errors on them at all. The odd thing with this failure is all the drives (parity and array) threw errors (Unbalanced was moving some files at the time). Afterwards, all drives were inaccessible. Tried stopping the array. That happened I think after about 3 hours. Not for sure because I just walked away and let it go. I rebooted and got the wonderful (unclean shutdown) notice. So now my question/concern...... I know if I start the array, because of the unclean shutdown, the system will start a parity check. I would assume if that happens I will lose the array drive that the system says will be emulated? Am I correct in that assumption? Diags attached. sol-diagnostics-20250114-1809.zip

For me, I see it when an unbalanced run completes. Appears to be successful, yet this error pops up upon completion.

That did it!! Thanks!! ps - Santa will put a little something extra in your stocking!!!

I'll be home in a couple of hours and will give it a shot and let you know what happens. Thanks!!!

The disks have never been mounted, at least in this box, so no idea why it shows that. There is only one SDK (Dev 2). The other 12TB drive is SDJ (Dev 1) and that is clearing just fine. And I've cleared each of those disks multiple times before starting a preclear, so no idea why they show a partition.

Before clearing the pre-clear error (1st 2 lines) and then after. Both drives look the same as the bottom line. Below is the pre-clear screen.

I am having the issue with a 12TB spinner too. The SSD was small and I wanted to wipe the data on it before I give it to my son. Normally I wouldn't pre-clear an SSD, but had several I wanted to clean and test. Logs attached (includes the SSD and the 12TB). TOWER-unassigned.devices.preclear-20241217-0841.zip

Any workarounds by chance? I did add it and another drive to the array, started it and then formatted the drives. Then I did a new config/removed the drive I want to pre-clear (leaving the other drive inplace), started the array and then tried to pre-clear the drive and same error. If no work around, no a big deal, I can wait for a potential fix. Thanks!

Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Preclear Disk Version: 1.0.31 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Disk /dev/sde is a SSD, disabling head stress test. Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Disk size: 1000204886016 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Disk blocks: 1953525168 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Blocks (512 bytes): 1953525168 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Block size: 512 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Start sector: 2048 Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: Disk /dev/sde is part of Unraid array. Aborted. Dec 16 07:30:35 preclear_disk_S1D9NSAF205613P_32066: error encountered, exiting ... tower-diagnostics-20241217-0834.zip

Have a drive that was in another Unraid box, and wanted to pre-clear it, but no matter what I do, the pre-clear fails with a message telling me the drive belongs to an array. It isn't. It is unassigned. I've added to the new array, removed it, cleared it, changed formats, etc. but just can't get it to the point where pre-clear will start the process. No issues with several other drives I've tried this with, just this one. Thoughts?

I haven't done anything yet. Those diags are from the old server that lost a parity and data drive (Disk 8). I have a new server, but just in the process of powering it on and getting BIOS and whatnot configured. I'm looking for what the best process is to set up the new server. Create everything from scratch and reconfig all dockers then copy files over, or can you do something like copy the docker file and libvirt file to a new machine, create all the same shares and have the thing work? Or can you just unplug flash and drives and move everything over to the new server? I'd still have a missing parity and bad disk 8, but would have to do a new config to try and fix that.

sol-diagnostics-20241020-0933.zip

So, took a hit from remnants of Hurricane Helene recently. No power for 4 days. But prior to it going out, we took multiple up/down power hits. While I was able to stop Unraid and my disk array, when the power finally went off, my disk shelf apparently had some issues. When powered back up, I had lost 1 of my 2 parity drives and a data drive in the array. I was able to move the files off the emulated drive to other drives in the array. While not a big (I thought), I have since lost 3 other slots that had spare unused staged drives. So, at this point, the shelf is dying and need to retire it. I've got another server I'm going to spin up, but an looking from guidance on best method to migrate everything from old to new. I could just spin up another Unraid server, install everything from scratch with new drives and then copy all files from old to new. Drawback is I would really like to try and avoid having to do all the setup and config of all the dockers, virtuals, etc. But, I'm wondering if there is some tricky magic process that I could use to at least move all my dockers, virtuals, config to new server and the either copy the files to new box or pull the drives and move them to the new server. Getting all the config and cockers and such is a bigger concern then moving the files. Any thoughts? Greatly appreciated!!

Hmmmm......going to have to consider that. Thanks!!

Curious why you would select iDrive e2? I've been looking at migrating to a mass cloud storage too and been looking at Backblaze's storage. Haven't looked at iDrive yet, but curious why you might have settled on them. Thanks!

Any idea why the Backblaze Personal Backup just gives me a black screen with 'Server Disconnected (code 1006)"? No matter what I try, that is all I get. Let is sit for 2 hours, refreshed and nothing.

Hmmm.....could be....I'll take a look. Thanks!!

Has anyone run in to issues with 6.12.2 or 6.12.3 throwing 400 Bad Request web page error? This all started after I upgraded from 6.9 to 6.12 to 6.12.3-rc2 and now in stable 6.12.3. Unraid works fine for a few days after an array shutdown and reboot, but after that I pretty much can't load anything from from CA (or follow any links through CA for support, info, etc.) and have have a couple of dockers that start throwing the same error when I try and run them. I couldn't update any plugins or containers before the 6.12.3 upgrade because of this error. Now after the reboot, is working fine, but will only last a few days then start up again with the error. I can regain control of the main page by clearing cache stuff in Chrome and the main page will work, but nothing else in CA or these couple of dockers. Thanks!

Anyone have any ideas. It started working out of the blue a week later and worked fine until 3 days ago. Now, not working again and no matter what I do, can't get it to run.

Anyone having issues where out of the blue, nzbhydra2 just throws a "http 400 bad status" error? I used it 2 days ago, no problem and now today, this pops up within 1 second of trying to connect to the web gui. I forced an update and even deleted the docker and reinstalled with no luck.

Has anyone had issues with dockers starting up after the backup but not actually working? In my specific case, qBittorrent gets turned back on after the backup, and everything appears to be working, yet, no uploads/downloads are happening. After a few days troubleshooting, I found that every morning, I have to (in the app itself) log out of qBittorrent, then exit qBittorrent, then restart the docker container. Once I do that, qBittorrent starts and whatever was uploading/downloading when the backup was executed, starts up automatically again. Thanks!