I was executing a bash script this morning and I noticed that when I listed the contents of the directory, which previously had executables in it (color coded) that they are all now 'grey' and there is a directory with the name "/ <-- quotation-forward-slash.

See this post here as it was the same script and similar problem but it didn't affect the entire firesystem: https://www.reddit.com/r/unRAID/comments/17825wq/somehow_this_folder_got_created_and_i_have_no/

 

I'm really concerned because it appears to have affected every single directory in the system. All of the directories that used to be colored are now greyed out. How bad is this and can you recommend any way to fix this? I have a recent Appdata backup, which also backs up my flash drive too. I'm just a little concerned to do anything for fear of mucking it up fully.

The contents of the array appear to be okay. But Docker containers are now throwing execution errors and won't open. Oh crumb.

 

https://imgur.com/a/ofvAiWL

 

Edit: the docker service now fails to start after rebooting the system

Edit2: Restoring the flash drive from last night's back up using the UnRAID USB creator (local file) has not worked. The system is now saying "This is not a bootable disk. Please insert a bootable floppy and press any key to try again..."

 

System: Running a SuperMicro X11SCL-F with an Intel Xeon 2126g and 64GB of RAM. Cache is on a 2TiB NVME. Two parity drives and 8 data disks.

Edited October 24, 20232 yr by zachlovescoffee

Restoring using the unraid usb creator doesn't work. Still getting the error. So I tried doing a fresh install and it doesn't work. Same error as above. I've checked BIOS settings and it's set to legacy boot. Fast boot is disabled. I've tried a different USB port. No good :<

Trying a new USB drive to see if this works. Fingers-crossed.

 

Edit: Tried a new key and getting the same non-bootable error.

Edited October 24, 20232 yr by zachlovescoffee

Figured out one problem - the unRAID USB creator for Mac does not appear to actually work. It creates corrupt disks. The windows unRAID USB creator appears to work. The disk is booting to the 5 menu options "Lime Tech" but because of the way the 'restore' from backup zip worked, it wrote the backup directory as a separate directory instead of creating everything in the primary directory with 'syslinux'. So, it doesn't know from where to boot. I'm now re-creating the boot drive from scratch and I'll copy over the old 'config' folder.

 

**fingers crossed** will update

The server is back up and everything appears to be operational except the docker service, which says "Docker service cannot be started". My cache drive appears to be totally full so I am invoking the mover to see if that sorts things out.