TheGreenWizard

Solution Found: Just had to reconstruct the docker.img file following these instructions. Thanks again for the help!

After the debacle with the previous topic (see first post - you helped me a bit there), I have a back up that has a new install of 6.9.2 UNRAID, but hte config file is the original one that I had... (if that makes sense). I used a new computer to visit the WebGUI and I am still getting the same error. I rebooted the system and still the same error. I wonder if I were to delete the docker.img file - which I"ve read on the forums is quite fragile - and try to do a reinstall maybe that would work?

Gods above I need my eyes checked. Could have sworn I attached them. Thank you for catching that, and here's the ZIP file. yoda-diagnostics-20220811-1257.zip

Recently had issues with a data disk not mounting - but thanks to the community, I was able to get it fixed (I've attached the thread for context). However, Now that I was able to get the Disk 2 to mount, I've noticed that the Dockers tab is showing this message: Fatal error: Uncaught UnexpectedValueException: RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: Not a directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:97 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(97): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096) #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(129): DockerTemplates->listDir('/boot/config/pl...', 'xml') #2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(243): DockerTemplates->getTemplates('all') #3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(323): DockerTemplates->getTemplateValue('cr.hotio.dev/ho...', 'Icon', 'all', 'jellyfin') #4 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(298): DockerTemplates->getIcon('cr.hotio.dev/ho...', 'jellyfin') #5 /usr/local/emhttp/plugins/dynamix.docker.manager/inclu in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 97 I've attached my Diagnostics. Any thoughts? Previous Post on what was done before I noticed this error (basically, flash drive got corrupted before, and I needed to remove a character from the disk.cfg file).

Thanks again for this - I'm noticing other problems now, but I'll post a new thread if I can't find it after looking. (Deals with the dockers I had)

So I did that. And it fucking worked. Thank you SO MUCH!!!! I'd give you a bear hug if I could. Before I do, should I do anything else? Another diagnostics? etc?

Ran diagnostics - see attached ZIP file. yoda-diagnostics-20220811-1203.zip

Alright. Huge sigh of relief. I was able to get the original USB device to boot up (using my Ubuntu Machine) thanks to this post: Turns out it wasn't booting up because my system did NOT have syslinux installed. I copied over my config file to the USB stick and am now able to access the server. I'm gonna take a break but now, I'm back to square one: my Disk 2 is stating it's unmountable and there's no file system.

I tried a new USB disk, and for some reason that one didn't work either... It's the same generic brand I got from work. I'll see if using a different USB brand altogether will make a difference. Out of curiosity - does it matter what version of UNRAID I use? I'm wondering if I should try using a different newer version of UNRAID and then go from there.

I did this already on both a Macbook Air (with MacOS), and on my Linux Machine. Still not booting up.

My macbook did not recognize the drive when I tried to boot up to it. When I see it through the File Manager in Linux, I can see the files. My BIOS is old - American Megatrends and the mobo is a Crosshair IV Formula from ... 2010 I think. It doesn't have a UEFI option.

So, I tried to see if my macbook could boot up from the USB drive... and it doesn't even detect the USB drive that UNRAID was on. Am I right in assuming that my USB drive basically got fried?

Update: I tried to make the USB disk manually on Linux. I followed the instructions here. When I got to the step making the USB disk bootable, I get this in the terminal on Linux: INFO: make_bootable_linux v1.3 INFO: The following device appears to be the unRAID USB Flash drive: /dev/sdc INFO: Temporarily mounting unRAID USB Flash drive to /tmp/UNRAID_TMP_MOUNT Permit UEFI boot mode [Y/N]: n INFO: unRAID USB Flash drive currently mounted to /tmp/UNRAID_TMP_MOUNT, copying temporary installer files to /tmp/UNRAID To continue you may need to enter your admin password INFO: Installing Syslinux bootloader on /dev/sdc1 sh: 1: mcopy: not found INFO: Writing MBR on /dev/sdc 0+1 records in 0+1 records out 447 bytes copied, 0.00148693 s, 301 kB/s INFO: the Unraid OS USB Flash drive is now bootable and may be ejected. Should I be concerned about "sh: 1: mcopy: not found" ? Also, was I supposed to copy the config folder over before or after making the disk bootable?

Alright folks. Here's what I did: 1. Connected to MacOS, I downloaded the USB Creator from UNRAID. 2. Copied and uploaded the original USB contents to my Google Drive. 3. Using USB Creator from UNRAID, I did a fresh install of UNRAID to the USB stick with the same version (v6.9.2). 4. I copied over the original config folder to the new USB disk, replacing the "fresh" config folder. 5. I ran the "make bootable mac" file and selected NO to the UEFI boot. I plugged it in, and... I get the message that "This is not a bootable disk. Please insert a bootable floppy and press any key to continue." Note: I made the USB bootable on the Mac, choosing NOT do to UEFI. After checking the BIOS to make sure that I have USB drive as the first priority... it still does the same message.

Regarding backups of that stuff - I believe I have everything on their original drives, but I know my husband may not have done that with his stuff... HOWEVER.... I was able to use the Macbook Air and get into the USB drive - I can see everything, including a Config folder. What should I do?