5TB drive not working on My cloud

I have it formatted as NTFS. It shows the drive under the USB tab but shows 0 space available and it never shows under Shares. My Cloud is running v04.06.00-111 firmware.

The drive is a Seagate Backup+

I have seen others posting that 5TB drive size works just fine.

What My Cloud device do you have? Did you format the drive BEFORE putting it into the NAS? Typically, you let the NAS do the formatting.

Are you replacing a drive that failed? If so was it 5tb or smaller?

Thanks for the reply. I have the original single disk My Cloud device. The 5TB drive is connected to the back of the My Cloud into the USB port. I formatted the drive as NTFS Data Drive.

Mine looks like this but it is the version that is no longer supported:

v04.06.00-111 indicates the OP is using a first generation single bay My Cloud.

@Mark_Knight

Do you have it set up by the User Manual, Chapter 12? Does the Seagate Drive meet the requirements for working with a My Cloud device?

User Manual

Could be a mounting problem with the v4.x first gen single bay My Cloud firmware. Check the USB drive to see if it has more than one partition configured. Could be there are two partitions with the data partition the second one of the two and the v4.x firmware gets hung up on using the first partition rather than the second.

Some troubleshooting suggestions if you haven’t tried them yet.
Connect the USB drive direct to the My Cloud USB port. Avoid using a USB hub while troubleshooting.
Power off the My Cloud and USB drive, remove the power adapter from power for several minutes, then reconnect the power adapter to power and power on the My Cloud. Once booted to a blue front LED, check if the USB drive is showing up correctly. If the USB drive is powered, remove it from power at the same time you remove the power for the My Cloud. Reconnect the power for both at the same time.

No issues with a 5TB Seagate Backup+ Hub external powered USB drive being seen by a first gen single bay My Cloud.


1 Like

Thanks for the reply Bennor. I only get the blinking amber LED on boot and never the Blue LED on powering on the MY Cloud device. I think the Blue LED is burnt out? It did go RED on my one time and I had to powercycle it. I do have the LED set to on under Energy Saver so not sure why no Blue LED. The only drive that seems to work connected to the back of the device is my older Fantom Green 2TB green drive (see first photo). It comes up just fine and I can map to it in Windows, so at least we know it is not an issue with the My Cloud device? I have tried a 16GB thumb drive that is formatted NTFS and it will not even show as connected. Even tried a WD 3TB drive connected and it also does not show as even being connected? The 5TB Seagate that you show in your photo, is that yours?, If so how is that formatted? I have formatted mine several times and even deleted the entire partition and recreated it and reformatted it but with no success.

Now I am doing all this partitioning and formatting on Windows 11 machine, perhaps I should try doing on my Linux machine?

Any other ideas would be greatly appreciated as I am at a complete lose why only one drive seems to play happy with my WD.

Oh and I ran a test on the system to make sure it would pass:

Yes, its my Seagate 5TB Backup+ Hub drive. Bought it many years ago from Costco. Its formatted for NTFS.

One suggestion. Try changing your external Seagate USB hard drive’s name if you can. Also try a different USB cable if you can. Even try using a USB hub as well as a basic troubleshooting step. Unfortunately this isn’t a uncommon issue on the first gen single bay My Cloud. Been a number of past discussions of drives not mounting properly.
https://community.wd.com/search?q=%23personal-cloud-storage%3Awd-my-cloud%20usb%20hard%20drive%20not%20seen%20order%3Alatest

WD has a support document:

External USB Drive Will Not Mount, Not Seen or Detected by a My Cloud

Do you mean the “Seagate Backup+ Desk” friendly name? or the HD1 name that I gave it when I formatted it? Is that Seagate name even changeable?

Try changing the “HD1” name you gave it.

So here is what I have tried. I brought the Seagate 5tb and the Fantom GreenDrive both to my laptop and looked at them both in Minitool Partition Wizard. The Fantom drive that does work with the WD My Cloud was formatted as ext4. So I moved the Seagate 5tb over to my linux machine and formatted to the same ext4 and changed the name from HD1 to 5TB. I then connected it back up to the WD My Cloud using a different USB cable. After all that same exact problem:

If you haven’t done so already, you may want to take some time to read through the many past posts about the USB drive 0k (including a few of mine) to see if anything in the past discussions may help.

https://community.wd.com/search?q=%23personal-cloud-storage%3Awd-my-cloud%20usb%200k

For what ever reason the My Cloud just has trouble with certain USB enclosures. Had a 1TB Toshiba external USB 3.0 drive that for ages wouldn’t mount properly, showed 0K. Others (in the above search link) indicate having trouble with certain Seagate external drives. Various suggestions range from editing the /var/local/autoMount/autoMount.db file to remove the problematic USB enclosure entry, to using a different USB enclosure/drive.

1 Like

Yeah I had read through those post, thanks again for the link. Great minds think alike. I am in the process of moving the 5TB drive into the Fantom encloser to see what happens. Seagate was a pain to get open but there was a great YouTube video that walks you though it.

Well the drive enclosure of the Seagate is definitely the culprit. I now have to figure out why it is only showing 600MB out of a 5TB drive. :laughing:

Got it to work. I ended up connecting the Seagate up to my Linux and made some changes to the “Edit Mount Options…” It was set to “User Session Defaults” and there is a slide button there. I slide that to the left and changed “Identify As” from the long Seagate name to a short name and checked the “Mount at system start up”. I then formatted it as NTFS and connected to my WD My cloud and as you can see it is showing in my interface and as a share. Hope this helps someone down the road or future me when I forget all this again in 2 weeks. :laughing:

2 Likes

@Mark_Knight, If your 5TB drive isn’t working on My Cloud, first check if the drive is properly formatted (NTFS/exFAT), supported by My Cloud, and that you’re using the latest firmware. Try rebooting both devices. For more detailed assistance, visit My Cloud Support.

Good to see you got it to work. Interesting issue that it was the long Seagate name causing the problem. Just one more of the quirks to add to the very long list of quirks on the OS3 single bay My Cloud.

1 Like

In case you missed what the OP initially posted, they stated they formatted the USB drive for NTFS and they are running the latest (last available) firmware for their end of support OS3 My Cloud device:

I have it formatted as NTFS.
…
My Cloud is running v04.06.00-111 firmware.

Again FYI, the OP indicated they are using “v04.06.00-111 firmware” in their initial post. The v04.06.00-111 firmware means they are running a OS3 single bay/single drive My Cloud device. The My Cloud Home is an entirely different device than the My Cloud line of devices. The My Cloud Home uses a entirely different operating system than the My Cloud line of devices. The My Cloud Home product sales page you provided as a support page does not apply.

The correct support link for the single bay/single drive My Cloud is:
https://support-en.wd.com/app/products/product-detailweb/p/126

This is what the single bay/single drive My Cloud looks like:

This is what the single drive My Cloud Home looks like:

Thank you for the help. Your posts always give me another set of eyes that help me think in other directions that I would not even guess to try.

Still working fine this morning even after I disconnected the 5TB from the WD and connected it back up so seems to be solid now.

Still not sure why I do not have a Blue LED in the front of the My Cloud but hey as long as it is still running even after all these years! :sweat_smile: