Is there a 8 tb img here and step by step instruction


#1

My 4tb cloud took a dump Its a first gen WDBCTL0040HWT-00 So I now have a 8tb which I would like to put in. So been reading everywhere on this and getting confused ! So do you put the img on the drive it self ? and what commands do I need to do ?


[GUIDE] How To Unbrick your 2TB/3TB/4TB My Cloud
#2

See one of the various “unbricking” guides using the forum search feature (magnifying glass icon upper right). You will need to know which My Cloud version you are using, first gen v4.x or second gen v2.x as the directions and files for unbricking each are different.

User Fox_Exe has unbricking directions which some have found useful.
First Gen: https://drive.google.com/drive/folders/0B_6OlQ_H0PxVZTBtM3EyRVhDVms
Second Gen: https://drive.google.com/drive/folders/0B_6OlQ_H0PxVRXllYjY5RG1CZEU

Some of us have successfully used the unbricking guides when adding or replacing a hard drive in the single bay My Cloud enclosure. In my case I used a 2TB image for my first gen My Cloud when replacing a dead 4TB drive with a 1TB spare drive I had sitting around.


#3

Does anyone have a “useful” answer, other than telling someone how to use the search function? Obviously if the question is being asked, someone has taken advantage of the magnifying glass search function and not found an answer. I too have the same question as Rick.


#4

What I posted above IS a useful answer. You do not need an 8TB image or any image specific to the size of your hard drive. Just use the directions from Fox_Exe’s links or one of the past unbrick methods discussed elsewhere. I’ve just successfully installed an 8TB drive into a first gen single bay enclosure using Fox_Exe’s first gen directions linked to above.

In the process of upgrading the firmware to the latest.

Edit to add: Typically (in the past) if the total hard drive size is incorrect post unbrick that is often fixed by performing a 40 second reset.


#5

Thank you, that is quite useful information. Some posts say that you must know the correct sector numbers for the size of hard drive you are upgrading to, I think that is what throws most people off. Based on the links and your description, it makes it a lot more clear.


#6

Well followed everything after the 40 seconds reset RED light. So I can log in its asking for Firmware update so I click yes it returns error saying the drive isn’t big enough.
Its a 8 tb drive with a 2 tb image and the rest of the drive I formatted to EXT4 but its only showing 2 tb on the login


#7

Which directions did you follow?

If you have a first gen v3.x/v4.x single bay My Cloud, the Fox_Exe directions linked above work. Here is the direct link to the text file from the link above for first gen My Cloud units.
https://drive.google.com/file/d/0B_6OlQ_H0PxVbzZac0plbkZKeGM/view

One just needs to download the .tar.gz file from the correct location (click here for the original_v04.01.02-417.tar.gz) as the URL in the directions are broken. In the directions I used there isn’t an 2TB image file. Instead one uses a “.tar.gz” file and once unbricked one upgrades to the latest firmware as normal through the Dashboard.


#8

I have a duel boot pc with Ubuntu and use the graphical interface by applying the img. I tried to use the terminal window but his commands do not work :frowning: When it comes to using Ubuntu I am very limited Oh well that you for trying to help me


#9

The commands work fine in the terminal window in Ubuntu. However, one may have to use “sudo” prior to issuing each command if they don’t have proper root access in Ubuntu. I use Ubuntu and the terminal window with the directions above to put several different sized hard drives into my first gen My Cloud enclosure.

Example Sudo command: sudo parted /dev/sdb

Currently an 8TB drive is working fine in a first gen My Cloud enclosure.


#11

I typed in sudo fdisk -1 it returns back with invalid option – “1”


#12

That’s because it’s not the number 1, it’s a lower case L - for ‘list’

You might want to conider copying and pasting commands if you don’t understand what they are doing, or what the options might mean.

Just to check; did you run parted and create all eight partitions?


#13

here is the screen after the return of L

I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xda96ad4a

