So I ran CHMOD -R 777 * as root from / yolo

Legacy Products My Book Live
1

Alright, here’s the story behind my idiocy: bottom line is that I was trying to get root dir accessible from platform UIs that are seen as ‘guests’ instead of /Public/ so I decided to SSH into my MBL (3tb) and cd / followed by CHMOD -R 777 *

Now pretty much everything is defunct… fpkmgr is installed but limited usability and is throwing the error “sudo: must be setuid root” and SSH is down and the dashboard wont allow me to initiate a FW upgrade or access any of the menus or display any information about the drive.

Was able to get a small portion of the terminal log after chmod -r 777 * was ran.

paste2.org/VwXWPmcX

lol

do I have any options here where I can retain my data?

2

bump

3

Read up to step two… Might help…

http://community.wd.com/t5/My-Book-Live/GUIDE-How-to-unbrick-a-totally-dead-MBL/td-p/435724

4

no

5

bump

6

bump

7

**bleep** the police

8

Based on my experience, screwing with permissions on a global scale = trouble. I mean not only in UNIXes, but also Windows…

The only thing you’ll be able to do is (in a nutshell):

Hope that helps …

And before you ask… I’ve did my own share of research, and no, there is no other solution than a fresh format. 

You have to crack it open.

*ps: please note that I’ve never experienced this thing in my MBL, but I did the same mistake twice, back then in my Red Hat days, and in my first Win8 x64 install.

9

thanks for a fact based and informative reply man… really appreciate it