The main issue as I see it is getting to the dashboard Once you login to the dashboard the rest should be fine, you probably need to turn off MBLD put the second disk (Disk B) as well and turn on the device and perform a Factory Reset from the dashboard. I did that for both Disks (A and B) and this time when I connected disk A and saw the yellow led again (I tought I am stuck in the same loop again), I tried a ping from a network computer to mybookliveduo hostname and I saw a response so I managed to login to the dashboard! I also read in this thread that when running the same debricking script twice with a reboot between each try, some of the errors disappear
#Systemrescuecd shutdown software
In my case, I managed to take out the data I had on the HDD with the software R-Linux so I could try Guide 2 which talking about installing MBLD OS on a new unalloacted disk
#Systemrescuecd shutdown download
So I went to older version repository of SystemRescue CD and downloaded systemrescuecd-x86-3.2.0.iso file which was release somewhere around (here is a link to download this version) It made me think that maybe this old thread (I am talking about 2013 when it was created) using tools in older versions than the version I’ve used when I was downloading the same tools (I am talking specifically about SystemRescue CD) I did the debrick process with SystemRescue CD and also with different versions of Ubuntu (12.10, 16, 18) and I noticied that with each operating system that I try, the results are a bit different and errors that I get from the script are a bit different. What was even stranger is that the md partitions that were created (not really sure yet what exactly is md partition but I understood it is something related to RAID) were md126 and m127 and not md0 and md2 I noticed that I was receiving some errors in the debrick script output.
No “ping” reply from the MBLD device whatsoever. In my situation after 2 minutes of yellow led, device was rebooting by itself, then I saw the blue led for couple of seconds and then the yellow led again until the next self reboot Actually, this is also how I got here…Īfter 2 days of struggling myself with debricking my device I finally managed to do it.Įverything I tried didn’t help me to pass the yellow led which I was stuck on. The year is almost 2020 and I see people are still struggling with bricked MBLD. I type Y for everything it comes up and then says all done! after i get these partitions im using the systemrescuecd got the debrick script on my flashdrive and the newest 2015 firmware i tried the link of the 2012 one here as well. not even my router gets an ip for the duo. i dont know what software to run i downloaded the “mbl_duo_windows_setup” but tries to set up and cant find it. anything i do i still get the yellow light of death haha. i followed guide 2 and still no go i typed the commands. didnt know like most of you guys the operating system is in the drive.
#Systemrescuecd shutdown how to
Hello everyone, so i have been going at debricking mybook live duo for 2 days now and i cant get it to boot, i recently bought 2 used duos a 6tb and a 8tb both working great, the seller showed me how to set it up etc, but he didnt get a chance to erase them so i zeroed it out for him and now im here. So if it is possible, PLEASE refer me to some one who can help in this matter. and i’m very afraid that i might make something wrong and wipe the whole data.Īll my projects and years of study are in that disks.!ĭoes this operation (Debricking) - can be done REMOTELY by any expert?Īlready i lost a whole week trying to figure out how to recover my data, but no clue. but i couldn’t understand how should i do. I’m not an expert in Linux and commands, thou i read ALL the guides and comments above, and in every where else. I can see them put i can not open or explore them. not working eitherĮven with direct SATA - SATA cable is not working. Tried to connect via SATA - USB cable, and tried to access them through linux reader. I have MBLD 6TB (2 * 3TB) that is connected to network all the timeīut suddenly can not find in network any more. At first, sorry for my English, its not my native language
0 kommentar(er)
