Frank1940 Posted January 26, 2017 Share Posted January 26, 2017 What are the choices? Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 What are the choices? Link to comment
John_M Posted January 26, 2017 Share Posted January 26, 2017 Try 5 first. Failing that 4 or 3. Definitely not 1. Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 Everything except 2 give me the same result- There is no CDROM, or the wrong CD-ROM! Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 If I boot in safe mode this is the result- Am I entering something wrong? The files are at the root of the flash drive. Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 I'm not much good at DOS, but when I use "dir" I'm not seeing the files listed. Do I need to cd to another directory? I see 2 listed, "DRIVER" and "FREEDOS". Neither of these is listing the files I transferred either. I'm sure I'm missing something simple. No idea what though. Link to comment
Frank1940 Posted January 26, 2017 Share Posted January 26, 2017 Try boot it on Hardware NOT a virtual machine. You should actually be trying this on the computer with the BIOS you want to update! Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 Try boot it on Hardware NOT a virtual machine. You should actually be trying this on the computer with the BIOS you want to update! Don't have any VM's. I'm booting this directly on the motherboard. Link to comment
John_M Posted January 26, 2017 Share Posted January 26, 2017 Try typing C: then dir again. Can you see the files now? Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 WORKED GREAT :D Flash update is running. One more question though. At the end of the update I'm supposed to unplug the AC and clear the CMOS. How do I clear the CMOS? Link to comment
Frank1940 Posted January 26, 2017 Share Posted January 26, 2017 Read the manual. Clearing the CMOS is a common operation and I seem to recall that manufacturers use a couple of different approaches. Link to comment
John_M Posted January 26, 2017 Share Posted January 26, 2017 On my Asus boards it's an option in the BIOS to load factory settings. On others you move a link for a few seconds then put it back. I can't help you with specifics, I'm afraid. Link to comment
wgstarks Posted January 26, 2017 Author Share Posted January 26, 2017 Thanks to everyone for your help. Bios is up to date and it looks like the original problem has been resolved. System is currently running 6.2.4. Can't be sure how long this will last since originally the problem was intermittent, but I have high hopes. COULD NOT HAVE DONE THIS WITHOUT YOUR HELP. THANK YOU. Link to comment
wgstarks Posted February 4, 2017 Author Share Posted February 4, 2017 Well, I thought flashing the bios with latest from SuperMicro had fixed this issue but it looks like I was wrong. Attempted to update to unRaid 6.3 today and I'm having the same problem with reboot after install. I just get a blank console screen after "reading bzimage" "reading bzroot". Nothing on the screen except a flashing cursor. Same thing for safe mode and gui mode. Link to comment
Squid Posted February 4, 2017 Share Posted February 4, 2017 Well, I thought flashing the bios with latest from SuperMicro had fixed this issue but it looks like I was wrong. Attempted to update to unRaid 6.3 today and I'm having the same problem with reboot after install. I just get a blank console screen after "reading bzimage" "reading bzroot". Nothing on the screen except a flashing cursor. Same thing for safe mode and gui mode. Without reading through all the posts, does 6.3.0 boot if you download it onto another flash drive, run makebootable, etc Link to comment
wgstarks Posted February 4, 2017 Author Share Posted February 4, 2017 It wouldn't before. Wasn't 6.3.0 of course, it was 6.2.4 and 6.3rc9 that I was testing with. I had to revert to 6.1.9. After flashing my bios to the latest version the problem appeared to be corrected and I could boot 6.2.4. Now it looks like that may have just been a coincidence??? Link to comment
Squid Posted February 4, 2017 Share Posted February 4, 2017 It wouldn't before. Wasn't 6.3.0 of course, it was 6.2.4 and 6.3rc9 that I was testing with. I had to revert to 6.1.9. After flashing my bios to the latest version the problem appeared to be corrected and I could boot 6.2.4. Now it looks like that may have just been a coincidence??? 6.3.0 is 6.3.0-RC9 with very minor changes, and nothing within the boot process. Assuming that all the usual suspects were taken care of in the thread (and with 3 pages, I assume they are) don't know what to tell you Link to comment
Squid Posted February 4, 2017 Share Posted February 4, 2017 Real shot in the dark here: Change the cmos battery (probably a CR2032). The posts state that its an intermittent problem you've been having previously with the same thing. If the problem corresponds with shutdown's of the server, BIOS settings could be getting reset and/or corrupted. Change the battery, set the CMOS back up to how it should be and see what happens.... Link to comment
wgstarks Posted February 4, 2017 Author Share Posted February 4, 2017 Real shot in the dark here: Change the cmos battery (probably a CR2032). The posts state that its an intermittent problem you've been having previously with the same thing. If the problem corresponds with shutdown's of the server, BIOS settings could be getting reset and/or corrupted. Change the battery, set the CMOS back up to how it should be and see what happens.... Thanks. I'm running memtest right now. Ran it for about 30 hours before with no errors so this time it's another shot in the dark. Doubt I'll see any errors, but figured it couldn't hurt anything. i'll grab another battery and try that too. Link to comment
wgstarks Posted February 4, 2017 Author Share Posted February 4, 2017 Real shot in the dark here: Change the cmos battery (probably a CR2032). The posts state that its an intermittent problem you've been having previously with the same thing. If the problem corresponds with shutdown's of the server, BIOS settings could be getting reset and/or corrupted. Change the battery, set the CMOS back up to how it should be and see what happens.... No luck. Changed the battery but still won't boot into 6.3.0. Tried 6.2.4 as well with the same result. Since this problem first occurred when 6.2 was released and has been intermittent ever since, I have to believe that it must be some change that LT made in 6.2. Version 6.1.9 boots every time without any issues. Link to comment
wgstarks Posted April 12, 2017 Author Share Posted April 12, 2017 Finally figured out the cause of this problem. Un-racked my server to install a new cpu just as a guess that maybe that would solve the problem since everybody reporting it uses an Intel Xeon E3-123X. Installed a 1241 which is almost identical and everything was completely resolved. Re-racked the server and connected the old APC console that I usually use and boot issues are back. Not sure of the exact cause, but it appears there was some change to version 6.2+ that causes the boot to freeze when an AP5015 is connected. For now I'll just stick with iKVM Viewer and IPMI. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.