Device Boot Start End Blocks Id System
/dev/sda1 * 63 1933040064 966520001 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.
/dev/sda2 1933041662 1953523711 10241025 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 1933041664 1934993407 975872 82 Linux swap / Solaris
/dev/sda6 1934995456 1953523711 9264128 83 Linux

WARNING: GPT (GUID Partition Table) detected on ‘/dev/sdb’! The util fdisk doesn’t support GPT. Use GNU Parted.

Disk /dev/sdb: 8001.6 GB, 8001563222016 bytes
255 heads, 63 sectors/track, 972801 cylinders, total 15628053168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn’t contain a valid partition table
rickt1962@rickt1962-Aspire-5517:~$


#14

I am now stuck

print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) mklabel gpt
Warning: Partition(s) on /dev/sdb are being used.
Ignore/Cancel?


#15

It is sudo fdisk -l not 1.

As cpt_paranoia suggests. I may be better (and quicker than typing) to copy the commands and paste them into the terminal window (using a mouse right click). Makes it easier than typing.

Typically I get an error or two when following the first gen directions. Usually when hitting the step to unmount the RAID (step 8). I usually ignore the error message. I also typically reboot the computer (reloading Ubuntu) after step 6 where I create the partitions on the drive. I typically rerun apt-get update && apt-get install mdadm parted after the reboot too.

It may take a few tries the first time going through the steps to get things right. Now that I’ve run these steps several times on several different hard drives, its pretty straight forward and fairly easy when using the copy/past method. It helps to download the directions to a text file on the PC or usb flash drive along with the v3.04.01-23 or v3.04.01-230 or v4.01.02-417 file. That way you can have the terminal window open and the text file directions open at the same time to copy commands from one window to the other.


#16

One uses fdisk -l or parted -l (sudo fdisk -l or sudo parted -l) to find what hard drives are connected to the Linux computer. One would select the correct /dev/sdx entry for the hard drive to be used for the My Cloud. For example on my system it was /dev/sdb (yours may be different).

Then one would run the parted utility with the correct /dev/sdx value.
Example: sudo parted /dev/sdb

One would then type in print to list the partitions, if any, on the hard drive. If there are existing partitions on the hard drive, one needs to remove them BEFORE continuing to the next step of creating the new partition table. To remove a partition, one would enter (for example): rm 1. One would continue entering the rm command plus partition number until all partitions are deleted/removed.

Once the partitions are removed one can then proceed to create the new partitions. Make sure to use the exact numerical values listed.


#17

Ok I started over using copy paste here is where I am stuck

rickt1962@rickt1962-Aspire-5517:~$ sudo fdisk -l
[sudo] password for rickt1962:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xda96ad4a

Device Boot Start End Blocks Id System
/dev/sda1 * 63 1933040064 966520001 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.
/dev/sda2 1933041662 1953523711 10241025 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 1933041664 1934993407 975872 82 Linux swap / Solaris
/dev/sda6 1934995456 1953523711 9264128 83 Linux

WARNING: GPT (GUID Partition Table) detected on ‘/dev/sdb’! The util fdisk doesn’t support GPT. Use GNU Parted.

Disk /dev/sdb: 8001.6 GB, 8001563222016 bytes
255 heads, 63 sectors/track, 972801 cylinders, total 15628053168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn’t contain a valid partition table
rickt1962@rickt1962-Aspire-5517:~$ sudo print
rickt1962@rickt1962-Aspire-5517:~$ print
rickt1962@rickt1962-Aspire-5517:~$ mklabel gpt
No command ‘mklabel’ found, did you mean:
Command ‘mlabel’ from package ‘mtools’ (main)
mklabel: command not found
rickt1962@rickt1962-Aspire-5517:~$ sudo mklabel gpt
sudo: mklabel: command not found
rickt1962@rickt1962-Aspire-5517:~$ parted /dev/sdb
WARNING: You are not superuser. Watch out for permissions.
Error: Error opening /dev/sdb: Permission denied
Retry/Cancel? c
rickt1962@rickt1962-Aspire-5517:~$ sudo parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) print
Model: ATA ST8000DM004-2CX1 (scsi)
Disk /dev/sdb: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 8002GB 8002GB ext3

(parted) remove 1
align-check TYPE N check partition N for TYPE(min|opt)
alignment
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partition NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
resizepart NUMBER END resize partition NUMBER
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
align-check TYPE N check partition N for TYPE(min|opt)
alignment
check NUMBER do a simple check on the file system
cp [FROM-DEVICE] FROM-NUMBER TO-NUMBER copy file system to another partition
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkfs NUMBER FS-TYPE make a FS-TYPE file system on
partition NUMBER
mkpart PART-TYPE [FS-TYPE] START END make a partition
mkpartfs PART-TYPE FS-TYPE START END make a partition with a file system
resizepart NUMBER END resize partition NUMBER
move NUMBER START END move partition NUMBER
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resize NUMBER START END resize partition NUMBER and its file
system
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted) mklabel gpt
Warning: Partition(s) on /dev/sdb are being used.
Ignore/Cancel? i
Warning: The existing disk label on /dev/sdb will be destroyed and all data on
this disk will be lost. Do you want to continue?
Yes/No? y
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4828M 100%
(parted) mkpart primary 4624M 4724M
(parted) mkpart primary 4724M 4824M
(parted) mkpart primary 4824M 4826M
(parted) mkpart primary 4826M 4828M
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.

rickt1962@rickt1962-Aspire-5517:~$ mkfs -t ext4 /dev/sdb4
mke2fs 1.42.9 (4-Feb-2014)
mkfs.ext4: Permission denied while trying to determine filesystem size
rickt1962@rickt1962-Aspire-5517:~$ sudo mkfs -t ext4 /dev/sdb4
mke2fs 1.42.9 (4-Feb-2014)
/dev/sdb4 is apparently in use by the system; will not make a filesystem here!
rickt1962@rickt1962-Aspire-5517:~$ sudo mkswap /dev/sda3
/dev/sda3: No such file or directory
rickt1962@rickt1962-Aspire-5517:~$ sudo mdadm --stop /dev/md*
mdadm: error opening /dev/md*: No such file or directory
rickt1962@rickt1962-Aspire-5517:~$ mdadm --stop /dev/md*
mdadm: must be super-user to perform this action
rickt1962@rickt1962-Aspire-5517:~$


#18

By chance did you forget to run: sudo apt-get update && apt-get install mdadm parted at the very beginning before starting step 1?

You have to run the sudo parted /dev/sdx (where x is the location of your drive) before running the print or mklabel gpt command


#19

Yes sudo apt-get update && apt-get install mdadm parted

My drive location is USB how do I direct it to that ?


#20

One can use the sudo fdisk -l (note that is an l not a 1, the support forum is changing it) command to list the attached hard drives both internal and external on the Linux system/computer. Make note of the drive name for the drive you want to run the unbricking steps on. Typically the drives are listed something like;/dev/sda, /dev/sdb, /dev/sdc, /dev/sdd, etc.

So for example if the drive you want to unbrick on /dev/sdb then one would use that going forward when referencing the drive to be unbricked. Some example commands using the example drive location.

sudo parted /dev/sdb
sudo mkfs -t ext4 /dev/sdb4
sudo mkswap /dev/sdb3

#21

Here is what I get from Fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xda96ad4a

Device Boot Start End Blocks Id System
/dev/sda1 * 63 1933040064 966520001 7 HPFS/NTFS/exFAT
Partition 1 does not start on physical sector boundary.
/dev/sda2 1933041662 1953523711 10241025 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 1933041664 1934993407 975872 82 Linux swap / Solaris
/dev/sda6 1934995456 1953523711 9264128 83 Linux

WARNING: GPT (GUID Partition Table) detected on ‘/dev/sdb’! The util fdisk doesn’t support GPT. Use GNU Parted.

Disk /dev/sdb: 8001.6 GB, 8001563222016 bytes
255 heads, 63 sectors/track, 972801 cylinders, total 15628053168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
rickt1962@rickt1962-Aspire-5517:~$