One of the things that stops the MyCloud sleeping is external network accesses. So WDSleepFix might disable Cloud Access (I don’t know, since I don’t have a Gen2 MyCloud, and haven’t used any of the ‘cracks’, or app installs). Disabling Cloud Access stops the internal indexing and thumbnailing process. These processes are required for the Dashboard ‘pie chart’ display, to allow the different data types to be identified. Due to the known security vulnerabilities, I currently have Cloud Access disabled, and this causes the pie chart to indicate capacity only in blue: data type ‘Other’.
Twonky: have you enabled the Media Sharing on the shares containing media? Have you turned on the Twonky Media Server? Have you accessed the Twonky UI (port 9000) to see what directories it is searching in for media?
What to do next? I’d do a data backup (which you should have anyway), and then do a quick factory restore, install latest firmware, set up the device again, and then load the data from the backup.
Because i usually load file via Internet so Cloud Access will be enabled for me.
Now, DLNA has enable - Twonky working with port 9000, and sharing some folder.
I have sams idea with you but if i use Quick Factory Restore, will FW be reset all of apps, after that reset and re-fresh FW of MyCloud with update FW.
I mean: is MyCloud work again normally with 2.30.165?
If you changed your firmware yet those apps are still present that indicates changing firmware IS NOT uninstalling/deleting or otherwise removing those apps. Those apps could still be interfering with the My Cloud.
As explained previously doing any sort of a system restore or reset may not remove/delete or otherwise remove any unofficial apps.
As explained previously you may have to resort to wiping out all the partitions on the My Cloud hard drive, rebuilding them, reformatting them, then installing the firmware. Again, do an internet search to learn how to use SSH and Telnet at least in general terms.
I do not have a second gen v2.x My Cloud, I only have a first gen v4.x My Cloud. My understanding of how to modify v2.x firmware is limited.
The following assumes some knowledge of how to issue SSH commands to find the My Cloud hard drive name. Then using that drive name to run the Partition utility (Parted) to delete all existing Partitions. Then create new partitions, using step 5 from Fox_Exe’s My Cloud v2 unbrick procedure. Take care to delete ONLY the My Cloud partition. DO NOT blame me if you issue the wrong command and delete all your data on your computer. DO NOT blame me if these are the wrong commands or they are in the wrong order. User assumes ALL RISK performing the following commands. BACKUP ALL user data from the My Cloud before removing the partition!
Use fdisk -l (or parted -l) to see what name have for your My Cloud HDD.
For example: /dev/sdb. (Replace it to your My Cloud HDD name!)
Run parted utility: parted /dev/sdb
Type “print” for see what partitions exist on disk
Remove all: Type “remove 1” (where 1 - number of partition)
Note: If you do not know how to issue SSH commands or how to backup files (or copy files) from the My Cloud using SSH (FTP or Telnet) PERFORM an internet search to LEARN how to do so.
I’m on the way to back up files out of MyCloud and after that do a Quick Factory Restore for MyCloud.
Maybe first, i’ll try Quick Factory Restore and update FW to repair MyCloud. If not, i’ll try your guide later.
(because, your guide are samed with @Fox_exe intructions that i do it again and again many time )
Can i ask you some questions:
Are these command that you guide me will do base on Windows through SSH connect?
Are your guide not need to remove HDD from WDMC for recovery?
Are table of partitions of MyCloud Gen1 same Gen 2? (because i refer other thread of WD Community has these command which apply for Gen1, so i have ask you to make sure that also apply for MyCloud Gen2).
Is there reference in which command of parted utility from step 1 to 6.1: command “fdisk -l”
I mean: run command: fdisk -l => /dev/sdb (for example)
So i will use “/dev/sdb” for all step below?
or to Step 6, i must change to /dev/sda and do it to the end?
5. I don’t understand your mean:
=> Will i type “1” as you guide or… which number of partition?
6. As your guide, am i repaired USB stick has 4 file as @Fox_exe instructions?
I think your guide still need USB stick, right?
Hope so, your guides are last one that i can recover MyCloud and make it work again!
Thank you so much, @Bennor.
Philip.
I cannot stress this enough. If you don’t know what you are doing and don’t know how to use SSH or do not understand how disks/partitions are laid out in Linux, you should avoid using SSH until you spend some time learning how to use SSH and learning about Linux. Please perform an internet search on SSH commands, search this subforum as there is a LOT of past discussion on using SSH when unbricking. Many of your questions have been asked by others in past discussions. Also perform a internet search to learn about Linux file/directory structure.
SSH is SSH, you typically and generally issue the same command(s) whether you are using Windows, Mac or Linux.
The partition table I posted was from Fox_Exe’s Gen 2, while the commands came from his Gen 1 unbrick file. The commands are typically the same even though the partition sizes may be different between the two versions.
I understand the desire to shortcut the Linux learning process to get one’s My Cloud drive back running after improperly installing unsupported modules or apps. But you have to learn how to use various Linux commands in order to avoid problems while unbricking and that involves reading and searching on the internet. The answers are all there at your fingertips.
I do NOT have a v2.x My Cloud so I can only go by what Fox_Exe and others have posted in the various unbricking threads including using a USB drive to unbrick the v2.x My Cloud.
Thank you so much, @Bennor. You’re very kind to support me!
I’ve understand what you say and i much learn more about Linux to understand and fix MyCloud.
I also so confuse and hopeless for waiting reformat, before situation is: loop rebooting when Quick Factory Restore.
I think in this case: Blue Led blinking will come when have some trouble with FW. @Fox_exe instructions is tried or re-arranged partitions to get FW back so far by use Safe boot to recover FW. => he has a good skill when he recognized that trouble came!
I think that: maybe WD has a “good” FW of MyCloud to recover device when brick, then try some of FW that WD release - first release & 2.10.310 FW can be.
Once again, thank @Bennor so much when you are tried to help me.
Philip.
For the 1st gen My Cloud, yes the firmware is on the hard drive. I assume the same is true for 2nd bay My Cloud units.
My understanding with how a Quick Restore and Full Restore works is they don’t actually erase the whole whole hard drive. Instead they both just erase the user data on the one partition that holds the user data.
That’s why I suggested earlier that you erase/delete all partitions on the hard drive and rebuild it. That is the only way to ensure no remains of the firmware or mods/apps remain within the firmware.
You can do a search through this subforum to find various discussions on the way the firmware works on the 2nd gen My Cloud units. Particularly how changes a user makes may not be retained when one reboots the 2nd gen My Cloud.
)
