Forum Home
Press F1
Thread ID: 148187	2019-08-31 23:26:00	W10 on M.2 NVMe not opening	kioti (17360)	Press F1

Post ID	Timestamp	Content	User
1463451	2019-09-02 01:48:00	Nope. have given up the idea of wiping the M.2 etc. I thought I would try convert Gpt to MBR see if that get the M.2 to boot. Used Easeus Partition Master to do the convert to MBR, couldn't lock the volume because thiongs were beien used elsewhere ( where that could be I have no idea)..so it had to do the convert in Native mode and needed a reboot to do it. After reboot as it entered Easeus to do the convert, it said 100% ,,,,but next line said Errors occurred,,,, on opening to W10 on the Disk 0 160GB sata HDD, no changes had been made. So option/s now are to either Wipe the M.2, disconnect all bar the optic drive and M.2 and try install new W10 v1903 to the M.2, with it as a Gpt drive. Whatever, I think that because the 'BIOS' is now UEFI because of Motherboard, W10 is only going to install to a Gpt drive.... as it had done before when I tried to install it to the M.2 SSD. Other options are leave it as it is, buy new M.2 SSD and wait a couple days for it to arrive in post then install to it, As said I was considering buying a 500GB M.2 NVMe SSD and my mind is now decided. I had been looking at Samsung Evo Pro's or Intels, WD Black/Blue and 500GB M.2 NVMe vary in price from $250-$650 NZ, sure they have read/write speeds of 30,000+ MBps but the Intel 660P Series 512B M.2 NVMe SSD...….CL SKU 3242.....$119.00 with Sequential Write 1000 MB/s and Sequential Read 1500 MB/s well I think that be just fine for me. My Corsair Force MP 300 was like greased lightening and its R/W were nowhere near as fast as the Intel. cheers.	kioti (17360)
1463452	2019-09-02 02:54:00	Other options are leave it as it is, buy new M.2 SSD and wait a couple days for it to arrive in post then install to it, As said I was considering buying a 500GB M.2 NVMe SSD and my mind is now decided. . Why not save yourself alot of grief, just buy a ~normal~ SSD HD and be done with it. Cheaper, and I'd bet almost as fast in real world use .	1101 (13337)
1463453	2019-09-02 07:25:00	Why not save yourself alot of grief, just buy a ~normal~ SSD HD and be done with it. Cheaper, and I'd bet almost as fast in real world use . 1101 hi.... yep I considered that option also. I do have a Samsung 860 EVO SSD that I used as Storage for games/apps and I could clear that and use that as C Drive. All games/apps loaded to it are not going to be any good to me and have to be reinstalled anyway, should I reinstall W10 to a new M.2 NVMe SSD. I can get 1TB SSD for prices from $180NZ-$220NZ. I might give that a spin tonight when I get home from shopping where I am about to go -do in 20 mins. Only thing I hope is that I can install the W10 x64 v1903 onto the Samsung SSD I have... because I tell you this and I crap not not: I cannot wipe clean the M.2 Drive using any Partition App at my disposal, And I tried to instal it to the M.2 and I was informed by notification that I could not install it to the drive because it is Gpt and has to be MBR!!!!!! Now to me that is ridiculous because when I initially installed the W10 onto the M.2 drive I was told that I can only install it to a Gpt Drive and had to permit Windows to create the Gpt drive on the M.2 NVMe I have for the installation of W10 x64 v 1903 to proceed. hahahahahahhaha Really honestly. I did take a pic using my mobile phone of it saying its Gpt and has to be MBR...I will upload / attach it. Absurd!!!! Cheers...my driver has arrived so it's Hi-ho a-shopping I go ciao for now :banana: www.computerlounge.co.nz	kioti (17360)
1463454	2019-09-02 08:57:00	From your attachment, it looks like you are trying to install to Drive 0 Partition 1. It should be to Partition 4. Partition 1 only has 15mb, far too small.	Bryan (147)
1463455	2019-09-02 09:59:00	From your attachment, it looks like you are trying to install to Drive 0 Partition 1. It should be to Partition 4. Partition 1 only has 15mb, far too small. bryan hi. yep it looks like that and I know it should be Drive 0 Partition 4, and I chose that and as soon as I click to install it leaps back to that partition 1 and pops up the notice I posted in attachment. It will do the same no matter what Partition on Drive 0 I try to install to. As said I cannot wipe that NVMe drive at all because when I try I get notification showing that the drive cannot be locked because it is being accessed by other apps. I went into Task Manager and shut down the app that was accessing the NVMe SSD, then it shut down. rebooted to do the clearing of the drive and then Sods law arrived.... the damn power went down...in the street, so that put an end to that. 2 hour later power came on, and Sod's law part 2 kicked in...the W10 I was using on the 160GB Sata HDD wouldn't boot...into BIOS to try to get it sorted out as first boot and it wouldn't have it. End of day I figured that the 160GB Sata HDD had been wiped of everything ad was unallocated space! Yeah, sigh.... So I had to install W10 v1903 onto that again and start from scratch. This is becoming a real headache. I used Aomei Partition Assistant to do the ' wipe drive' on the NVMe and somehow somewhere over the rainbow it all got screwed over. So question I asking now and for some time is/are...How the hell do I wipe a Gpt Drive when as far as I know and can remember reading some time back: GPT is more Secure than MBR and cannot be Altered ( deleted is altered) It was a safeguard that came with the new UEFI take over of outdated BIOS. I did take a pic of the supposed wiping of the NVMe SSD not too long before the Power was killed up the road some where. I am of the opinion that the Boot sector of W10 on the M.2 SSD has been corrupted, and that is why it is visible in This PC and all the Disk Management apps I use but it will not boot! Even though its' Volumes all show as Healthy. I do not have Easeus Partition Manager or Aomei Partition Assistant installed again, yet, so I cannot attach any pics to show what I mean. Although, it is all visible in the attachments I showed prior to the reinstall of W10 to the 160GB Sata HDD. Where it shows the size of the drive being wiped as "149.056GB" that is the size of the Sata HDD. and I had thought it had been set to wipe the M.2 NVMe SSD, that SSD has used space of 160GB on it so my brain has figured its correct and the M.2 is being cleared of all data! How the hell it went from my selecting the M/2 SSD in Aomei to be the chosen disk to wipe to the Sata HDD I have no @#$%^^&* idea :(	kioti (17360)
1463456	2019-09-02 10:50:00	I tell ya a story about this Forced use of "GPT" happening when I installed W10 x64 v1903. It was NOT until I attempted to instal v1903 to the M.2 NVM2 SSD that I had to use GPT because of the Motherboard UEFI. Christmas last my computer at that time died. I was running AMD Athlon II x4 630 and 8GB DDR3 in Gigabyte Mboard. I had lots of probs and posted about them. Eventually in Mid-late Jan I bought all the bits for the rig I have now. All New parts. I had bought a Gigabyte AB350M-D3H Mobo many months before when I was going to buy the 1st Gen AMD Ryzen 7 CPU. That didn't happen and when I bought the AMD Ryzen 5 2400G APU, 16GB G-Skill FlareX 2955MHz DDR4 RAM, the Corsair Force MP300 M.2 NVM2 SSD and the Samsung 860 EVO SSD, I was gutted! The 2nd Gen Ryzen 5 2400G would not run in the GByte Mobo I had (1st gen only), didn't have a 1st Gen CPU to use to update the BIOS to run the APU I had so had to buy a new Mobo, so bought the Asus Prime B450M-A mobo I now have. All powered by a Corsair HX 750Watt Fully Modular PSU. A couple months later a added a used AMD Radeon Sapphire Nitro+ RX580 8GD5 GPU. Now to get to the point of the W10 v1903 and the GPT enforcement. When I built the new rig I had been using W10 x64 v 1809 and had no intention of upgrading to the Sept release of v1903 because it was buggy. When I installed W10 v 1809 onto the MP300 M.2 NVMe SSD it was installed and the drive was Basic MBR. Around June I attempted to upgrade to the v1903 and it did and I got problems with it...tried to muddle way through them, posted here in PF1 many times about the probs and in the end, as was suggested, I wiped the M.2 and Fresh installed the stable release copy of W10 x64 v1903 that I had downloaded using Media Creation tool and burned the ISO to DVD....wainuitech had posted about the stable v1903 and supplied links to get it so I did. I wiped all from the M.2 and went to install v1903 to it, and that was when the GPT was laid on me. Notification came on screen saying that W10x64 v 1903 can only be installed to GPT drive because of the Mobo UEFI . So, I gave it the thumbs up to make the M.2 SSD into a GPT Drive and the install of W10 started and finished. All was as good as gold till the balls up happened and the freezing up of the computer, resulting in my cold kill the computer and from that day on the M.2 has been Unbootable ( yet it shows as all being Heathy and Hunky- Dory in Partition apps) Now there is the tale.... W10 v1809 installed on a basic MBR M.2 NVMe SSD, but from my experience, v1903 requires GPT. And now I being informed that I cannot install v1903 to the M.2 SSD because it is GPT. AND … I cannot wipe out a GPT SSD to make it MBR. hahahahahahahhahahahaha crack me up.	kioti (17360)
1463457	2019-09-02 10:57:00	One of the reason you cant wipe the drive is because you are trying to wipe the partition from within Windows and use the program at the same time - Hence its Locked. Thats the message you get from the 1st Picture PreOS mode. Also you more than likely are having problems with all those drives /partitions attached, 12 in total showing. There's no way there is only the M.2 drive attached. To wipe the main OS drives you need to use a bootable CD or USB Drive, you cant wipe a drive while its being used. Have you tried to actually select the boot menu option (NOT the BIOS boot sequence) Had it happen a few times imaged a drive back ( esp if its a smaller drive than original) and says no boot option, select the boot option menu, select Windows Boot manager and away it goes ( it resets it). As for actually backing up - Give up Backupper - Its useless, seen so many of them fail its not even funny, it cant handle it. No point in having backups if they dont work. For ages I used to use Active@ but it has problems with insider builds, have since changed over to Macrium, you can easily mount images to extract data, or use its own VI boot which allows you to run a backed up image as a Virtual Machine. (you need Pro or above to use Hyper-V which VI uses)	wainuitech (129)
1463458	2019-09-02 11:13:00	www.techdim.com	kioti (17360)
1463459	2019-09-02 11:57:00	wainuitech hi. I assure you that when I tried to wipe the M.2 SSD there was only that attached to computer. I had disconnected all other external HDD's and the internal Samsung SSD. The pics showing all the other drives attached were taken after I had connected them to install software to use that is stored on them. I have had nothing connected bar the Optic drive and The M.2 and tried to get it to boot and it will not. At start up on a black screen is message to use a drive tha has an operating system on it. As for me getting the message that it was being used so the wipe of it couldn't be done, it did say what the app was that was using the drive and said to use task manager to close the app. I can't remember exactly what it was that was accessing the M.2 but was something to do with Windows Host service...or Service Host something ...not 100% sure of that but it was Host in the middle of the 3 words :D hmmmmm "Select the Boot Menu option (not the BIOS Boot sequence)" yep I used the Boot Menu option when I was in BIOS to choose the MP300 Boot and also the Window Boot Manager MP300. and always had the black monitor screen telling me to restart and use a device that has a boot or use a DVD ?CD to ass a boot to it...… As I said also, no matter what I do in BIOS, any changes I make and I hit F10 to save changes, I am informed that I have not made any changes. As for wiping drives, I have used Easeus Partition Master to wipe HDD's and have all Unallocated Space because I had to do it because when I tried to use the OS Instal DVD to 'Delete' the existing OS it wouldn't do it. That was a few year back. Now, I cannot even get Easeus to wipe the M.2 SSD. I set it to do it, it shows Unallocated space, click the Apply tab, the screen blinks and lo n behold, there it all is where it was meant to be gone …. SMH :D. And as I said, I cannot use the W10 v1903 DVD to delete the data on the M.2 and install W10 v1903 to it...because it is a GPT Drive/partition I am being informed. MH again. "Select the Boot menu option" do you mean pressing F8 at start up of computer??? ..I will do another reboot and hit F8 and see what I get...If I get option to use the M.2 I will select it and see what transpires. If its still a no-go it can stay as it is. I have ordered and paid for the Intel 660P Series 512B M.2 NVMe SSD and will wait for it to arrive and out the existing M.2 aside for a while. I am interested in seeing what happens when I go to install W10 x64 v 1903 to it. GPT or MBR ( yeah I have to decide that when I Initialise the Drive) Off to reboot and hit the F8 key :D cheers	kioti (17360)
1463460	2019-09-02 12:39:00	wainuitech hi I am back. I rebooted and used the F8 key. Selected both the Windows Boot manager (Force MP300) and the Force MP300 entries and both failed to open to usable System. Is a lost cause I thinking. Here are the pics. Sorry, they are a little blurred because I using Mobile phn camera, but they are legible.	kioti (17360)
1 2 3 4 5 6 7 8 9 10 11