Forum WD Community

Hi everyone, recently i face the new problem, i have WD my passport ultra, i bought it like ten years ago or more. about one week ago i cant access my files on it. but the thing is, my hardisk is still have the light on, detected on device manager and no problem detected. when i open the disk management, it shown unallocated. can you guys help me how to solve this problem? i connect it in to type c port on my windows laptop

I’m looking for advice or help getting a Western Digital warranty replacement escalated. I opened an RMA for a WD Red Plus drive, model Model WD60EFPX-68C5ZN0 (“Made in Thailand MAY 2026”). The RMA was created on September 14, 2026. The return shipment (UPS) was delivered to Western Digital/Budapest Center for Europe on September 16, 2026, and Western Digital oddly confirmed that they had received and processed the return on September 23, 2026. The issue is that the replacement status is still stuck at: “Received / Processing” There is still no replacement part number, no replacement serial number, no carrier, no tracking number, and no shipped date. I understand that processing can take time, but the return has been in Western Digital’s possession since September 16, and their own system confirmed receipt and processing (only) on September 23. Has anyone else had a Western Digital RMA sit in “Received / Processing” this long? Is there a better escalation path than the normal support portal? I’m not trying to be unreasonable. I just need the warranty replacement completed, or at least a clear explanation of what is holding it up, because this delay is now affecting my business continuity and backup/data protection planning.

one of 10 reasons I dumped OS5 and reverted to OS3 long ago (and segregated the NAS units from the internet)

YEs. You need a Linux file reader program. WD OS5 disks are formatted as EXT4 (a linux protocol). Native windows will not read the disks. This presumes that your disk was a raid 1 (mirrored) and not stripped (default is mirrored). (REMINDER: Flood is “common mode failure” for a dual disk NAS unit. So is “Fire”. Always have an offsite backup) (And maybe don’t put electronics in a basement. ) (and yes, I had water in a basement as well - - -but the NAS units were in a house 120 miles away, about 600’ above sealevel)

Firmware: MJAOA5F0 Rotation rate: 7200RPM, Cache: 64MB S.M.A.R.T.: zero power on hours, now it’s 43hs, zero power cycles, now it’s 37, zero bad sector sand CRC errors. I think it’s very old open box (or reprogramed/f*cked/whatever) MaxDigitalData MD4000GSA6472DVR 4TB 7200RPM 64MB Cache SATA III, witch is originally is HGST. relabeled as WD purple. because the PCB pin and HDD itself look like new, no scratches or usage marks. What drives me crazy is that we are facing a new type of counterfeiting that uses genuine serial numbers. Have counterfeiters managed to access Western Digital’s database? Are they intercepting shipments to copy the serial numbers? Or is there some disaster we don’t know about? Anything is possible in this shi&&y f*cked AI era.

The 1.6TB issue is due to a 32-bit LBA limitation in the USB-SATA bridge. https://www.google.com/search?q=4TB%20-%202TiB%20in%20TiB 4TB - 2TiB = 1.64 tebibytes 32-bit LBA limits and reduced capacities: https://www.hddoracle.com/viewtopic.php?p=24696#p24696

VICTOIRE ! réponse du technicien ! "Pour résoudre ce type de conflit d’activation et forcer la réinitialisation de la détection réseau sans impact sur vos données, nous vous invitons à suivre la procédure ci-dessous. Cette manipulation ne supprime en aucun cas vos fichiers ou vos dossiers partagés. Accès direct via l’IP : Ouvrez votre navigateur internet habituel et saisissez directement l’adresse IP locale de votre appareil dans la barre d’adresse : http://192.X.X.X afin d’accéder directement au tableau de bord local du My Cloud Home. Effacer les paramètres de l’appareil : Une fois connecté sur cette interface, accédez à votre profil en haut à droite et appliquez la méthode décrite dans notre guide officiel : Effacer les paramètres de l’appareil sur My Cloud Home. Cliquez sur Effacer pour lancer le processus. Étapes pour effacer les paramètres de l’appareil sur un My Cloud Home ou ibi https://support-fr.wd.com/app/answers/detailweb/a_id/50462/initiator/user Redémarrage et réindexation : L’appareil va s’éteindre et redémarrer proprement pour réinitialiser sa configuration système (le commutateur réseau local et les identifiants locaux seront remis par défaut). Veuillez patienter le temps que le voyant se stabilise et que l’appareil redevienne pleinement disponible. Réactivation de l’accès local : Connectez-vous à nouveau à l’interface d’administration en utilisant à nouveau l’adresse IP locale ( 192.X.X.X ) dans votre navigateur. Activez de nouveau l’option d’accès au réseau

