What did I do wrong and can it be fixed?
History: a hacked WD Mybook World Edition 500GB.
Several partitions regualarly went read-only. Fixed md3 and md4 while the system was running following these steps:
cd /var tar cpsf /shares/internal/var.tar * /etc/init.d/network_servers.sh stop umount /dev/md3 mkfs.ext3 -m 0 /dev/md3 mount /dev/md3 /var cd /var tar xf /shares/internal/var.tar /etc/init.d/network_servers.sh start
Then I fucked up the permissions of busybox, so I could not become root anymore. : (
So I decided to take the disk out of the case and hook it up to an ubuntu system.
Was able to:
chown root:root busybox
Now busybox looks like:
root@Ubeee:/mnt/sdc1/bin# ls -al busybox -rwsr-sr-x 1 root root 496792 2007-06-30 16:34 busybox
While I was at it I thought of fixing the read-only issue on the first partition: md1
From ubuntu I tared the content of the whole partition and got these messages:
robbie@Ubeee:/mnt/USB$ sudo tar cpsf ../BULK/sdc1.tar * tar: dev/log: socket ignored tar: tmp/screens/S-root/2271.pts-0.nasje: socket ignored tar: tmp/screens/S-root/2981.pts-1.nasje: socket ignored tar: tmp/lighttpd.fcgi.socket-0: socket ignored tar: tmp/php.socket-3: socket ignored tar: tmp/php.socket-1: socket ignored tar: tmp/php.socket-0: socket ignored tar: tmp/php.socket-2: socket ignored
Ignored the messages and went ahead and formated the partition
After tarring the content back I assembled the disk back.
No blue button and no busybox on the line…
Is there any hope of getting the system back on without reinstalling the backup images from the rescue procedures? I’d like to see the system back with all packaged still installed. Is this possible? And else what should I do to get Mybook back alive?