Cannot see my HDD in MyWDCloud UI 0.00 capacity

My Cloud OS 5 Personal & Network Attached Storage My Cloud
1

Hi All,

I have clean my HDD and seems that my wd cloud is not seeing the HDD anymore, 0 capacity and format is grey-out
When i connected to the device via ssh i do have this error message -
EXT4-fs (sda2): VFS: Can’t find ext4 filesystem

when running fdisk -l i have this info:
Filesystem 1K-blocks Used Available Use% Mounted on
%root% 55529 35063 17599 67% /
/dev/ram0 55529 35063 17599 67% /
mdev 257248 32 257216 0% /dev
/dev/sda3 999320 200604 729904 22% /boot
/dev/sda7 999576 1548 971324 0% /usr/local/config
/dev/loop0 96512 96512 0 100% /usr/local/modules
tmpfs 1024 256 768 25% /mnt
tmpfs 40960 1024 39936 3% /var/log
tmpfs 102400 5184 97216 5% /tmp

Could you please advise how can i see my 4TB HDD again, so i can start my backup

Thanks,

2

If you have a single bay/single drive My Cloud unit, try doing a System Only Reset through the My Cloud Dashboard, sometimes that will fix the 0K capacity. If you have a multi bay My Cloud unit you may have to go through the process of selecting JBOD or RAID first under Storage before formatting the drives.

My Cloud: Changing the RAID Mode

3

I do have single bay, and i tried to do system only reset, but this didn’t resolve the issue.
I do mind to loose the data inside, but for some reason i cannot even format it via the dashboard,

anything else i can do?

4

Some additional suggestions in the following WD Knowledge Base Article:

My Cloud: Dashboard Zero Capacity, No Data Volume Mounted and Shares Not Accessible or Missing

One can also see if performing a Quick Restore or Full Restore via the My Cloud Dashboard > Settings > Utilities page solves the issue. Just note a quick restore or full restore may destroy any user data on the drive.

My Cloud:System, Quick and Full Restore a (single bay) My Cloud

5

When i tried to run full restore via the dashboard it seems there is no progress for more than 1 hr - please see the attachment.

full restore
full restore1120×570 36.2 KB

When i ran dmesg command i received these errors -
[ 83.269848] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3922, 163 clusters in bitmap, 32768 in gd
[ 83.279255] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3923, 375 clusters in bitmap, 32768 in gd
[ 83.288853] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3924, 462 clusters in bitmap, 32768 in gd
[ 83.298197] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3925, 919 clusters in bitmap, 32768 in gd
[ 83.307514] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3926, 1879 clusters in bitmap, 32768 in gd
[ 83.316916] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 3927, 165 clusters in bitmap, 32768 in gd
[ 83.326514] JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There’s a risk of filesystem corruption in case of system crash.
[ 83.363141] JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There’s a risk of filesystem corruption in case of system crash.
[ 83.374471] JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There’s a risk of filesystem corruption in case of system crash.
[ 101.863698] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 15920, 23894 clusters in bitmap, 24646 in gd
[ 101.873533] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 15921, 11666 clusters in bitmap, 32763 in gd
[ 101.883334] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 15922, 16807 clusters in bitmap, 32768 in gd
[ 101.893082] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 15923, 9726 clusters in bitmap, 32768 in gd
[ 101.902803] JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There’s a risk of filesystem corruption in case of system crash.
[ 110.927507] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 5024, 1089 clusters in bitmap, 24543 in gd
[ 110.936939] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 5025, 1356 clusters in bitmap, 32738 in gd
[ 110.946343] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 5026, 602 clusters in bitmap, 32768 in gd
[ 110.955650] EXT4-fs error (device sda2): ext4_mb_generate_buddy:758: group 5027, 1380 clusters in bitmap, 32768 in gd
[ 110.965073] JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There’s a risk of filesystem corruption in case of system crash.
[ 332.006283] EXT4-fs (sda2): error count: 31936
[ 332.009444] EXT4-fs (sda2): initial error at 1682881657: ext4_mb_generate_buddy:758
[ 332.015837] EXT4-fs (sda2): last error at 1682915702: ext4_mb_generate_buddy:758

Can i delete/format the HDD from scratch?

6

A full factory restore can take quite a bit of time. If you remove the second gen single bay hard drive and format the entire hard drive then you have to reconfigure the drive for use in the My Cloud enclosure. This includes properly partitioning and formatting then copying/installing the single bay second gen firmware. There are various methods of “unbricking” a second gen single bay My Cloud hard drive one can find using the forum search feature. Here is one set of directions:
https://wd.hides.su/fox_exe/WDMyCloud-Gen2/_Unbricking_en.txt
https://wd.hides.su/fox_exe/WDMyCloud-Gen2/
usbrecovery.tar.gz
uImage-wdrecovery
uRamdisk-wdrecovery

7

Could you please help me how can i install OMV OS, since i tried to follow the guide in the website, but seems i have this error -
root@wdmc:~# apt-get install --force-yes openmediavault-keyring

Reading package lists… Error!

W: Duplicate sources.list entry Index of /public erasmus/main armhf Packages (/var/lib/apt/lists/packages.openmediavault.org_public_dists_erasmus_main_binary-armhf_Packages)

E: Problem syncing the file - sync (5: Input/output error)

E: Write error - write (30: Read-only file system)

E: IO Error saving source cache

E: Problem renaming the file /var/cache/apt/srcpkgcache.bin.WTfw0x to /var/cache/apt/srcpkgcache.bin - rename (30: Read-only file system)

E: Failed to truncate file - ftruncate (30: Read-only file system)

E: Problem renaming the file /var/cache/apt/pkgcache.bin.503PxL to /var/cache/apt/pkgcache.bin - rename (30: Read-only file system)

E: The package lists or status file could not be parsed or opened.

8

Only suggestion I can give is read the huge topic in the OS3 subforum on installing Open Media Vault. For example see the following link to a post in that discussion, and several posts in that discussion that follow it where a similar error is mentioned:
https://community.wd.com/t/clean-os-debian-openmediavault-and-other-firmwares/93714/257

9

Thanks for the detailed info!
Finally i decided to go with the original firmware, but seems that after i re-image my HDD, i cannot update the firmware, everything is grey-out even after 4sec reset - any clue what should i do?
Because i still see my HDD 4TB in BAD state.

image
image1858×1272 161 KB

10

Try performing a System Only Reset via the Utilities menu if you haven’t done so already. That sometimes fixes issues.

11

Unfortunately, this system reset didn’t help…also format for the HDD or Scan HDD is gray-out, i really don’t know what is wrong here…
This is what i do see in Dashboard -

image
image1972×1252 213 KB

And the HDD is not being detect or can be used
Ok, now i used different browser (Safari) and seems the firmware update was grayed-out after 3 seconds so i just click on it faster and seems now i have different error -
image
image1200×422 12.8 KB

any suggestions?

12

The diagnostics indicate an error, what does that indicate?
You may need to pull the hard drive and attach it to a computer and, using a partition manager program that supports Linux partitions, check the EXT4 (data) partition for it’s capacity and if there are any errors present, or that that specific partition is even there.

Edit to add: It also appears the OS3 v2.x firmware you are running is older. If the Manual Firmware update option works one can try downloading the latest/last OS3 v2.42.115 firmware and update manually then try updating to the OS5 v5.x firmware. The 2.10.302 firmware is the initial release firmware for the second gen single bay My Cloud from way back in 2015.