Wd my cloud 2TB mess - ssh ok, dashboard gone

playing with apt-get wasn’t really a good idea :frowning:
apt-get autoremove ended up messing up everything… now I can’t access the dashboard.

I’ve been trying to install the firmware via ssh (I had to manually edit the lost .sh files as read here ) but there must be something not working; this is the output:

-bash-4.2# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-040500-315-20170331.deb

shutdown -r now does’nt work, the firmware updating wasn’t successful…
what should the correct output be?

any suggestions? :blush:

this is lsblk command output:


sda 8:0 0 1.8T 0 disk
|-sda1 8:1 0 1.9G 0 part
| '-md1 9:1 0 1.9G 0 raid1 /
|-sda2 8:2 0 1.9G 0 part
| '-md1 9:1 0 1.9G 0 raid1 /
|-sda3 8:3 0 489M 0 part [SWAP]
|-sda4 8:4 0 1.8T 0 part /DataVolume
|-sda5 8:5 0 95M 0 part
|-sda6 8:6 0 96M 0 part
|-sda7 8:7 0 1M 0 part
`-sda8 8:8 0 2M 0 part

what is the corrupted partition? sda1? sda2?

would a dd if=rootfs.img of=/dev/sda1 / sda2 be possible via ssh?

I haven’t try that.

Let’s see if any of the users can share some information about it.

perhaps it wont be possible as sda1 and sda2 are mounted.
anyway, ssh or usb or opening the unit, given the fact that fiddling with apt-get autoremove shoudn’t broke the partition table, do you thing flashing only sda1 and sda2 should be enough to bring back mycloud dashboard to life?

dd if=rootfs.img of=/dev/sda1 and sda2 didn’t help, still solid white light that restart after 40seconds or so.

does it make any sense trying to do it also for kernel.img and config.img?

is user data sda4 safe this way?

just in case someone would care, dd if=rootfs.img of=/dev/md0 did the trick.
back to life and no data loss.