blade316 Posted December 29, 2019 Share Posted December 29, 2019 Hey guys, I hope everyone had a great Christmas! .... Its seems the grinch may have visited me a little later though haha Ok so the scenario is, shut down my server to install an Icy Box 5 bay enclosure, made sure each of the drives what connected back to the same SATA ports on the motherboard from the Icy Box, started the server back up, and now once I get to the UnRAID Login prompt, I get a segmentation error in emhttpd. In this state I can still ping the UnRAID server and I can SSH to it, however I cannot access the WebUI. I have rebooted several times - same error each time. I have also done a chkdsk on my UnRAID flash drive - no errors, however its now around 50% success on boot whether it recognises the USB drive to boot from or not - Might be a separate issue though. Heres what I can do: Can boot to UnRAID OS - gets to the login prompt - throws a segmentation error - can SSH to server - cannot get the WebUI - cannot access the array Can boot to UnRAID OS GUI mode - cannot connect to the WebUI directly from the server or from another machine - can SSH to server - cannot access the array Can boot to UnRAID OS safe mode (no plugins) - can get into the WebUI on the server and from remote machines - can SSH to server - can start array once I enter my decryption key - can access data on the array - can start docker service - can start and use docker containers I'm not sure if the below is related, but I have never seen permissions display 'd?????????' before. I'm wondering if UnRAID is unable to boot normally due to not being able to access these locations? However that doesn't explain why Safe mode works, as it will still be accessing some of those same locations. root@unRAID:/boot# ls -l ls: cannot access 'syslinux': Input/output error ls: cannot access 'LOGS': Input/output error ls: cannot access 'preclear_reports': Input/output error ls: cannot access 'previous': Input/output error ls: cannot access 'packages': Input/output error total 173004 d????????? ? ? ? ? ? LOGS drwxrwxrwx 2 root root 2048 Dec 19 2016 System Volume Information -rwxrwxrwx 1 root root 6135808 Jun 25 2019 bzfirmware -rwxrwxrwx 1 root root 65 Jun 25 2019 bzfirmware.sha256 -rwxrwxrwx 1 root root 4559520 Jun 25 2019 bzimage -rwxrwxrwx 1 root root 65 Jun 25 2019 bzimage.sha256 -rwxrwxrwx 1 root root 101732216 Jun 25 2019 bzroot -rwxrwxrwx 1 root root 64527404 Jun 25 2019 bzroot-gui -rwxrwxrwx 1 root root 65 Jun 25 2019 bzroot-gui.sha256 -rwxrwxrwx 1 root root 65 Jun 25 2019 bzroot.sha256 -rwxrwxrwx 1 root root 14587 Jun 25 2019 changes.txt -rwxrwxrwx 1 root root 7975 Jun 25 2019 license.txt -rwxrwxrwx 1 root root 1760 Jun 25 2019 make_bootable.bat -rwxrwxrwx 1 root root 3291 Jun 25 2019 make_bootable_linux -rwxrwxrwx 1 root root 2428 Jun 25 2019 make_bootable_mac -rwxrwxrwx 1 root root 150024 Jun 25 2019 memtest d????????? ? ? ? ? ? packages d????????? ? ? ? ? ? preclear_reports d????????? ? ? ? ? ? previous d????????? ? ? ? ? ? syslinux -rwxrwxrwx 1 root root 4 Jul 2 2018 update.assistant.tmp When I boot into UnRAID OS safe mode (no plugins), I found the below in the system logs. These errors appear with each restart. Dec 29 20:49:07 unRAID kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA Dec 29 20:49:07 unRAID kernel: ACPI: Early table checksum verification disabled Dec 29 20:49:07 unRAID kernel: pci 0000:01:00.1: BAR 10: failed to assign [mem size 0x00020000] Dec 29 20:49:07 unRAID kernel: pci 0000:01:00.2: BAR 7: failed to assign [mem size 0x00020000] Dec 29 20:49:07 unRAID kernel: pci 0000:01:00.2: BAR 10: failed to assign [mem size 0x00020000] Dec 29 20:49:07 unRAID kernel: pci 0000:01:00.3: BAR 7: failed to assign [mem size 0x00020000] Dec 29 20:49:07 unRAID kernel: pci 0000:01:00.3: BAR 10: failed to assign [mem size 0x00020000] Dec 29 20:49:07 unRAID kernel: floppy0: no floppy controllers found Dec 29 20:49:07 unRAID kernel: random: 7 urandom warning(s) missed due to ratelimiting Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT2._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT2._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT3._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT4._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:49:07 unRAID kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Dec 29 20:49:07 unRAID kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) Dec 29 20:50:19 unRAID rpc.statd[1777]: Failed to read /var/lib/nfs/state: Success Dec 29 20:50:25 unRAID avahi-daemon[2064]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! The only thing I haven't done is taken the drives out of the icy box and connected them directly to the motherboard. I would prefer to avoid that as it was a PITA to get it all in the case (cable overload!) .... and seeing in safe mode it recognizes the drives properly, and the array starts successfully, I don't think the icy box is causing an issue. I've attached my UnRAID diagnostics I was able to grab whilst in safe mode. I'm really hoping someone will be able to help me, or at least point me in the right direction. If I've left any critical information out please let me know. Cheers, Daniel unraid-diagnostics-20191229-1054.zip 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.