trurl

Do you have an attached keyboard and monitor? Can you boot in GUI mode?

4KiB

Try the manual method to prepare flash: https://wiki.unraid.net/UnRAID_6/Getting_Started#Manual_Method_.28Legacy.29

How did you prepare flash drive?

Tools - Diagnostics attach ZIP to NEXT post.

Not enough information in that Amazon listing to decide whether to recommend or not. You could try it.

Connection issues on 2 disks, disk4 and another that might have been disk6, serial ending EZJ3. syslog shows you formatted both disk4 and disk6 Sep 28 19:45:17 durinstower emhttpd: shcmd (484): /sbin/wipefs -a /dev/md4 Sep 28 19:45:17 durinstower root: /dev/md4: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42 ... Sep 28 19:47:19 durinstower emhttpd: shcmd (489): /sbin/wipefs -a /dev/md6 Sep 28 19:47:19 durinstower root: /dev/md6: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42 Did you actually unassign disk 6 before formatting? If not then presumably it formatted all assigned disks that weren't mountable. Since you have backups that will be the simplest way to recover. Of course, formatting isn't the way to fix unmountable disks. You should have asked for help before doing anything.

Note that mover can't move open files, so if your Downloads includes seeding torrents, for example, they can't be moved while seeding. Your diagnostics were just after reboot so no mover runs in syslog. If those files aren't getting moved and you can't figure out why you can turn on mover logging in Settings - Scheduler.

Assuming you have prepared Flash drive correctly, you will have to work with your BIOS to get it to boot. Can't tell more without more information from you.

USB is not a reliable permanent connection which is required for parity array or cache pool. Usually you power drives from the same power supply as the motherboard. You might want more RAM if you want to try docker or VM.

Go to Shares - User Shares, click Compute All, wait for the result. If it doesn't show the results after a few minutes refresh browser. Then post a screenshot.

Looks like disk3 is already not assigned. Stop array, unassign disk8 (and disk3 if not already), start array with both unassigned. Stop array, reassign disk8, start array to begin disk8 rebuild. After disk8 rebuild completes, you can shrink the array with New Config (without disk3) and rebuild parity.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Since you have dual parity, you can rebuild disk8 without having disk3 installed.

Do you know how to proceed?

Seems I misunderstood. It sounds like the disabled disk is not the disk you want to remove. Is that correct? Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

If there is any data on the emulated drive you want to keep you will have to copy it elsewhere before removing it.

To re-enable it in the array you have to rebuild it. To remove it from the array, New Config, unassign it, and rebuild parity.

You have configured docker.img to be on the isos share instead of system where it normally would be. And isos is on the array.

Looks like it might still have your config. Have you tried it?

Yes the missing disk can be read and even written but you have no redundancy until replace/rebuild of course.

Post a screenshot of the contents of that config folder.

Go to Tools-diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Parity2 does have a lot of reallocated. I didn't look at the others. Are there SMART warnings for any other disks on the Dashboard?

You didn't notice the SMART warning on disk2? Extremely high number of CRC (connection) errors. Suspect you have numbers in the Errors column on Main also. You are doing parity2 swap? Why don't you have parity assigned?