- Jan 29, 2010
- 5
- 0
- 18,510
I just bought a new gaming laptop, ASUS ROG 15.6". The model is GU501GM.
I wanted to upgrade the C drive NVMe disk from 128 to 500G so bought the memory and an enclosure with a USB-C port. The manual says it can't be used to boot but I did not need to boot from the new disk when mounted externally.
Ultimately went with Clonezilla. It was hack-ish but it worked when I chose the 'device/device' option. (ie I cloned the 128 onto the 500. Maybe stupid move?)
The new disk boots up fine, except it shows up EXACTLY like the old disk and no sign anywhere of the lost space.
DISKPART in the Win 10 command line shows that disk 0 has capacity of 500 but my attempts to extend, etc say I have no room left.
I figured I just need to wipe the 500 of any volumes but...
Somehow the original disk got corrupted and it won't boot. The data is available as a data drive fine, assigned as E: (when mounted in the external enclosure). But Win 10 setup can't repair it. EaseUS 'SuperScan' says I have overlapping partitions in red letters; the only indication of what my problem might be.
My dilemma:
So I have a 500 that only boots as 128, and the original 128 that won't boot anymore.
This is a new gamer-grade laptop and I'm on the precipice of bricking it and I stopped while it still works. Until I figure out how to make a second NVMe that boots with a copy of the original partitions, I can't do anything else except buy another NVMe to experiment on, but I have no need of a spare drive after I'm done. I do not want to experiment on the original disk but would rather get it to boot again.
My tech-biorhythm must have been at an all time low yesterday because it was a day when nothing I touched would work right, including signing onto this forum! (plus I started my day when I got out of bed to discover my custom 3D printer had smashed it's head into pieces and blew the expensive controller board.)
So far I have:
-A thumbdrive with FreeDOS that would not boot.
-A Windows 10 install thumbdrive that has a command line that makes no sense. It recognizes DIR but not LIST or HELP. wtf?
-Clonezilla on a thumbdrive that works, but caused my problem, and seems to have no disk tools. I also don't know Linux cli at all.
Any help to get out of this hell-hole would be highly appreciated!
thanks
I wanted to upgrade the C drive NVMe disk from 128 to 500G so bought the memory and an enclosure with a USB-C port. The manual says it can't be used to boot but I did not need to boot from the new disk when mounted externally.
Ultimately went with Clonezilla. It was hack-ish but it worked when I chose the 'device/device' option. (ie I cloned the 128 onto the 500. Maybe stupid move?)
The new disk boots up fine, except it shows up EXACTLY like the old disk and no sign anywhere of the lost space.
DISKPART in the Win 10 command line shows that disk 0 has capacity of 500 but my attempts to extend, etc say I have no room left.
I figured I just need to wipe the 500 of any volumes but...
Somehow the original disk got corrupted and it won't boot. The data is available as a data drive fine, assigned as E: (when mounted in the external enclosure). But Win 10 setup can't repair it. EaseUS 'SuperScan' says I have overlapping partitions in red letters; the only indication of what my problem might be.
My dilemma:
So I have a 500 that only boots as 128, and the original 128 that won't boot anymore.
This is a new gamer-grade laptop and I'm on the precipice of bricking it and I stopped while it still works. Until I figure out how to make a second NVMe that boots with a copy of the original partitions, I can't do anything else except buy another NVMe to experiment on, but I have no need of a spare drive after I'm done. I do not want to experiment on the original disk but would rather get it to boot again.
My tech-biorhythm must have been at an all time low yesterday because it was a day when nothing I touched would work right, including signing onto this forum! (plus I started my day when I got out of bed to discover my custom 3D printer had smashed it's head into pieces and blew the expensive controller board.)
So far I have:
-A thumbdrive with FreeDOS that would not boot.
-A Windows 10 install thumbdrive that has a command line that makes no sense. It recognizes DIR but not LIST or HELP. wtf?
-Clonezilla on a thumbdrive that works, but caused my problem, and seems to have no disk tools. I also don't know Linux cli at all.
Any help to get out of this hell-hole would be highly appreciated!
thanks
Facebook
Twitter
Instagram