Hello dear community,
I’ve been a very satisfied owner of a MyBook Live since some days now.
However, being so enthusiastic about it, I gave it to a good friend of mine to try it out, as he was also interested in getting one. While both of us are into Linux, my friend suggested to install Finch (the console version of the Pidgin messenger) on the MyBook as an “allways-on-chat-client”. Well, apparently everything went well with that - until I plugged the MyBook in after geting it back today.
Since then I keep getting the message “Data volume failed to mount” and a red status LED. The Webinterface keeps saying 0GB/0TB used.
As the SSH daemon is still up and running, I was able to log into the MyBook and check out how much damage was done.
Here are some things I was able to discover:
Output of: /etc/init.d/mountDataVolume.sh
>>>> mount data volume...mount: you must specify the filesystem type
swapon: cannot stat /dev/sda3: No such file or directory
mount: none already mounted or /sys/kernel/security busy
mount: according to mtab, none is already mounted on /sys/kernel/security
Kernel API version: 2
settrustees API version: 2
Pass 1: Checking for parse errors
Could not find device /dev/sda4
Parse error /etc/trustees.conf:0
failed.
Output of: mount
/dev/md1 on / type ext3 (rw,noatime)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=50M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=50M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,size=50M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
Content of: /etc/fstab
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /tmp tmpfs rw,size=50M 0 0
/dev/md1 / ext3 defaults,noatime 0 0
Content of: /var/log.hdd/kern.log
Feb 9 15:02:29 localhost kernel: drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Feb 9 15:02:29 localhost kernel: md: Waiting for all devices to be available before autodetect
Feb 9 15:02:29 localhost kernel: md: If you don't use raid, use raid=noautodetect
Feb 9 15:02:29 localhost kernel: md: Autodetecting RAID arrays.
Feb 9 15:02:29 localhost kernel: md: Scanned 2 and added 2 devices.
Feb 9 15:02:29 localhost kernel: md: autorun ...
Feb 9 15:02:29 localhost kernel: md: considering sda2 ...
Feb 9 15:02:29 localhost kernel: md: adding sda2 ...
Feb 9 15:02:29 localhost kernel: md: adding sda1 ...
Feb 9 15:02:29 localhost kernel: md: created md1
Feb 9 15:02:29 localhost kernel: md: bind<sda1>
Feb 9 15:02:29 localhost kernel: md: bind<sda2>
Feb 9 15:02:29 localhost kernel: md: running: <sda2><sda1>
Feb 9 15:02:29 localhost kernel: md1: WARNING: sda2 appears to be on the same physical disk as sda1.
Feb 9 15:02:29 localhost kernel: True protection against single-disk failure might be compromised.
Feb 9 15:02:29 localhost kernel: raid1: raid set md1 active with 2 out of 2 mirrors
Feb 9 15:02:29 localhost kernel: md1: detected capacity change from 0 to 2047803392
Feb 9 15:02:29 localhost kernel: md: ... autorun DONE.
Feb 9 15:02:29 localhost kernel: md1: unknown partition table
Feb 9 15:02:29 localhost kernel: kjournald starting. Commit interval 5 seconds
Feb 9 15:02:29 localhost kernel: EXT3 FS on md1, internal journal
Feb 9 15:02:29 localhost kernel: EXT3-fs: mounted filesystem with writeback data mode.
Feb 9 15:02:29 localhost kernel: VFS: Mounted root (ext3 filesystem) on device 9:1.
Feb 9 15:02:29 localhost kernel: Freeing unused kernel memory: 384k init
Feb 9 15:02:29 localhost kernel: Enable EMAC EMI Fix
Feb 9 15:02:29 localhost kernel: eth0: link is up, 100 FDX, pause enabled
Feb 9 15:02:36 localhost kernel: svc: failed to register lockdv1 RPC service (errno 97).
Feb 9 15:02:39 localhost kernel: eth0: no IPv6 routers present
Feb 9 15:06:00 localhost kernel: nfsd: last server has exited, flushing export cache
I’m not really sure if the /dev/md1 really belongs here? I think the behaviour of this device is configured in /etc/mdadm which belongs to some kind of softraid management tool. As the MyBook just contains one HDD, this doesn’t really make sense to me at all.
Could somebody give me a helping hand on this?
Even though it is obviously my own fault as I was the one who gave it away in the first place.
With kind regards
Alexander
