December 17, 20178 yr My server locked up so I rebooted and now I cannot connect to the web gui! I have no idea what's going on and am freaking out since I have so much data on there. Any clue on what to check and how to check it? the server seems to boot up ok and I can ssh in but there is just no web gui edit, when I ssh in it shows no files in /boot. but when i put the flash drive into another computer i see all the files there Says -bash: cd: mnt: No such file or directory edit 2, rebooted, did a ls in /boot and saw this /bin/ls: cannot access 'System Volume Information': Input/output error /bin/ls: cannot access 'syslinux': No such file or directory /bin/ls: cannot access 'bzimage': No such file or directory /bin/ls: cannot access 'bzroot': No such file or directory /bin/ls: cannot access 'bzroot-gui': No such file or directory /bin/ls: cannot access 'EFI-': Input/output error /bin/ls: cannot access 'previous': Input/output error /bin/ls: cannot access 'make_bootable_linux': No such file or directory /bin/ls: cannot access 'make_bootable_mac': No such file or directory /bin/ls: cannot access 'readvz': No such file or directory /bin/ls: cannot access 'logs': No such file or directory /bin/ls: cannot access 'packages': No such file or directory /bin/ls: cannot access 'preclear_reports': No such file or directory /bin/ls: cannot access 'FSCK0009.REC': No such file or directory EFI-/ FSCK0012.REC* FSCK0025.REC* System\ Volume\ Information/ make_bootable.bat* FSCK0000.REC* FSCK0013.REC* FSCK0026.REC* Tonga.rom* make_bootable_linux FSCK0001.REC* FSCK0014.REC* FSCK0027.REC* bzfirmware* make_bootable_mac FSCK0002.REC* FSCK0015.REC* FSCK0028.REC* bzimage memtest* FSCK0003.REC* FSCK0016.REC* FSCK0029.REC* bzmodules* packages/ FSCK0004.REC* FSCK0017.REC* FSCK0030.REC* bzroot preclear_reports/ FSCK0005.REC* FSCK0018.REC* FSCK0031.REC* bzroot-gui previous/ FSCK0006.REC* FSCK0019.REC* FSCK0032.REC* changes.txt* readvz FSCK0007.REC* FSCK0020.REC* FSCK0033.REC* config/ syslinux/ FSCK0008.REC* FSCK0021.REC* FSCK0034.REC* ldlinux.c32* FSCK0009.REC FSCK0022.REC* FSCK0035.REC* ldlinux.sys* FSCK0010.REC* FSCK0023.REC* FSCK0036.REC* license.txt* FSCK0011.REC* FSCK0024.REC* FSCK0037.REC* logs/ Edited December 17, 20178 yr by ffhelllskjdje
December 17, 20178 yr 8 minutes ago, ffhelllskjdje said: when I ssh in it shows no files in /boot. Ultimately when this happens it means that your flash drive dropped offline, the syslog is full of "bread" errors which may cause the log to fill up, which may cause a ton of other issues. No recourse other than to reboot the system (from command prompt) powerdown -r But, try a different USB controller for the flash drive. Ideally USB2
December 17, 20178 yr May have misread your OP. This happened immediately after a reboot? Could be that your flash drive suffered corruption. Run chkdsk on it from a windows box (not sure of Mac equivalent).
December 17, 20178 yr Author 10 minutes ago, Squid said: May have misread your OP. This happened immediately after a reboot? Could be that your flash drive suffered corruption. Run chkdsk on it from a windows box (not sure of Mac equivalent). I tried to chkdsk but it says it is write protected Edit, nm, I think it's because it's my locked down work computer, i'll look to see how to do this on mac or linux Edited December 17, 20178 yr by ffhelllskjdje
December 17, 20178 yr Community Expert 1 hour ago, ffhelllskjdje said: I tried to chkdsk but it says it is write protected or your flash drive is gone, common error when there's a problem.
December 17, 20178 yr Author 3 hours ago, johnnie.black said: or your flash drive is gone, common error when there's a problem. yeah i think the flash drive crapped out on me. I formatted a new one and threw the /config folder over and all seems well now? Not sure if I did that right but the array went back up and it's checking parity
Archived
This topic is now archived and is closed to further replies.