Hi everyone,
I’m facing a critical issue with my My Cloud EX4100 after a recent system error. I’m hoping someone from the community or staff can help me “re-sync” the Web Dashboard with the actual state of the drives.
The Problem:
-
The Web Dashboard shows no RAID volume configured and prompts me to create a new one (which would wipe my data).
-
All four disk LEDs are solid red.
-
The “Import RAID” option is nowhere to be found in the UI.
The RAID actually seems perfectly fine at the OS level. When I log in via SSH, cat /proc/mdstat shows the array is active and healthy:
root@Fornax ~ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid5 sda2[4] sdd2[3] sdc2[5] sdb2[6]
8778211776 blocks super 1.0 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 2/3 pages [64KB], 65536KB chunk
md0 : active raid1 sdd1[3] sdc1[2] sdb1[1] sda1[0]
2094080 blocks super 1.2 [4/4] [UUUU]
bitmap: 0/1 pages [0KB], 65536KB chunk
By manually forcing the Samba service to start via SSH, I can access all my files over the network. The data is there and intact, but the NAS “thinks” it’s broken.
What I’ve tried:
-
Running a disk scan (I can hear the disks working, but the UI doesn’t update).
-
Searching for any way to “Mount” or “Import” the existing md1 volume through the UI.
-
Multiple reboots (the situation remains the same: CLI is fine, UI is blind).
Is there a specific command or a configuration file (like config.xml or a system database) I need to edit/refresh to force the Dashboard to recognize the existing md1 array and turn the LEDs back to blue?
I want to avoid “creating” a new RAID because I don’t want to risk the initialization process wiping the partition table.
Any help would be greatly appreciated!
The My Cloud EX4100 is showing all four disk LEDs as red and the Web Dashboard reports no RAID, but the RAID arrays are actually healthy at the OS level and all files are accessible via Samba. The issue is caused by missing or corrupted system configuration files that the Dashboard uses to detect RAID, such as mdadm.conf or other WD NAS config files. To fix this without risking data loss, back up the configuration files, regenerate mdadm.conf from the active arrays, and restart the wdmcserver service. This should make the Dashboard recognize the existing RAID, restore the LED status, and keep the data intact.
Hi everyone,
I’m writing an update to share how I finally solved this issue.
After some deep diving into the system via SSH, I managed to fix it myself by investigating the diskmgr executable and its suggested commands using the -6 option.
I found a specific command that allows you to rebuild/re-link the RAID (even if the array is technically healthy) and, most importantly, communicate the correct status to the Web Dashboard. This finally resynced the internal system state with the UI.
For anyone facing the same problem, here is the exact sequence of commands I used via SSH:
-
Check the RAID status:
cat /proc/mdstat
-
Manually assemble the array:
mdadm --assemble /dev/md1 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2
-
Create the mount point and mount the drive:
mkdir -p /mnt/HD/HD_a2
mount /dev/md1 /mnt/HD/HD_a2
-
Run the diskmgr command to fix the Dashboard and sync the status:
diskmgr -d -v1 -m5 -a /dev/md1 -ksdasdbsdc -csdd -v2 -3 -m2 -ksdasdbsdcsdd -b
.
The results:
-
The Web Dashboard is now fully functional again.
-
The drive LEDs immediately turned from red back to blue.
-
Bonus: This process actually recovered additional space by creating a new volume that the Dashboard UI wouldn’t allow me to create before (I am running a mix of 3x4TB and 1x1TB drives).
I hope this helps anyone else stuck with a “healthy” RAID that the official software refuses to recognize!
P.S.: I don’t know how to regenerate the mdadm.conf file. Can you please elaborate, @kencarter556?
1 Like
