TheGreenWizard

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?

My friend - who was visiting - had his Windows laptop with him and he helped me set it up using his laptop. I do have my husband's Macbook Air with MacOS but that only has the USB-C connector - I'll see if I can find the dongle that changes it to USB-A. More importantly: is my data safe? What do I do?

Unfortunately I don't have a back up of the USB drive. Given that I only have Linux machines (Ubuntu on one, Manjaro XFCE on another), how should I go about this? Should I just email LimeTech and ask for a new key (if that even is possible)? What about my data on my drives - is it still safe or is it all gone now?

So I rebooted the server, and now I'm getting a message on the monitor (connected to the server), that there is no configuration file found and it has "boot:" with a cursor after it.... WTF. EDIT: I checked the USB stick with UNRAID on it... and I get the error, "Sorry could not display all the contents of "UNRAID": error when getting information for "/media/username/UNRAID/SYSTEMz1": Input/Output error" When it rains it pours.... gah. Did I royally eff this up?

So I stopped the array, and the started it up again. Still says it's unmountable. I tried doing a reboot of the system as well, and it still has the same message. I ran xfs_repair -v and got this: Phase 1 - find and verify superblock... - block cache size set to 736008 entries Phase 2 - using internal log - zero log... zero_log: head block 0 tail block 0 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Wed Aug 10 14:37:55 2022 Phase Start End Duration Phase 1: 08/10 14:37:55 08/10 14:37:55 Phase 2: 08/10 14:37:55 08/10 14:37:55 Phase 3: 08/10 14:37:55 08/10 14:37:55 Phase 4: 08/10 14:37:55 08/10 14:37:55 Phase 5: 08/10 14:37:55 08/10 14:37:55 Phase 6: 08/10 14:37:55 08/10 14:37:55 Phase 7: 08/10 14:37:55 08/10 14:37:55 Total run time: done

It told me to use -L. Here's what it came back with: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_fdblocks 969462755, counted 976277671 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:6) is ahead of log (1:2). Format log to cycle 4. done

Here's what I got (I did this with -nv): Phase 1 - find and verify superblock... - block cache size set to 736008 entries Phase 2 - using internal log - zero log... zero_log: head block 8 tail block 4 ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 969462755, counted 976277671 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Wed Aug 10 13:03:34 2022 Phase Start End Duration Phase 1: 08/10 13:03:34 08/10 13:03:34 Phase 2: 08/10 13:03:34 08/10 13:03:34 Phase 3: 08/10 13:03:34 08/10 13:03:34 Phase 4: 08/10 13:03:34 08/10 13:03:34 Phase 5: Skipped Phase 6: 08/10 13:03:34 08/10 13:03:34 Phase 7: 08/10 13:03:34 08/10 13:03:34 Total run time:

Okay, I'm a complete noob on this so I'll ask the question: I presume I'll have to stop the array, do a clean shut down, and then boot it up in Safe Mode GUI? Is that correct? EDIT: I just found out how to enter maintenance mode. My apologies. I'll post the check filesystem once I get it.

Hey all. Our server was shut down improperly a while ago, and after some life events, cleaning out the computer case, replacing the CPU Cooler, and booting it back up, I get the message that my Disk 2 (sdf) is "Unmountable: No file system" and under FileSystem, I see "&xfs". See the screenshot I attached. The server is running a parity check now, and won't be done for about 5 hours from now. I've looked on here before I posted, so I've attached my diagnostics report from UNRAID (v6.9.2). Also, I'm fairly new to UNRAID, but familiar with Linux and the Command Line. Just point me in the right direction of what to do and how to do it. Thank you great and knowledgeable people of the Internet. yoda-diagnostics-20220809-1913.zip