Print Page | Close Window

Z87E-ITX boot screen frozen after mSATA partition

Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3638
Printed Date: 06 Feb 2025 at 4:16am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com


Topic: Z87E-ITX boot screen frozen after mSATA partition
Posted By: Jessie
Subject: Z87E-ITX boot screen frozen after mSATA partition
Date Posted: 22 Oct 2016 at 8:37pm
" rel="nofollow - I have a Z87E-ITX that I am using with a mSATA drive (Kingston SMS200S3/30G).
It was working perfectly until today when I tried to change the mSATA drive partition.

I haven't changed anything from a hardware perspective (I just boot on a USB stick to partition the mSATA drive).

Now I cannot go past the BIOS Splash screen, it is frozen.

I tried CMOS reset, disconnecting everything (even the RAM) and update BIOS to the latest version (2.5). The BIOS Splash screen remains frozen, except when the mSATA drive is connected.

The mSATA drive was working perfectly before the partition, so I am not sure that it is the culprit.

I don't have a spare motherboard to test this mSATA drive, so it seems that the next step can only be to RMA the mSATA drive and see what happen.

Has somebody a better idea ?



Replies:
Posted By: parsec
Date Posted: 22 Oct 2016 at 11:41pm
Originally posted by Jessie Jessie wrote:

" rel="nofollow - [URL=][/URL][URL=][/URL]I have a Z87E-ITX that I am using with a Msata drive (Kingston SMS200S3/30G).
It was working perfectly until today when I tried to change the Msata drive partition.

I haven't changed anything from a hardware perspective (I just boot on a USB stick to partition the Msata drive).

Now I cannot go past the BIOS Splash screen, it is frozen.

I tried CMOS reset, disconnecting everything (even the RAM) and update BIOS to the latest version (2.5). The BIOS Splash screen remains frozen, except when the Msata drive is connected.

The Msata drive was working perfectly before the partition, so I am not sure that it is the culprit.

I don't have a spare motherboard to test this Msata drive, so it seems that the next step can only be to RMA the Msata drive and see what happen.

Has somebody a better idea ?


You did not say if the PC will boot with the mSATA drive removed from the board, so I can only assume that it doesn't boot at all now.

Your description is confusing, you said you think the mSATA drive has a problem, but the flash screen is frozen if the mSATA drive is connected.

If you remove the mSATA drive, does the PC boot?

I'll describe what I think is happening, but I'm really not sure this is the situation.

When you installed your OS (unknown, is that Windows?), was the mSATA drive connected to the board? Meaning both the OS drive and the mSATA drive were working when you installed your OS?

If that is correct, and you are using Windows, from your description of the problem it sounds like you were caught by a thing that the Windows installation program does.

If there was another drive connected to the board besides the target OS drive when you installed Windows, then Windows will put the System/Boot partition on the other drive, not the target OS drive. That means your PC depends upon both drives to boot Windows.

If the other drive is then formatted again as you said you did to the mSATA drive, then the System/Boot partition that was on the mSATA drive was removed, and Windows will no longer boot.

Can you get into the BIOS, and check the boot order?

If what I described is correct, you can fix your OS installation by booting from your Windows installation media (disk, USB flash drive) and select Repair. That will normally put the System/Boot partition where it belongs, on the OS drive.




-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: Jessie
Date Posted: 23 Oct 2016 at 2:56am
" rel="nofollow -
Originally posted by parsec parsec wrote:

You did not say if the PC will boot with the mSATA drive removed from the board, so I can only assume that it doesn't boot at all now.

Your description is confusing, you said you think the mSATA drive has a problem, but the flash screen is frozen if the mSATA drive is connected.

If you remove the mSATA drive, does the PC boot?


Yes the PC can access the BIOS and after that boot on a USB stick, if I remove the mSATA drive.
I the mSATA drive is there, I am stuck on the BIOS splash screen.

Originally posted by parsec parsec wrote:

I'll describe what I think is happening, but I'm really not sure this is the situation.

When you installed your OS (unknown, is that Windows?), was the mSATA drive connected to the board? Meaning both the OS drive and the mSATA drive were working when you installed your OS?

If that is correct, and you are using Windows, from your description of the problem it sounds like you were caught by a thing that the Windows installation program does.

If there was another drive connected to the board besides the target OS drive when you installed Windows, then Windows will put the System/Boot partition on the other drive, not the target OS drive. That means your PC depends upon both drives to boot Windows.

