MoebiusStreet Posted January 23, 2022 Share Posted January 23, 2022 (edited) On rebooting, my server comes up - the shares work, I can ssh into the box, etc. But the web interface doesn't come up. Can anyone help me figure out how to bring it back? How I got into this: I was trying to do some backups onto an external USB harddisk. Apparently the front-mount USB ports on my machine are flaky, and the device kept disappearing, then coming back. I moved it to the rear ports, where it was stable, but when I checked the external disk's filesystem there were lots of errors that were taking forever to fix. So I figured I'd just delete the partition and recreated it. But doing so while the fs repairs were still running angered the OS, with the log file advising me to reboot, so I did. When I rebooted the web interface came up fine, but the array didn't. I figured out that this was because I've got 6 real devices, with the external disk being a 7th, thus exceeding my license. So I told it to shutdown, I removed the external device, and powered it up again. Since this point, the system is coming up: I can ssh as I said, I can read and write to its shares, and from the ssh session I can see that it's also successfully connected to a separate NAS box in the house. Another oddity I notice is that the CPU is constantly busy, from 30%-50%. This is a relatively weak machine, it's just intended as a NAS, but I don't recall seeing it busy like that before unless it's verifying the array parity or something (perhaps that's exactly what it's doing, and I don't know because I can't see the web interface?). There are two processes taking up almost all of this: unraidd0 and mdrecoveryd. I don't even know where to look for the logs that would pertain to starting the web interface (or anything else for that matter). Can anyone offer guidance? Edited January 23, 2022 by MoebiusStreet Quote Link to comment
Squid Posted January 23, 2022 Share Posted January 23, 2022 9 hours ago, MoebiusStreet said: But the web interface doesn't come up. What does come up? Anything? You should post your diagnostics (you can grab them via the command line) Quote Link to comment
MoebiusStreet Posted January 23, 2022 Author Share Posted January 23, 2022 3 hours ago, Squid said: You should post your diagnostics (you can grab them via the command line) Can anybody tell me where to find them via the command line? BTW, I can confirm that the high CPU load must have been from parity checking, because this morning it's back to normal in that respect. Quote Link to comment
Hoopster Posted January 23, 2022 Share Posted January 23, 2022 Can anybody tell me where to find them via the command line? BTW, I can confirm that the high CPU load must have been from parity checking, because this morning it's back to normal in that respect.Type ‘diagnostics’ at the command line.Sent from my iPhone using Tapatalk Quote Link to comment
MoebiusStreet Posted January 23, 2022 Author Share Posted January 23, 2022 Hmmm. It won't let me do that: root@jabba:~# sudo su root@jabba:~# diagnostics Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/jabba-diagnostics-20220123-1226.zip' created. root@jabba:~# cd /boot/logs bash: cd: /boot/logs: No such file or directory Quote Link to comment
itimpi Posted January 23, 2022 Share Posted January 23, 2022 It might be worth using the ‘df’ command to check that the flash drive is mounted at /boot? The messages you give suggest that it is either not online, or has problems. Quote Link to comment
MoebiusStreet Posted January 23, 2022 Author Share Posted January 23, 2022 (edited) I'm not sure if this is correct, but it looks reasonable: root@jabba:~# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 5636072 879676 4756396 16% / devtmpfs 5636080 0 5636080 0% /dev tmpfs 5710776 0 5710776 0% /dev/shm cgroup_root 8192 0 8192 0% /sys/fs/cgroup tmpfs 131072 23372 107700 18% /var/log /dev/sda1 3907100 619744 3287356 16% /boot overlay 5636072 879676 4756396 16% /lib/modules overlay 5636072 879676 4756396 16% /lib/firmware tmpfs 1024 0 1024 0% /mnt/disks tmpfs 1024 0 1024 0% /mnt/remotes /dev/md1 3905110812 3207670612 697440200 83% /mnt/disk1 /dev/md2 3905110812 2834683480 1070427332 73% /mnt/disk2 /dev/md3 5858435620 2931119740 2927315880 51% /mnt/disk3 /dev/md4 3905110812 278353664 3626757148 8% /mnt/disk4 /dev/sde1 117220792 10697084 105500996 10% /mnt/cache shfs 17573768056 9251827496 8321940560 53% /mnt/user0 shfs 17573768056 9251827496 8321940560 53% /mnt/user //THOTH/Media 2879515136 2416516620 462998516 84% /mnt/remotes/THOTH_Media //THOTH/Other 2879515136 2416516620 462998516 84% /mnt/remotes/THOTH_Other //THOTH/Pictures 2879515136 2416516620 462998516 84% /mnt/remotes/THOTH_Pictures Editing to add: I should have thought to look inside that drive, too. And I can do so, but the contents don't look legit (and if these are the contents, how did I actually boot?) root@jabba:/boot# ls -al total 4 drwx------ 9 root root 4096 Dec 31 1969 . drwxr-xr-x 23 root root 480 Jan 23 12:26 .. Edited January 23, 2022 by MoebiusStreet Quote Link to comment
itimpi Posted January 23, 2022 Share Posted January 23, 2022 2 hours ago, MoebiusStreet said: Editing to add: I should have thought to look inside that drive, too. And I can do so, but the contents don't look legit (and if these are the contents, how did I actually boot?) root@jabba:/boot# ls -al total 4 drwx------ 9 root root 4096 Dec 31 1969 . drwxr-xr-x 23 root root 480 Jan 23 12:26 .. It must have been online during the boot-tocess, but it looks as if it may have now dropped offline since none of the expected contents are showing. 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.