Aspect

Members
  • Posts

    52
  • Joined

  • Last visited

Everything posted by Aspect

  1. No bios updates for me this is a very old dell system. still cant boot on 6.12.4
  2. UPDATE: 6.12.4 still has same issue.
  3. UPDATE: The 6.12.3 update does not boot either for anyone following this thread. I guess i may be stuck at 6.11.5 as the latest version that functions on my system.
  4. Just tried creating a new usb with 6.12.2 fresh config as suggested and I’m getting the same error I’m only booting to the first line bzroot then the server reboots and does that loop over and over. I let it do this for 30 minutes and it never got past the bzroot line.
  5. correct i tried that about an hour ago and im stilling having the boot only to the bzroot line then the screen glitches with a red line and the system reboots and does that over and over.
  6. at the bzroot line right after the boot selector screen
  7. also i cant UEFI boot as my server does not support it. old Dell 5810.
  8. The manual BZ file transfer did not work. so for me all solutions mentioned above have not worked.
  9. for some reason i was never notified of these replies. @itimpito answer you question yes i have tried both UEFI and Legacy still same result. i have now also tried to manually select the USB as the boot device and am still having same issue. im going to try the manual BZ file transfer mentioned here and see what happens.
  10. I don’t want to jack the thread as I have created my own but just wanted to mention I’m having the exact same issue and have tried all troubleshooting steps I’ve seen mentioned on the forum.
  11. I have 2 servers 1 with tones of VMs Dockers drive pools and config changes that had no issue with the latest 2 updates. with that said however my other server which is a backup server with a few dockers and 1 VM on it seems to have an issue with 6.12 and 6.12.1. It will not fully boot. it makes it to the bzroot line after the startup menu and then restarts and is stuck in that boot loop. its and Intel Xeon E5-1660 V3 so for sure not an 11th gen that i read are having a few issues with the current Linux kernel. I have provided diagnostics but for 6.11.5 since that's the latest version that will fully boot. please help. foreshadow-diagnostics-20230620-1619.zip
  12. I upgraded one server no issue. The other however will not boot it crashes right after the auto start and the bzroot line comes up a small red line appears horizontally across the screen then the server reboots and it keeps doing that over and over again. But if I replace the flash drive files with the backup it boots right into 6.11.5.
  13. i do not have the errorcode 14 but my logs are flooded with IPV6 errors. would be nice if there was something in the template to turn off IPV6 as i don't believe the urbackup app itself has this built in yet. i notice people complain about this directly on their forum too.
  14. @trurlI 100% don't have an other devices or anything logged into the server. i do have pfBlocker_NG on my pfsense FW but i have had that with no changes for about 3-4years so i don't see why it would affect it now?
  15. I cant even make this up right after posting the above i logged into the server and its stuck with the staring services... notification in the bottom right while everything seems fine and running. I really have no clue what to do at this point.....
  16. I'm going to mark this as solved as I am currently running with 9 days up time with no issue. not exactly sure what resolved the issue but below is what I changed in the process of trying to figure it out. I'm on AMD so i changed some BIOS settings for C-states "Power Supply Idle Control" set it to "typical current idle". as well as disabled global C-States i moved my USB boot drive from a front panel USB port to an on motherboard USB 2.0 port i installed the plug in to auto remount the USB boot drive if it unmounts for any reason Changed the IPs my FW and servers where using form 105.55.5.0/24 to 10.10.5.0/24 Switched Docker from macvlan to ipvlan Hopefully i don't jinx myself but i think i am back to running normally.
  17. Uptime 6 days 12 hours 12 minutes Might have fixed it!!!!!!!!! Fingers crossed.
  18. understood that will be the next thing i try. will i need to mess with anything with the dockers i have setup or is that just as simple as switch it and see what happens with the crashing?
  19. understood. could macvlan conflicts or my dockers in general be causing these issues?
  20. @trurl no i do not currently just the 1 tab open for unraid webUI. only 2 devices i log into this server are my computer and phone. phone is logged out and this computer has 1 tab open. can it cause an issue when there is a big difference in shares when running these 2 commands? ls -al /mnt/user and ls -al /boot/config/shares
  21. @trurl @JorgeB So this morning i logged in to check to make sure the server wasn't in a soft crash state, its not fully in the state i had started this thread for, now it seems normal other than the fact that its stuck saying starting services in the bottom left even though everything is started and has been for 2 days. i checked in a private browser and on chrome and Firefox and still shows the same. output of df -h / is root@Rocky:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 32G 2.1G 30G 7% / so it went up by .1GB. there are no notifications or errors other than the "starting services" notification. i'm attaching the current diagnostics. since i last posted i have moved the USB to a 2.0 space directly on the motherboard and changed the IP range that my servers are on. is there any chance this is a symptom of a dying USB? the one that's in this server has been there for a few years and it use to be in a 3.0 slot until i read that that can cause it to burn out quicker. I'm at a lose and don't know what to do this is becoming an upsetting issue because no matter what i do i cant seem to find or resolve the problem. rocky-diagnostics-20230212-1011.zip
  22. I changed it realized my mistake. using 10.10.5.0/24 now.
  23. @trurl I use PFsense and i have my server ipv4 port set to that IP its internal to my network i use 192.168.2.0 , 10.10.10.0 and 105.55.5.0. Is that something i should change i assumed the ipv4 addresses of my internal network didnt matter?
  24. Digging through my log file i see at Feb 8 16:49:XX its almost like my USB drive got disconnected and the server logs show like the server restarted multiple times within a few minutes? I'm going to look through every line of these logs and try to find something that makes sense. I really want to figure this out because the only way I know when the server has crashed in this odd state is when I log in to check or do something. @JorgeB @trurl Thank you both for your suggestions and looking into this. Hopefully I can report back what the cause was and what resolved the issue. syslog-127.0.0.1.log.zip