The problem seems to be DHCP and the dashboard not allowing the 169.254.9.233 that it defaults to.
If i could get it to limp to the dashboard, I could reinstall the firmware, or manipulate it from a browser.
If I could find how to make it a static address, I could do that via SSH and Winscp
I am not sure I can maintain a SSH session on a destructive script operation.
Again, Twonky server and 169.254.9.233:9000 fully cooperate, as well as SSH to 169.254.9.233.
The MBL cloud setup will see the drive at 169.254.9.233 and allow me to setup a cloud account, but never sends the email.
The WD Link don’t see the drive.
The Win7 machine doesn’t see the drive
A Win XP sees the drive and server at 169.254.9.233, allow invoking Twonky, rejects invoking dashboard.
I am sending this from the browser inside the rescue OS, and preparing to try to debrick yet again.
All partitions have been deleted prior to debrick.
Debrick, so far, in the last 3 tries has errored out prior to finishing. I will try to capture the errors this time
All I want to do is reinstall the OS and WD routines to restore it to a new condition, as if I had just implemented a new drive.
The last 2 times, I used Gparted to delete the partitons. They were sucessfully created by the debrick script.
The machine has to be rebooted every time the script fails on a mb0 error.
Trying agian…