February 21, 20179 yr Hi, I decided it was time upgrading Unraid from 5 to 6. After cleaning up my boot drive and making it bootable the bootloader is installed but when the os is initilizing it stops at "Ehci-pci 0000:00:1d:7 : irq 23, io mem 0xfb9fc000"and after leaving it for 6 hours and then 12 hours but still no results. Tried googling and reading the unraid wiki but havent found anything usable. To be noted i also acquired new hardware, i got an used Xeon 5670 with an EVGA motherboard. Would be really glad if someone could assist me getting my system running. Currently been offline for an entire week. warm regards, andreas edit: attached image of screen Edited February 23, 20179 yr by aekstrom
February 23, 20179 yr On 2/21/2017 at 4:08 PM, aekstrom said: i got an used Xeon 5670 with an EVGA motherboard Which EVGA motherboard is it exactly? Also, is it running with the latest BIOS firmware?
February 23, 20179 yr Author Hi thanks for the reply, Its the EVGA Classified SR-2 (Super Record 2). I got both the motherboard and CPU cheap from a friend and I booted Windows without any problems so theres no hardware failure. I need to check the BIOS version as soon as i get home. Probably one or two updates available.
February 23, 20179 yr It would be worth trying the boot drive in a different USB socket, if you haven't done that already.
February 23, 20179 yr USB 2 is generally more reliable for booting from but since the problem controller is a USB 2 one then yes, do try USB 3. Yes, enable legacy boot.
February 23, 20179 yr Author Uuh. So I think were doing some progress? Got a new error now after tinkering around in the BIOS settings.. maybe i should make a new thread for this error message. offtopic but is there a way to dump the boot log on the usb stick?
February 23, 20179 yr That looks like progress. I don't see an error there - or are you saying that it has frozen at that point? If you can get a command prompt or if you can telnet in from another computer the most useful thing you can do is type diagnostics which will gather a lot of useful information, including the syslog, and store it as a zip file in the logs folder on your boot USB stick.
February 23, 20179 yr If it has frozen I recommend rebooting and choosing MemTest from the boot menu.
February 23, 20179 yr Author Sorry for being unclear. Its frozen. Not really an error. Running the memtest packaged from Limetech right now.
February 24, 20179 yr On 2/21/2017 at 5:08 PM, aekstrom said: I decided it was time upgrading Unraid from 5 to 6. After cleaning up my boot drive and making it bootable the bootloader is installed but when the os is initilizing it stops at "Ehci-pci 0000:00:1d:7 : irq 23, io mem 0xfb9fc000"and after leaving it for 6 hours and then 12 hours but still no results. Tried googling and reading the unraid wiki but havent found anything usable. To be noted i also acquired new hardware, i got an used Xeon 5670 with an EVGA motherboard. It's never wise to make 2 changes at the same time, especially if both are relatively major. Now it's hard to know which change is at fault. I would try to either recreate your previous boot drive with v5 that you know worked, and see if it will boot on this new hardware, -or- try to boot your old hardware with the new boot drive. This way, you can isolate which one needs further troubleshooting. As John said, on this hardware, a Memtest is imperative. That will provide both a memory test and a rudimentary system check (but not a good checkout of the I/O subsystems).
February 24, 20179 yr I would post in detail what your BIOS settings are. I would disable the onboard, sound, disable one of the two ethernet ports, disable the e-sata ports, disable the IDE port and go from there. Also are you running the latest BIOS for the board?
February 24, 20179 yr Author The memtest+ did unfourtanely pass without any errors.. Im going to try downgrading my usb stick to Unraid 5 and go on from there. 4 hours ago, RobJ said: It's never wise to make 2 changes at the same time, especially if both are relatively major. I know.. i cant believe i was so stupid upgrading Unraid before getting it to boot on V5. Also the bios is at its latest version.
February 28, 20179 yr Author I'm losing my mind, still haven't gotten my computer to boot Unraid. Downgraded the usb stick to 6.2.4 and got stuck on "rtc-cmos 00:01 : setting system clock to 2017-02-23 21:09:56 UTC (1487884196)" Why is this so crazy hard? I've tried running Unraid in safe mode, gui mode.. With 1 RAM stick switched out that RAM stick with three others just to be sure theres not any memory errors. Why would Unraid boot on my old used $20 AMD FX processor but not Xeon? I literally changed ZERO bios settings with my old hardware. Is it time to realise its never going to work and switch to FreeNas? I would rather not since my data would be lost but I need my server. Also, this whole time Windows has booted just fine from my SSD. Edited February 28, 20179 yr by aekstrom Forgot to mention something
February 28, 20179 yr It's freezing at roughly the same point, no errors showing, but whatever is trying to initiate at that time is failing, badly. As best as I can tell, loading USB devices is usually next. Assuming you have USB legacy mode enabled, try different USB 2.0 ports for your boot drive, not 3.0 (increases your chance of success). Try both front and back USB 2.0 ports. It's somewhat surprising that Windows is working, but then, you aren't using the USB ports for it. FreeNAS uses another Linux like variant (don't remember which), so there's no guarantee it will boot any better. This really does seem like a hardware issue.
March 2, 20179 yr Author OK. Ive been doing various tests, for example ive now installed Unraid on a harddrive and disconnecting all USB devices from the motherboard. I also disconnected the front-panel USB Hub and my keyboard was connected trough my USB hub built in my monitor. Things are moving forward. I also noticed an error being displayed on my motherboard whilst booting Unraid, turns out one SATA connector on my PSU was damaged and didnt ground one of the harddrives properly. Switched out that cable and no more motherboard errors. Hurray, i guess. In addition to all this Ive been trying to boot Unraid without any harddrives in combination with no USB hardware connected but it seems to fail at exactly the same spot. Could it be my graphics card I have in the server that is causing these errors? The motherboard doesnt have built in graphics. But without the graphics card, how would i know if it boots?
March 2, 20179 yr Graphics card seems an unlikely suspect, because it works in Windows. If you try booting Windows again, can you test all of the available USB ports, whether they are fully operational? I have to confess that if it were my machine, I might have already given up on that motherboard combo!
March 11, 20179 yr Author I'm such a dumb-nut. Couldnt figure out why i didn't succeed appending boot flags to unraid, gave it a quick google and found it on the Wiki. Added these boot flags "acpi=off pci=noapic pci=nomsi nolapic noapic" and it works! Thanks for the suggestions people. Too bad no one was thinking of boot flags So this is what I'm running Unraid OS with (not gui mode, haven't tested that one. Machine will be running headless) "append initrd=/bzroot acpi=off" Edit: It also worked to have the bootable USB plugged in the upper left corner on the IO. In that port no boot flags are needed, at least not for me. Edited April 3, 20179 yr by aekstrom
March 11, 20179 yr I'm glad it's working, but I don't think you'll be happy. I think ALL of those will negatively impact performance, some dramatically! You should not need ANY of those on a modern functional motherboard. Try removing some of those, testing different combinations, and find the combo with the fewest that still works, hopefully there's only one that's absolutely needed. Computers now-a-days really depend on all of those features to run at full speed. I'd have to say this seems to indicate a bad BIOS or bad motherboard (or perhaps a bad PCI card of some sort). Edited March 11, 20179 yr by RobJ add note
March 11, 20179 yr Author Yes. You're right. It was too many boot flags. Ive gotten it down to two as for now. Will be doing tests and which ones are needed. Calling this system modern is a real stretch Since i created this post my needs for a home server has changed so will be building a completely new system in the near future. For now, this system provides the basics and I'll leave it at that. Will see if i can boot the system with one flag and then mark this thread as solved. Thanks again RobJ, especially for the swift responses!
Archived
This topic is now archived and is closed to further replies.