Clone hard drive to ssd gparted2/3/2024 If I can do that, I need a different command syntax for the mkpart command that specifies the partition number?Īt least that explains why there’s no room left. I did up the size of the SSD to 256GB so I have no clue what the problem is with the script of commands issued other than the previous command that stipulated 100%? Shouldn’t #4 be done last when 100% is stipulated? If so, I can rm 4 and then allocate partitions 5, 6, 7 & 8 and then #4. Remove all: Type “remove 1” (where 1 - number of partition) I had two drives for my emulation build - a 240 and a 1TB - I put Batocera on the 1TB and Windows on the 240 - after a little while I’ve decided I want them the other way round as I’ve purchased some huge PC games. sgdisk /dev/sdX -R /dev/sdY sgdisk -G /dev/sdY The first command copies the partition table of sdX to sdY (be careful not to mix these up). Then use the sgdisk command (man page here) to replicate the partition table. Type “print” for see what partitions exist on disk Install gdisk which is available in the Ubuntu Universe repositories. Use fdisk -l (or parted -l) for see what name have you WD’s HDD.I’m successful in all steps within the un-bricking scenario until the last command in the following sequence: One can use any number of Linux boot/live cd disc distro’s to boot their PC to perform the various unbricking steps. All drives worked fine after the unbrick process (once I typed it correctly ) in the My Cloud enclosure. I’ve used the first gen unbrick process on a 250GB drive (several times), a 1TB drive, and finally an 8TB drive. One would copy the user data to partition #4 if I remember correctly (off hand). Generally what it is advisable to do, with a first gen, is to perform the unbrick steps, then boot the drive in the enclosure (and perform a 40 second reset) so the firmware properly resizes the drive, Then one could (if they wanted) power down the drive, remove it from the enclosure and attach it to a PC’s SATA port to copy data at a faster rate via the PC’s SATA ports and proceed to copy user data from the old My Cloud drive to the new SSD drive. I’ve used several different hard drives within a first gen My Cloud enclosure. Not sure how long it takes on a second gen as I don’t have one. Like indicated above, one can typically “unbrick” a first gen in under half an hour. All one is doing with the “unbrick” process is configuring the drive to have the proper partitions (in proper formats) and then pushing the My Cloud firmware to the drive. The general steps are: Boot off a liveCD (disto or Rescue Disk) Create the partition table on the new disk (GPT recommended) Create the desired partitions on the disk. Have both disks connected when running it. The term “unbrick” as used in this subforum is just a catch all term for starting from scratch when one cannot boot a drive in the My Cloud enclosure or when replacing the My Cloud drive with a different hard drive. To get more exact suggestions, post the output from sudo parted -l please. One can use what we call the “unbrick” process on a brand new drive. , I’m first essentially told that I don’t have a “brick”,
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |