Files randomly deleted

[Belazor]

Hey all,

I'm having a weird problem that I'm hoping you guys will be able to shed some light on: My files are randomly vanishing. Not put in the Greyhole Recycle Bin, just poof, gone. Over 100 GB of data has been lost this way since I started using Amahi.

I download via uTorrent directly to the server, but overnight (night in this instance being a very loose term as my sleeping schedule is whacked) random files from random locations vanish, never to be seen again, only their empty folders remaining.

In the last 3 hours ago, while I was napping, I lost over 36 GB on a download I was working on. So much for watching another episode of Dexter with my dinner =/
I also lost 300 MB worth of music.
When I was copying 2 TB of data over from my local drives when I got started with Amahi, about 70 GB worth of movies and other TV shows vanished into thin air. Some of it was found in the Greyhole Recycle Bin, but most was not.

I have since upgraded to the latest version of Greyhole, from 0.9.6 or whatever was supplied with Amahi, I'm hoping that will fix the problems.

I'm posting this mainly for a few reasons:
1. Has anyone else ran into this issue and if so, was it ever solved?
2. Are there any logs or something I can check to investigate what happened?


EDIT: from greyhole.log:

Code: Select all

Nov 11 18:33:53 4 check_pool: PHP Warning [2]: file_put_contents(/var/hda/files/drives/drive1/gh/.gh_graveyard_backup/Files/Downloads/Dexter.S05.1080p.BluRay.x264-FLHD/Dexter.S05E05.PROPER.1080p.BluRay.x264-FLHD.mkv): failed to open stream: No such file or directory in /usr/bin/greyhole on line 2326

this would match the time the files vanished.

Code: Select all

[root@localhost ~]# cd /var/hda/files/drives/drive1/ [root@localhost drive1]# ls -l ls: reading directory .: Input/output error total 0

From greyhole stats we have this:

Code: Select all

/var/hda/files/drives/drive1/gh: Offline

If it matters, that drive is a USB drive.

[radioz]

ls: reading directory .: Input/output error

That doesn't look good. It could be a drive problem. Have you checked the SMART data on your drive(s)?
That might tell you if there are low-level hardware problems with the drive in question.

Take a look in /var/log/messages* for error messages.

Is the USB drive solid-state or a spinning disk?

[Belazor]

The S.M.A.R.T. data looks fine, I read up on it and I can see that higher = better, and the error rates are still in 100.

It's a platter drive, not an SSD.

I found the problem in the messages file though:

Code: Select all

Nov 11 18:33:12 localhost kernel: [355646.360886] usb 2-5: USB disconnect, address 2 Nov 11 18:33:23 localhost kernel: [355657.024095] sd 7:0:0:0: Device offlined - not ready after error recovery Nov 11 18:33:23 localhost kernel: [355657.024129] sd 7:0:0:0: [sdb] Unhandled error code Nov 11 18:33:23 localhost kernel: [355657.024133] sd 7:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Nov 11 18:33:23 localhost kernel: [355657.024139] sd 7:0:0:0: [sdb] CDB: Read(10): 28 00 4c 72 c4 37 00 00 20 00 Nov 11 18:33:23 localhost kernel: [355657.024153] end_request: I/O error, dev sdb, sector 1282589751 Nov 11 18:33:23 localhost kernel: [355657.024251] end_request: I/O error, dev sdb, sector 973428519 Nov 11 18:33:23 localhost kernel: [355657.025361] Aborting journal on device sdb1-8. Nov 11 18:33:23 localhost smbd_greyhole: [2011/11/11 18:33:23.138851, 0] smbd/reply.c:3517(send_file_readX) Nov 11 18:33:23 localhost kernel: [355657.033062] JBD2: I/O error detected when updating journal superblock for sdb1-8. Nov 11 18:33:23 localhost kernel: [355657.033174] journal commit I/O error Nov 11 18:33:23 localhost smbd_greyhole: send_file_readX: sendfile failed for file Downloads/Dexter.S05.1080p.BluRay.x264-FLHD/Dexter.S05E11.1080p.BluRay.x264 -TENEIGHTY.mkv.!ut (Input/output error). Terminating Nov 11 18:33:23 localhost kernel: [355657.062840] EXT4-fs error (device sdb1): ext4_journal_start_sb: Detected aborted journal Nov 11 18:33:23 localhost kernel: [355657.062954] EXT4-fs (sdb1): Remounting filesystem read-only Nov 11 18:33:23 localhost kernel: [355657.257051] usb 2-5: new high speed USB device using ehci_hcd and address 3 Nov 11 18:33:23 localhost kernel: [355657.374410] usb 2-5: New USB device found, idVendor=1bcf, idProduct=0c31 Nov 11 18:33:23 localhost kernel: [355657.374417] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 11 18:33:23 localhost kernel: [355657.374421] usb 2-5: Product: USB to Serial-ATA bridge Nov 11 18:33:23 localhost kernel: [355657.374425] usb 2-5: Manufacturer: Sunplus Innovation Technology Nov 11 18:33:23 localhost kernel: [355657.374429] usb 2-5: SerialNumber: FAFFFFF0FDF13FF1CF605439 Nov 11 18:33:23 localhost kernel: [355657.376760] scsi8 : usb-storage 2-5:1.0 Nov 11 18:33:24 localhost kernel: [355658.387829] scsi 8:0:0:0: Direct-Access SAMSUNG HD103UJ 0200 PQ: 0 ANSI: 4 Nov 11 18:33:24 localhost kernel: [355658.390575] sd 8:0:0:0: Attached scsi generic sg1 type 0 Nov 11 18:33:24 localhost kernel: [355658.391917] sd 8:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) Nov 11 18:33:24 localhost kernel: [355658.398171] sd 8:0:0:0: [sdc] Write Protect is off Nov 11 18:33:24 localhost kernel: [355658.398181] sd 8:0:0:0: [sdc] Assuming drive cache: write through Nov 11 18:33:24 localhost kernel: [355658.406185] sd 8:0:0:0: [sdc] Assuming drive cache: write through Nov 11 18:33:24 localhost kernel: [355658.406272] sdc: sdc1 Nov 11 18:33:24 localhost kernel: [355658.432171] sd 8:0:0:0: [sdc] Assuming drive cache: write through Nov 11 18:33:24 localhost kernel: [355658.432255] sd 8:0:0:0: [sdc] Attached SCS I disk Nov 11 18:33:31 localhost kernel: [355665.619264] EXT4-fs error (device sdb1): ext4_find_entry: inode #57933825: (comm greyhole) reading directory lblock 0

Then the last line is simply repeated with different inode numbers. Would you happen to know what could be the cause for the USB Disconnect?

I suppose I could just make it an internal drive for the time being, even though it does kinda limit my maximum storage capacity...

In either case I managed to hook the drive up to my desktop and extract the files, so I don't think I lost any data