July 3, 20233 yr Hi all, I need help since my server does not boot anymore after 6.11.5 -> 6.12.2 upgrade, it looks like it's crashing. I have reverted to 6.11.5 for now... Any help is appreciated. Best regards, IMG_0759 (1).mov
July 3, 20233 yr Author I was comparing the 6.11.5 syslog messages to what I got from 6.12.2 and looks like it got stuck Jul 2 23:58:29 Tower kernel: pci 0000:09:00.1: PME# supported from D0 D3hot D3cold <------------- this is the last msg I see during boot time on 6.12.2, the next lines are from 6.11.5 Jul 2 23:58:29 Tower kernel: pci 0000:08:02.0: PCI bridge to [bus 09] Jul 2 23:58:29 Tower kernel: pci 0000:08:02.0: bridge window [io 0xa000-0xafff] Jul 2 23:58:29 Tower kernel: pci 0000:08:02.0: bridge window [mem 0xf7200000-0xf72fffff] IOMMU group 14:[111d:8018] 08:02.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) [8086:10bc] 09:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) [8086:10bc] 09:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) IOMMU group 15:[111d:8018] 08:04.0 PCI bridge: Microsemi / PMC / IDT PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) [8086:10bc] 0a:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) [8086:10bc] 0a:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06) Best Regards,
July 3, 20233 yr Author I have also tried to boot with a stock 6.12.2 usb, same result it got stuck, last post below: Jul 2 23:58:29 Tower kernel: pci 0000:09:00.1: PME# supported from D0 D3hot D3cold Help please...
July 3, 20233 yr I made the mistake of updating as well. I am currently trying to recover from a backup USB image but it isn't wanting to do that either now. I get it to boot up and start the process of loading, only have to have come to this point in the screen shot, then the display goes dead and the server IP is silent. I am at a super loss now. I was a BIG supporter of this project, with multiple instances, and now I am starting to second guess if this was the right way to go with my home servers. Seriously thinking about converting to TruNas Scale at this point. All I have had are problems with this, either bad / corrupt / dead USB or boot errors. The fact I have to wait 3 days to get a license moved from one USB to another is total BS.
July 3, 20233 yr 8 hours ago, Gnur said: the next lines are from 6.11.5 Jul 2 23:58:29 Tower kernel: pci 0000:08:02.0: PCI bridge to [bus 09] It likely PES12N3A 12-lane 3-Port PCI Express Switch (rev 0e) cause this problem. Anyway pls try disable iommu in bios does this help.
July 3, 20233 yr 38 minutes ago, DrMcNasty said: The fact I have to wait 3 days to get a license moved from one USB to another is total BS. You can restore the backup to new USB and it should allow you self-service to replace the key. ( Self-service allow once per year ) Edited July 3, 20233 yr by Vr2Io
July 3, 20233 yr Author Didn't help. I have disabled Intel vt-d and intel virtualization... Same behavior.
July 3, 20233 yr 34 minutes ago, Vr2Io said: You can restore the backup to new USB and it should allow you self-service to replace the key. ( Self-service allow once per year ) This is the second or 3rd time I have had to do this. USB disks are not meant for this purpose of being on and powered all the time. Right now I can kind of get into my server but the connection is there then drops and back and forth. I have a service ticket in but that does me no good since last time I had to wait 2 days for a new key to put on it and it left my array offline. And no, setting up a new trial is NOT an option based on the files shares and all the configuration I have in place. The USB key for the registration is the WEAKEST point of this entire platform, and more and more it is becoming an issue. Why can't I move the key more than one on my own self service profile? If the key had to be bound to a SINGLE GUID of a USB disk then what is the issue?
July 3, 20233 yr Author OK, I removed the PCI express adaptor to my nvme cache and didn't help, then I removed my IBM 39Y6138 IBM PRO/1000 PT Quad Port Server Adapter LP PCI-E and the boot completed without a problem... Now that I have identified the Quad Port NIC as the culprit, any idea how to solve the issue?
July 3, 20233 yr Author Solution Update: I switched the PCI express card slot with the QUad Ports NIC card.... that did the trick.... not sure why... but it is working...
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.