TheGreenWizard Posted August 9, 2022 Share Posted August 9, 2022 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 Quote Link to comment
trurl Posted August 10, 2022 Share Posted August 10, 2022 Check filesystem on disk2, be sure to capture the output so you can post it. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 (edited) 16 hours ago, trurl said: Check filesystem on disk2, be sure to capture the output so you can post it. 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. Edited August 10, 2022 by TheGreenWizard found the answer to my question. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 16 hours ago, trurl said: Check filesystem on disk2, be sure to capture the output so you can post it. 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: Quote Link to comment
JorgeB Posted August 10, 2022 Share Posted August 10, 2022 Run it again without -n, if it asks for -L use it. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 2 minutes ago, JorgeB said: Run it again without -n, if it asks for -L use it. 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 Quote Link to comment
JorgeB Posted August 10, 2022 Share Posted August 10, 2022 Should mount now, then look for a lost+found folder and any data inside. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 (edited) 42 minutes ago, JorgeB said: Should mount now, then look for a lost+found folder and any data inside. 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 Edited August 10, 2022 by TheGreenWizard added report for xfs_repair -v Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 (edited) 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? Edited August 10, 2022 by TheGreenWizard Quote Link to comment
trurl Posted August 10, 2022 Share Posted August 10, 2022 Do you have a backup of your Unraid flash drive? The config folder from your backup is all you need to get going again with all your configuration intact on a new install. If your flash drive is still usable, you won't have to transfer the license to a new flash drive. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 14 minutes ago, trurl said: Do you have a backup of your Unraid flash drive? The config folder from your backup is all you need to get going again with all your configuration intact on a new install. If your flash drive is still usable, you won't have to transfer the license to a new flash drive. 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? Quote Link to comment
trurl Posted August 10, 2022 Share Posted August 10, 2022 2 minutes ago, TheGreenWizard said: I only have Linux machines How did you originally create your Unraid flash drive? Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 (edited) 6 minutes ago, trurl said: How did you originally create your Unraid flash drive? 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? Edited August 10, 2022 by TheGreenWizard Quote Link to comment
trurl Posted August 10, 2022 Share Posted August 10, 2022 If you can create a new install on the same flash drive then you won't have to transfer the license to a new flash drive. Without your configuration you will be starting from scratch, but your data should be OK if you assign your disks correctly. We can get your disk assignments from the diagnostics you already posted. You must always have a current backup of flash. You can download a zipped backup of flash from your Unraid webUI, and MyServers plugin will store a flash backup for you on Unraid cloud. Since we are on the subject of backups Do you have another copy of anything important and irreplaceable? Parity is not a substitute for backups. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 7 minutes ago, trurl said: If you can create a new install on the same flash drive then you won't have to transfer the license to a new flash drive. Without your configuration you will be starting from scratch, but your data should be OK if you assign your disks correctly. We can get your disk assignments from the diagnostics you already posted. You must always have a current backup of flash. You can download a zipped backup of flash from your Unraid webUI, and MyServers plugin will store a flash backup for you on Unraid cloud. Since we are on the subject of backups Do you have another copy of anything important and irreplaceable? Parity is not a substitute for backups. 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? Quote Link to comment
trurl Posted August 10, 2022 Share Posted August 10, 2022 Make a backup of config folder, prepare flash drive as a new install, restore your config folder to that new install, try to boot. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 20 minutes ago, trurl said: Make a backup of config folder, prepare flash drive as a new install, restore your config folder to that new install, try to boot. 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. Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 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? Quote Link to comment
TheGreenWizard Posted August 10, 2022 Author Share Posted August 10, 2022 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? Quote Link to comment
trurl Posted August 11, 2022 Share Posted August 11, 2022 Can you read its files, and does it have the expected capacity? Quote Link to comment
trurl Posted August 11, 2022 Share Posted August 11, 2022 You set the flash drive up for non-UEFI boot, are you sure your BIOS isn't trying to boot UEFI? Quote Link to comment
TheGreenWizard Posted August 11, 2022 Author Share Posted August 11, 2022 10 minutes ago, trurl said: Can you read its files, and does it have the expected capacity? 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. 8 minutes ago, trurl said: You set the flash drive up for non-UEFI boot, are you sure your BIOS isn't trying to boot UEFI? 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. Quote Link to comment
trurl Posted August 11, 2022 Share Posted August 11, 2022 https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method Quote Link to comment
TheGreenWizard Posted August 11, 2022 Author Share Posted August 11, 2022 42 minutes ago, trurl said: https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method I did this already on both a Macbook Air (with MacOS), and on my Linux Machine. Still not booting up. Quote Link to comment
trurl Posted August 11, 2022 Share Posted August 11, 2022 If you can get another flash to work with a new install, your config backup will still work, but you will have to go through the license transfer. https://wiki.unraid.net/Manual/Changing_The_Flash_Device Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.