If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#21
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Mon, 17 Dec 2018 23:03:53 -0500, Charlie
wrote: Have you tried raising the CPU voltage slightly? My ASRock Z270 Extreme will reboot on startup if the CPU voltage is too low. It's worth a try although I'm at a loss to understand how it would boot from a DVD. Well that was an interesting suggestion. The default setting for vcore is Auto, which resulted in a vcore voltage of 0.971v. Google seems to indicate that 1.35v is probably the upper ceiling for the Core i7-8700, but values of 1.1v to 1.3v are usually selected in order to keep the heat under control. Taking somewhat of a chance, I set vcore to Fixed (versus Auto), then entered a value of 1.1v. The system booted without issues from the Linux DVD, but it has done that before. I shut it down and reconnected the SATA HDD, leaving the optical drive connected, and tried to boot from the HDD. It booted perfectly! That's the first time it has been able to boot from the HDD. Now I'm letting it run through some boring routine admin tasks, such as creating system snapshots, making and suggesting a list of software packages that could be updated, etc. It's been running from the HDD for about 3 minutes now, and that's a huge leap forward. [Edit: It's been running for over 30 minutes and still going. Amazing!] What are you running for vcore? Also, Fixed or Ratio or ? In a previous post, I remember saying that I trust the defaults. Grrr... |
#22
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Tue, 18 Dec 2018 00:00:49 -0500, Paul wrote:
Char Jackson wrote: This afternoon I took a recent Win10 ISO image and burned it to an m.2 NVMe drive. I disconnected the optical drive and the SATA HDD, then installed the m.2 drive. Twice, out of about 20 boot attempts, I saw a flash of the initial login screen from Win10, but in every case the system would power down, pause, and restart. So it's not a Samsung 2TB SATA HDD issue. A thread with a good deal of weirdness in it. http://www.tomshardware.com/answers/...rd-owners.html One person may have damaged a CPU. Hard to believe they don't test this stuff and monitor the voltage settings the BIOS is using, under lab conditions. Ugh, that's an ugly thread. I upgraded from 1.20 to 1.80 with no issues. Sounds like it could have been a lot worse. |
#23
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Mon, 17 Dec 2018 23:17:48 -0600, VanguardLH wrote:
Char Jackson wrote: Hmm, I started wondering about UEFI which, I believe, is used by your mobo. I haven't delved into that. When you boot using the USB thumb drive, I'm not sure how UEFI is involved. When booting from a SSD or HDD, UEFI is involved. The whole UEFI scheme was Microsoft wanting to lockdown an installation of their Windows product. It seems to irritate Linux users because of the SecureBoot protection. Can you find a SecureBoot option in the BIOS and see what happens when you disable it? https://www.avira.com/en/support-for...tail/kbid/1811 https://docs.microsoft.com/en-us/win...ng-secure-boot You'd think they have the firmware issue some bitch message that your OS wasn't properly signed but knowing Microsoft they might've convinced the BIOS makers to just immediately shutdown without a clue to the user. The SecureBoot option comes disabled by default. I did go looking for it to make sure, but I didn't need to disable it. Charlie suggested checking the vcore voltage, which might have been too low. I bumped it from 0.971v to 1.1v and I'm testing it now. The system booted from the HDD for the first time and has been running now for about 45 minutes. I'm optimistic. |
#24
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Mon, 17 Dec 2018 23:26:06 -0600, VanguardLH wrote:
Paul wrote: Char Jackson wrote: This afternoon I took a recent Win10 ISO image and burned it to an m.2 NVMe drive. I disconnected the optical drive and the SATA HDD, then installed the m.2 drive. Twice, out of about 20 boot attempts, I saw a flash of the initial login screen from Win10, but in every case the system would power down, pause, and restart. So it's not a Samsung 2TB SATA HDD issue. A thread with a good deal of weirdness in it. http://www.tomshardware.com/answers/...rd-owners.html One person may have damaged a CPU. Hard to believe they don't test this stuff and monitor the voltage settings the BIOS is using, under lab conditions. Paul Flashing back to 1.30 (from 1.80) would be one of those "frickin' frackin' son-of-a-brishing azzholes". When you upgrade the BIOS, did the updater offer to save the current code into a .bin file (so you could revert)? You could then go back to 1.20 that came in the mobo, see if that works, try 1.30 (or something just incrementally next in version), and keep walking forward until the mobo puked again, and then step back a version. I read in their forum that you can, under normal circumstances, go from any BIOS version to any other BIOS version. Choosing to believe that, I skipped the step where I could have saved 1.20 to a storage device, especially since plugging in a storage device had a habit of making the whole system unstable. I got lucky and the upgrade went well. |
#25
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Tue, 18 Dec 2018 00:02:53 -0600, Char Jackson
wrote: I bumped it from 0.971v to 1.1v and I'm testing it now. The system booted from the HDD for the first time and has been running now for about 45 minutes. I'm optimistic. And I almost earlier said almost the same thing: swap the CPU for one less demanding, possibly a quad instead hexacore. Except nobody says that: I once refused delivery on a MB I'd already ordered, when I called back to ask that the BIOS was dated correct and current, as advertised, revised for a CPU requiring the update, I'd also selected to include in the same order. The shop I was buying from, someone not so much in the know suggested I buy another CPU, locally, and return it for my money back, once having done my own BIOS update, in case the MB didn't work with their CPU. I'd hope a question of a better PS than you have is indicated. Both recent Gigabyte board purchases I made from NewEgg this past six months do well enough for stock voltages on 95W CPUs (10% overclocking at 4GHz for a stock 3.6 quad and 3.6 on a stock 3.3GHz octal). With whatever I've thrown them from discount $20 PS sales on a couple 500-watt EVGAs. Not especially an impressive feat of engineering, if ASRock marginally choked-out your CPU at below standard specifications, then, leaving enduser customers to figure it out. ....You mention twenty OS install attempts and such. An unusual fortitude, long before then, many would have returned on for their money back. |
#26
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Mon, 17 Dec 2018 20:33:42 -0600, Char Jackson wrote:
On Mon, 17 Dec 2018 22:20:21 +0000 (GMT), "rp" wrote: On Mon, 17 Dec 2018 13:41:44 -0800, mike wrote: Another issue I've had recently relates to partition alignment. I had old drives that were formatted with 32Kbyte partition offset. That rang a bell with me. I had a system refuse to boot due to the allocation unit size. I'd tried using a large size for a partition I used for backup and it did the power off and try again thing even though the boot and system partitions hadn't changed. This was with Windows 10 but it wasn't getting far enough to attempt the boot if I remember correctly. Good info, but I'm pretty sure alignment isn't the issue. I'll keep it on the list, though. Thanks. No, I think you've eliminated that as a potential problem by now, good luck. -- Regards - Rodney Pont The from address exists but is mostly dumped, please send any emails to the address below e-mail rpont (at) gmail (dot) com |
#27
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Tue, 18 Dec 2018 02:01:29 -0500, Flasherly
wrote: On Tue, 18 Dec 2018 00:02:53 -0600, Char Jackson wrote: I bumped it from 0.971v to 1.1v and I'm testing it now. The system booted from the HDD for the first time and has been running now for about 45 minutes. I'm optimistic. And I almost earlier said almost the same thing: swap the CPU for one less demanding, possibly a quad instead hexacore. Except nobody says that: Then, too, the board is a socket 1151 Z390, so it's not like I have another less demanding CPU lying around. I once refused delivery on a MB I'd already ordered, when I called back to ask that the BIOS was dated correct and current, as advertised, revised for a CPU requiring the update, I'd also selected to include in the same order. The shop I was buying from, someone not so much in the know suggested I buy another CPU, locally, and return it for my money back, once having done my own BIOS update, in case the MB didn't work with their CPU. There is currently a situation in the AMD CPU camp exactly like that. As I understand it, if you buy certain board+CPU combos, you'll need to use a previous gen CPU, temporarily, to flash the board so that it recognizes the newer CPU. AMD is aware of the situation and offers, free upon request, loaner CPUs via postal mail. You're expected to use it to flash the board, then return it to AMD. https://www.amd.com/en/support/kb/faq/pa-100 Check the section titled, "Short Term Processor Loan Boot Kit" I'd hope a question of a better PS than you have is indicated. Both recent Gigabyte board purchases I made from NewEgg this past six months do well enough for stock voltages on 95W CPUs (10% overclocking at 4GHz for a stock 3.6 quad and 3.6 on a stock 3.3GHz octal). With whatever I've thrown them from discount $20 PS sales on a couple 500-watt EVGAs. Not especially an impressive feat of engineering, if ASRock marginally choked-out your CPU at below standard specifications, then, leaving enduser customers to figure it out. In over 40 years of working with PC hardware and doing system builds, I can't remember another time where the BIOS defaults let me down. Plenty of times where I voluntarily changed something, but not where I couldn't even boot with the defaults. That might be a first for me. ...You mention twenty OS install attempts and such. An unusual fortitude, long before then, many would have returned on for their money back. I would say the number is much greater than 20. Probably close to 40 on the first board, before I RMA'd it because I thought it was defective. (ASRock agreed that it was probably defective.) Then another 30-40 attempts with the replacement board. I'm apparently a slow learner. |
#28
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
On Tue, 18 Dec 2018 08:08:28 +0000 (GMT), "rp"
wrote: On Mon, 17 Dec 2018 20:33:42 -0600, Char Jackson wrote: On Mon, 17 Dec 2018 22:20:21 +0000 (GMT), "rp" wrote: On Mon, 17 Dec 2018 13:41:44 -0800, mike wrote: Another issue I've had recently relates to partition alignment. I had old drives that were formatted with 32Kbyte partition offset. That rang a bell with me. I had a system refuse to boot due to the allocation unit size. I'd tried using a large size for a partition I used for backup and it did the power off and try again thing even though the boot and system partitions hadn't changed. This was with Windows 10 but it wasn't getting far enough to attempt the boot if I remember correctly. Good info, but I'm pretty sure alignment isn't the issue. I'll keep it on the list, though. Thanks. No, I think you've eliminated that as a potential problem by now, good luck. Yeah, so far it seems like it was a vcore voltage issue all along, and I was simply too ignorant to recognize it. I saw that voltage numerous times while staring at the BIOS screens over the past few weeks and it never occurred to me that it was too low. |
#29
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATAHDD
Char Jackson wrote:
Then another 30-40 attempts with the replacement board. You've reminded me why I stay away from the bleeding edge, use quality parts, etc. And still I've had a few "difficulties". IMO, Having to mount a CPU just to flash the MB seems like an awful lot to ask... I would expect a discount, maybe. Good luck! Bill |
#30
|
|||
|
|||
New system build - reboot loop when attempting to boot from SATA HDD
"Char Jackson" wrote in message ... On Mon, 17 Dec 2018 18:21:26 -0500, Paul wrote: Char Jackson wrote: This is a new system build that fails to boot from the SATA HDD. Instead, it appears to power down and restart, in a loop. Mobo: ASRock Z390 Taichi (original BIOS P1.20, since updated to P1.80) *RAM: G.Skill Ripjaws F4-3200C16Q-64GVK (4x16GB) *CPU: Intel Core i7-8700 Asus optical drive scavenged from parts drawer Samsung 2TB 5400RPM SATA HDD scavenged from parts drawer PS2 keyboard USB mouse Onboard video (also tested with older PCIe video card) *The CPU and RAM are on ASRock's approved compatible list for this mobo. With all parts on hand, I built the new system on a non-conductive table, using the mobo's non-static envelope for additional protection. I like to do the initial build outside of a case to make sure everything works before I go to the trouble of physically installing everything inside the case. The CPU and stock cooler installed without issue, with the stock cooler coming from the factory with heat transfer compound already applied. I installed a single memory module in slot A1 (closest to CPU). I connected a known working PSU (Corsair vx550w), the PS2 keyboard and the USB mouse. I connected a monitor via HDMI to the onboard video and fired it up. No optical drive or HDD connected at this point. The PSU is connected by the standard 24-pin connector and the 8-pin EPS12v connector. The mobo has a separate 4-pin ATX12v connector, which remains unconnected. ASRock tech support says that's fine. With no boot devices connected, the system came up directly in the BIOS screen, where everything looked normal. The CPU and RAM were recognized; the CPU fan RPM was reported as about 1580 RPM and CPU temp at 34C (later stabilizing at about 38-45C, depending on activity). I shut it down, plugged in a USB thumb drive with Memtest+ 6.00 on it, and started back up. As the only available boot device, the system automatically booted into the Memtest program. (Fast forward here, but I tested an individual RAM stick in slot A1, then B1, then A2, and finally B2. Then I jumped ahead and installed all 4 memory modules and let Memtest run overnight. Absolutely no issues so far, but I removed all but the A1 module before proceeding to the next test.) Next, I removed the Memtest USB thumb drive and connected the optical drive via SATA. I inserted a known good Linux Mint 19 disc and started the system. The 'live' Linux environment came up without any issues. I temporarily connected the breadboard system to my LAN and browsed the net for a period of time to watch for issues, but everything was fine. Next, I shut down and connected a single Samsung 2TB 5400 SATA HDD and restarted the system. Again, I booted the Linux live environment, but this time I elected to install Linux to the HDD. That completed without issue. The next step would be to boot into that new Linux install. When I was ready, I removed the Linux disc from the optical drive and rebooted, expecting the system to boot into Linux from the HDD. I got to the expected grub menu, where I have 4 choices and the first choice is the default: Linux Mint 19. Pressing Enter or allowing the timer to expire, the next thing that happens is all of the LEDs (there are quite a few on this mobo) go out, the CPU fan stops spinning, and after 2-3 seconds, the system powers up again, repeating the behavior described. It gets to the grub menu, then whether I intervene or not, it powers down and restarts, in a loop. === Status so far: Stable in the BIOS screens with no storage devices connected. Stable in Memtest when run from USB thumb drive. Stable in the live Linux environment when run from optical disc. **Unable to boot into Linux from the SATA HDD.** === I grabbed a second Samsung 2TB SATA HDD and different SATA cable, then installed Linux to that drive. I got exactly the same behavior described above. Next, with the SATA HDD still connected, I chose the Memtest option from the grub menu. A slightly older version comes up, 5.01 rather than the 6.00 that I have on the USB thumb drive, but Memtest comes up and runs successfully. Thinking it's possibly a too-weak PSU at 550W, I swapped in the 650W PSU from another working system, a Corsair tx650w, but it made absolutely no difference, so I went back to the 550W unit. Online PSU calculators tell me that I need between 230W and 340W, depending on the calculator, so adding a bit for headroom they think I should be OK with 350W to 450W, indicating to me that 550 and 650 are well into the safe area. Thinking it's an overheated CPU, I can see in the BIOS screen and in Memtest that the CPU temp hovers at 38-45C, but usually stays right around 40-41C. The heat fins on the CPU cooler appear to be at room temperature, but then I'm only running Memtest or viewing the BIOS screens, so not any appreciable load. (Yes, it's UEFI, but I'm used to calling it BIOS.) Thinking it's RAM that's not being properly recognized, I see in the BIOS that it's recognized as exactly what G.Skill says it should be: "DDR4-3200 PC4-25600 CL 16-18-18-38 1.35v" ASRock suggested RMA'ing the mobo and Newegg agreed, so I did. When the replacement arrived the other day, I repeated all of the steps listed above and eventually arrived at exactly the same place: === Status so far: Stable in the BIOS screens with no storage devices connected. Stable in Memtest when run from USB thumb drive. Stable in the live Linux environment when run from optical disc. **Unable to boot into Linux from the SATA HDD.** === Beginning to doubt the integrity of the Linux DVD, even after its integrity check was successful and it's a disc that I've used successfully before, I downloaded and burned the latest Windows 10 ISO. Booting from the Windows 10 disc, I get to the point where it starts to copy files to the HDD, then the system powers down, LEDs and CPU fan off, then 2-3 seconds later it powers up again and starts the Windows install from scratch. Even though I was able to install Linux twice on the first HDD and once on the second HDD, I couldn't get the system to stay up long enough to get Windows installed. I also tried burning the Windows 10 ISO to a USB thumb drive, but I couldn't get the system to stay up long enough to get Windows installed that way, either. BTW, there are 8 SATA ports on the mobo, 6 on one controller and 2 on another controller. I tried SATA ports from both groups. I'm currently on page 58 of 491 pages on the ASRock forums, and so far I've seen two others with a "system powers down and restarts" issue, but no resolution provided. I've built at least several hundred PC systems for people since the early 1990's, most of which have gone smoothly, but this one currently has me stumped. This build is supposed to be for me, if I can get it working. At this point, I'm not sure where to go next. - Is it running out of power? Do I need a newer, bigger, PSU? - Is there an issue with the CPU? - Should I chalk this expensive mobo, my first ASRock, up to experience and go with something from ASUS or Gigabyte? Do you have a Kill-O-Watt meter ? I've been meaning to get one for years. They aren't that expensive. My Test System right now, varies from 100W to 350W (furmark). Booting draws as much as 170W, which suggests the CPU is railed on one core during parts of POST. I don't think I have any PSUs in the house, that could not power the system in that state. Only Furmark would be in danger of tipping over the most gutless supply. I was rather surprised what it takes to wake my new video card up. Even playing BF2 it was only drawing 130W or so. During installation, install media needs to be decompressed. On Linux, it's a squashfs perhaps. On Windows, it's their "fancy compressor which compresses as good as 7ZIP or RAR". These need to be decompressed during installation phase. Windows in the past, has elected to use more than one core during decompression. This implies (perhaps) that each file could be compressed individually. So more than one file could be processed at a time, depending on source media read rate. if you expect to do a good job of maximizing power consumption, you'll need Furmark (good) or Prime95 (less). If the Linux LiveCD will boot, you can go to mersenne.org/downloads and get the static linked Linux Prime95 and run the torture test. That will heat up the CPU nicely. Using lmsensors or equivalent, should allow monitoring CPU temps. At the moment, the situation has deteriorated to the point where the only peripheral connected is the optical drive, and yet it still won't boot as it did before. Previously, that combo would not only boot up, but I could have a HDD connected and tell Linux to install there. Disconnecting the optical drive and inserting a LiveCD on USB gives the same results - no boot, loss of power, pause, restart, loop. I'll let it rest for a bit and then try again. Got a $20 SSD handy ? Install onto that ? ******* Install Linux from a USB key... to a USB key ? The intention in this case, is to avoid SATA entirely. See above, even a single optical drive or USB stick is apparently enough to tip it over at the moment, let alone two of something. You would be creating a slash ("/") and swap on the USB key and installing file by file as normal. This isn't particularly good for the USB key of course, but it's just for a test, not for long-term running. ******* Seatools has a USB bootable option. AFAIK the Samsung division was bought by Seagate ? Maybe (by now) Samsung branded drives are included ? https://www.seagate.com/ca/en/support/downloads/ Running a HDD test, would prove whether it's "just" HDD access that tips it over. Well, right now, it's USB, SATA HDD, m.2 NVMe, and optical, any *one* of which are enough to tip it over. ******* I would take one last thorough pass through the BIOS settings, to see if there are any power limiters or something. There's got to be a hint in there somewhere. It was ASRock support who firmly stated that if the setup defaults don't work to boot the system, then I should RMA it, so I RMA'd the first board. Now that the replacement behaves exactly the same way, I'm not sure what to think. To me, it has always smelled like a lack-of-power issue, but I figured what are the odds that two PSUs that work fine in other systems, one with 16 internal drives, wouldn't work on this system with a freakin' USB or optical drive. This board/CPU combo may be a beast, though. ******* In the past, some BIOS did a poor job of resource planning. Most OS installed involve "PNP OS: No", which means that the BIOS plans the memory and address map. In one case, writes to RAM were actually writing to a USB overcurrent register, and causing an overcurrent message to appear on the screen. And this is a side effect of the BIOS not being able to plan a memory map properly. This typically happened on older systems with 8GB limits, where the user installed 4GB of RAM, and then... the BIOS would lose its mind. ******* Well, really, I'm stumped. Sounds like a design flaw. But I wouldn't let that stop me from having a little fun and running the more obscure test cases. Before trying a Gigabyte board. My last couple of boards have been Gigabyte and they were stable to the point of being boring, where boring is a good thing. This is my first ASRock and I'm not sure what I was thinking, other than "hey, the reviews are good, let's try it". Dumping the Samsung HDD and testing something else would be relatively high up my list. Just in case. I've been letting it all rest with the power off while I type this. Once I hit send, I'll try again to see if I can get at least as far as I got earlier. ******* The best part about some of the stuff I've run, is not remembering the results at all :-) https://www.easyuefi.com/wintousb/ "Hasleo software" "best free Windows To Go Creator" I think there is supposed to be a free version, maybe that's it. A USB-to-go would allow running Windows without an install step. I think I might have also booted an Enterprise Windows VM and tried to make an OTG stick from there too, in VirtualBox, with USB passthru. Hasleo might be an attempt to do that with non-Enterprise windows. Interesting, thanks. I don't think I'm at the point where I can try that since I need it to actually boot something without powering down, but I'll keep it in mind. I may have missed it somewhere in this thread, but have you tried plugging in the 4-pin ATX12v connector? Certainly wouldn't hurt anything if not needed, and would eliminate one more thing. Just a thought :-) -- SC Tom |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
EP45-DS3L: Reboot Loop? | (PeteCresswell) | Gigabyte Motherboards | 1 | November 7th 08 10:22 AM |
when installing XP pro, after first reboot, system corrected (destroy) files on attached SATA drive | [email protected] | Asus Motherboards | 4 | September 2nd 06 04:07 PM |
a7v600-x stuck in reboot loop? | Son Of LaL | Asus Motherboards | 10 | November 29th 05 09:13 PM |
Reboot loop woes... | Ignacio Dinchong | Asus Motherboards | 3 | July 3rd 05 11:54 PM |
How to stop system attempting to boot from external hard drive? | Miss Perspicacia Tick | General | 2 | January 15th 05 03:46 AM |