I tried to connect only 1 disk with a Sata2USB cable. The disk was mounted. So I run one of the backup scripts and it started working, but then, suddenly I got this:
- Code: Select all
...
mdi/Backup_Acer/D/Musica/MP3/Shineoma/Ventagli.MP3
mdi/Backup_Acer/D/Musica/MP3/Shineoma/Ventagli.doc
mdi/Backup_Acer/D/Musica/Registrazione/
mdi/Backup_Acer/D/Musica/Registrazione/Forever.bun
rrsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/share/1000/data1_1/mdi/Backup_Acer/D/Musica/Registrazione/Forever.bun": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(322) [receiver=3.0.9]
rsync: connection unexpectedly closed (69598 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
And the disk is unmounted.
- Code: Select all
e2fsck /dev/sdb1
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open /dev/sdb1
Possibly non-existent device?
The cronjob.log:
- Code: Select all
crond: USER root pid 9050 Rsync script started at : 08/03/2014 06:57:47 PM
crond: USER root pid 9050 USB share is available !
crond: USER root pid 9050 Rsync command successful !
crond: USER root pid 9050 Rsync script ended at : 08/03/2014 07:04:24 PM
Same story with the other disk (different file):
- Code: Select all
...
mdi/Backup_Acer/C/Desktop/Documenti/Club Medusa/Club.LOG
mdi/Backup_Acer/C/Desktop/Documenti/Club Medusa/Club.cfg
mdi/Backup_Acer/C/Desktop/Documenti/Club Medusa/Club.mdb
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: write failed on "/share/1000/data2_1/mdi/Backup_Acer/C/Desktop/Documenti/Club Medusa/Club.mdb": Read-only file system (30)
rsync: connection unexpectedly closed (11469 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
So, now I suspect that the disk has something strange, but why does it say that I have a ro filesystem, while it was actually writing since a while before?...
Do you think I should re-format?.
It seems that the disk goes in stand-by. Is there a way to check if the disk is set to go in standby on its own? Strange that it does while it is being used.... :tapfoot
Or maybe I can try formatting with MBR?... do you think I shall try?
Thank you,
MDI