March 10, 20251 yr I had a couple of power outages where my server did its thing and all was well, but it seems to have corrupted the flash drive. I am going to try and repair it, but if I can't, I need a way of getting the drive assignments out so I can put it back in the correct order. I still have shell access via SSH. Is there a command to get this information?
March 10, 20251 yr Community Expert First, try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files. And that backup will have everything you need if you need to replace it, assuming the config folder is still complete and readable.
March 10, 20251 yr Author I have plenty of backups. So you're saying if I recreate it using one of the backups it will automatically populate the drives in the correct order without me manually doing the mapping to the way it was?
March 10, 20251 yr Community Expert 9 minutes ago, Bmalone said: So you're saying if I recreate it using one of the backups it will automatically populate the drives in the correct order without me manually doing the mapping to the way it was It should.
March 10, 20251 yr Author here is the output of 'diagnostics' # diagnostics Starting diagnostics collection... sh: line 1: /usr/bin/todos: Input/output error tail: cannot open '/boot/bz*.sha256' for reading: No such file or directory sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sort: write failed: 'standard output': Broken pipe sort: write error timeout: failed to run command ‘todos’: Input/output error sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sh: line 3: /usr/bin/todos: Input/output error ls: write error: Broken pipe sed: can't read /goathead-diagnostics-20250310-1427/config/go.txt: No such file or directory timeout: failed to run command ‘todos’: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error timeout: failed to run command ‘todos’: Input/output error timeout: failed to run command ‘todos’: Input/output error awk: inplace:31: fatal: load_ext: cannot open library `/usr/lib64/gawk/inplace.so': /usr/lib64/gawk/inplace.so: cannot read file data: Input/output error timeout: failed to run command ‘todos’: Input/output error timeout: failed to run command ‘todos’: Input/output error timeout: failed to run command ‘todos’: Input/output error sh: line 1: /usr/bin/todos: Input/output error /usr/bin/env: ‘node’: No such file or directory sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error sh: line 1: /usr/bin/todos: Input/output error timeout: failed to run command ‘zip’: Input/output error done. ZIP file '/boot/logs/goathead-diagnostics-20250310-1427.zip' created.
March 11, 20251 yr Community Expert It appears to be failing, see if you can copy the syslog to the flash drive or user share: cp /var/log/syslog /boot/syslog.txt or cp /var/log/syslog /mnt/user/<share name>/syslog.txt If it's not visible there, you can also get the disk order from /boot/config/super.dat
March 11, 20251 yr Author I was able to find the super.dat file from the flash backup, but it doesn't appear to be in human readable format when I open it with Notepad. How can I extract the drive setup from this file?
March 11, 20251 yr Community Expert super.dat is how 23 hours ago, Bmalone said: it will automatically populate the drives in the correct order
March 11, 20251 yr Community Expert Unraid reads super.dat when it boots. That is how it knows the disk assignments. The config folder from your flash backup is all you need to get going again with all of your configuration (ALL settings from the webUI) on a new install. Much better to let Unraid do this from the existing config backup than trying to set everything up again yourself. Less trouble and less opportunity for mistakes.
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.