I was unaware of that facility but will look next time it happens thanks.RaTTuS wrote:does dmesg report anythign useful when it has gone awol ?
Smartmontools most often doesn't work on USB hard disks.fredoll wrote:you could install smartmon tools
Code: Select all
sudo apt-get update sudo apt-get install smartmontools
Following a reboot I have use the Pi for a while now without problem, however last night it transferred a large amount of data from HDD1 to HDD2 with cron jobs.RaTTuS wrote:sudo apt-get update && sudo apt-get upgrade
sudo apt-get install pastebinit
dmesg | pastbinit
it's possible you have a failing HD
or the connection may drop to it for some reason - you may be able to get away with a re-mount of the drive
is that how you reference it in your fstab? If so you might find it helps to reference it by it's uuid insteadmakem2 wrote:Still getting the 'losing' a drive. Very annoying as it is occurring quite often and spoiling backups.
I notice on boot-up a 'failed' in red relating to a drive:
special device /dev/sda2 does not exist
I have never noticed this before and wonder if it is related to the drive which keeps going AWOL.
Ah, that's something I also learned not all that long ago (relatively speaking). When mounting drives its recommended to use their uuid as the sd## can change when you have multiple drives plugged in. It's possible that this is the root cause of your troubles and change fstab to mount by uuid could fix your problems. Even if it doesn't fix it, it's still a better way of doing thingsmakem2 wrote:EDIT: ls -l /dev/disk/by-uuid/ shows only sdb1 and sda1 but both drives show in file manager. It seems I have gained an sdb1 and not a sda2 as it should be.