And now my other drive (10TB) is showing Bad and 2 red LEDs. Once again all diagnostics I performed are OK! Software Version 5.33.102.

Thanks, that helps. I think you’ve convinced me that the Pro is probably unnecessary for this setup. I’ll also give RAID 5 vs. RAID 6 some more thought based on how important the data is.

What you’re seeing is actually consistent with how the DX4000 handles Storage Spaces/RAID expansion rather than a normal filesystem migration. When you add a larger disk, the Sentinel has to update the array metadata and redistribute/recalculate parity across the existing members, but the usable capacity is constrained by the smallest participating disks, so adding a 14 TB disk to a set built around 4 TB members doesn’t immediately give you anything close to 14 TB of usable space. The fact that the first 14 TB migration completed and the reported capacity moved from 4 TB to 8 TB is a good indication that the controller/OS accepted the disk and successfully expanded the pool; the multi-day runtime is also not surprising because this is effectively a background parity/data redistribution operation with relatively weak DX4000-era hardware and firmware. I would not interrupt the migration or start another firmware operation while it is rebuilding, because the array metadata is being modified and a forced interruption is a much bigger risk than the slow progress. The “FAN FAILED” alert disappearing after a reboot also points more toward a stale sensor/health-monitoring state in the legacy Sentinel firmware than an actual fan failure. One important caveat: if the original objective is recovering an existing RAID-5 array that had the 0xD9 error, don’t treat this migration as a recovery method; rebuilding/expanding the array on those 14 TB disks can overwrite RAID metadata and make f

“Please select one item” error is most likely a UI workflow issue, not evidence that encryption cannot be modified. On OS 3, the Modify action operates on a selected encrypted volume, so if the volume/RAID entry itself is not selected in the Volume Encryption list, the frontend validation throws that message before it even attempts to change the encryption state. Once the RAID volume is explicitly selected, Modify → authenticate with the existing encryption password/key → enable Auto Mount → Apply should change the unlock behaviour. The fact that the volume requires the encryption password after every reboot simply indicates that its key material is not currently being used for automatic unlock at boot; it does not mean the RAID has to be recreated or encryption removed. Also, the distinction matters here: removing encryption and changing the mount policy are separate operations. If the goal is only to stop manually unlocking the volume after reboot, there is no reason to decrypt/rebuild the RAID at all; change the volume’s Auto Mount configuration instead.

I’d go with the Red Plus unless your NAS is going to be doing substantially more than you described. In a 4-bay box serving Plex, photo backups and a couple of simultaneous users, the NAS/network stack is usually the bottleneck long before the difference between the Plus and Pro matters; the Pro’s higher spindle speed and throughput become more relevant with sustained concurrent I/O, heavier RAID workloads, large sequential transfers or a much busier multi-user NAS. The trade-off is that the Pro’s 7200-RPM mechanics generally mean more vibration, acoustic noise and power/heat than the 5400-RPM-class Plus, and with four drives running continuously that is noticeable. The 5-year Pro warranty is useful, but I wouldn’t treat it as a performance justification by itself. For RAID, I’d also think about fault tolerance rather than benchmark numbers: RAID 5 gives you one-drive redundancy, while RAID 6 gives you two, which is much more relevant once you’re rebuilding multi-terabyte disks and exposing the array to another failure during that rebuild. On a 4-drive home array, RAID 6 costs you a lot of usable capacity, so RAID 5 with a good backup strategy is a reasonable choice if the data is replaceable; if the data is important enough that a second drive failure during rebuild would be unacceptable, RAID 6 is the safer architecture. In other words, the Pro is a better drive on paper, but for your stated workload you’re mostly paying for characteristics you probably won’t exploit, while