If the other drive is then formatted again as you said you did to the mSATA drive, then the System/Boot partition that was on the mSATA drive was removed, and Windows will no longer boot.

Can you get into the BIOS, and check the boot order?

If what I described is correct, you can fix your OS installation by booting from your Windows installation media (disk, USB flash drive) and select Repair. That will normally put the System/Boot partition where it belongs, on the OS drive.


Windows was installed on the mSATA drive. No other hard drive were connected.

If the mSATA drive is connected, I cannot do anything as I am stuck on the BIOS splash screen. Especially not booting on my USB stick (systemrescuecd) or a hard drive.

So the problem is not booting. Without the mSATA drive, I can boot on whatever I want and do whatever I want. But as soon as I connected back the mSATA drive, the motherboard is stuck on the BIOS splash screen (so I cannot reformat/repartition the mSATA drive).

I've also tried with activating/deactivating UEFI (through CSM compatiblity) and switching AHCI/IDE. But no improvement.

I've tried changing the boot order, but it doesn't have any effect. As soon as the mSATA drive is connected, the BIOS is frozen.

Any other idea ?

Thanks


Posted By: parsec
Date Posted: 23 Oct 2016 at 1:25pm
" rel="nofollow -
Originally posted by Jessie Jessie wrote:



Windows was installed on the mSATA drive. No other hard drive were connected.

If the mSATA drive is connected, I cannot do anything as I am stuck on the BIOS splash screen. Especially not booting on my USB stick (systemrescuecd) or a hard drive.

So the problem is not booting. Without the mSATA drive, I can boot on whatever I want and do whatever I want. But as soon as I connected back the mSATA drive, the motherboard is stuck on the BIOS splash screen (so I cannot reformat/repartition the mSATA drive).

I've also tried with activating/deactivating UEFI (through CSM compatiblity) and switching AHCI/IDE. But no improvement.

I've tried changing the boot order, but it doesn't have any effect. As soon as the mSATA drive is connected, the BIOS is frozen.

Any other idea ?

Thanks


It seems you ruined something on the mSATA drive (that we now know was an OS drive) when you tried to "... change the mSATA drive partition".

You'll need to describe what change the partition means. It now sounds like you have remnants of an OS installation on the mSATA drive that Windows uses to attempt to boot, but it fails. But that is only one possibility. Whatever happened from changing the partition, the Windows installation seems to be corrupted.

If the mSATA drive was quick formatted, or cleaned using the diskpart command, and still acted as you describe, then my guess would be that drive failed for some reason.

If you can boot from your Windows installation media, with only the mSATA drive in the PC, try to repair it. If that fails, your only other option is deleting the remaining partitions, and then use it for whatever you need.



-------------
http://valid.x86.fr/48rujh" rel="nofollow">


Posted By: Jessie
Date Posted: 23 Oct 2016 at 8:44pm
Originally posted by parsec parsec wrote:


It seems you ruined something on the mSATA drive (that we now know was an OS drive) when you tried to "... change the mSATA drive partition".

You'll need to describe what change the partition means. It now sounds like you have remnants of an OS installation on the mSATA drive that Windows uses to attempt to boot, but it fails. But that is only one possibility. Whatever happened from changing the partition, the Windows installation seems to be corrupted.


Windows was installed on the first partition.
Steam was installed on the second partition.
I just tried to wipe the Steam partition without touching the first partition.
But something must have gone wrong.

Originally posted by parsec parsec wrote:


If the mSATA drive was quick formatted, or cleaned using the diskpart command, and still acted as you describe, then my guess would be that drive failed for some reason.

If you can boot from your Windows installation media, with only the mSATA drive in the PC, try to repair it. If that fails, your only other option is deleting the remaining partitions, and then use it for whatever you need.


I cannot do anything as long as the mSATA drive is connected. So I especially cannot format/clean/repair it.
And I don't have a spare motherboard to try it on another system.

It's written http://superuser.com/questions/974872/ssd-causes-my-computer-to-freeze-on-bios-splash-screen" rel="nofollow - here that:
Quote
You may have a corrupted boot sector but a correctly working SSD. Some BIOSses do not handle that very well.


I think that is what is happening here. But as I don't have any way to test the mSATA drive (which is out of warranty), we'll never know.
The other possibility is of course that the mSATA drive is completely broken. But I find that strange that a repartitioning can utterly break a drive like that.



Print Page | Close Window

Forum Software by Web Wiz Forums® version 12.04 - http://www.webwizforums.com
Copyright ©2001-2021 Web Wiz Ltd. - https://www.webwiz.net