I looked at the S.M.A.R.T. data for my SSD and found some bad statistics:
Read Error Rate: 147
Reallocated Sector Count 544768 sectors
Reported Uncorrectable Errors: 122 sectors
Reallocation Count: 133 sectors
Uncorrectable Sector Count: 10 sectors
UDMA CRC Error Rate: 1
So my s3ql repository is on an external hard drive that doesn't have any
SMART data available in Lubuntu's Disks program. As far as I know it
doesn't have any problems. Is there some way I can just mount what I have
without trying to run fsck first so I can recover my data? When my computer
crashed I was using attic to create an archive from my s3ql mount (because
I was thinking of switching to attic), so I don't know where the s3ql
writes came from, but maybe attic had something to do with that.
I've attached all the logs that I found in ~/.s3ql, hopefully they provide
more insight.
On Tuesday, September 1, 2015 at 10:05:08 PM UTC-7, Donny Ward wrote:
>
> Here's my outputs:
>
> donny@donny-lubuntu:~$ cat
> ~/.s3ql/local\:\=2F\=2F\=2Fmedia\=2Fdonny\=2FWDBLACK\=2Fs3ql
> local:=2F=2F=2Fmedia=2Fdonny=2FWDBLACK=2Fs3ql-cache/
> local:=2F=2F=2Fmedia=2Fdonny=2FWDBLACK=2Fs3ql.db
> local:=2F=2F=2Fmedia=2Fdonny=2FWDBLACK=2Fs3ql.params
> donny@donny-lubuntu:~$ cat
> ~/.s3ql/local\:\=2F\=2F\=2Fmedia\=2Fdonny\=2FWDBLACK\=2Fs3ql-cache/* >
> /dev/null
> cat:
> /home/donny/.s3ql/local:=2F=2F=2Fmedia=2Fdonny=2FWDBLACK=2Fs3ql-cache/2967-0:
> Input/output error
>
>
> Then I ran:
> donny@donny-lubuntu:~$ dmesg | tail
> [10542.119291] ata2.00: error: { UNC }
> [10542.135701] ata2.00: configured for UDMA/100
> [10542.151568] ata2.01: configured for UDMA/100
> [10542.151593] sd 1:0:0:0: [sda] FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [10542.151600] sd 1:0:0:0: [sda] Sense Key : Medium Error [current]
> [descriptor]
> [10542.151606] sd 1:0:0:0: [sda] Add. Sense: Unrecovered read error - auto
> reallocate failed
> [10542.151611] sd 1:0:0:0: [sda] CDB:
> [10542.151614] Read(10): 28 00 2c 0c 10 10 00 00 08 00
> [10542.151630] blk_update_request: I/O error, dev sda, sector 738988048
> [10542.151666] ata2: EH complete
>
> So I guess my ssd is screwed. I've never dealt with any filesystem
> problems like this before. What should I do to recover my data?
>
> On Tuesday, September 1, 2015 at 6:33:34 PM UTC-7, Nikolaus Rath wrote:
>>
>> On Sep 01 2015, Donny Ward <[email protected]> wrote:
>> > Hello,
>> >
>> > I have an external hard drive (exFAT) with an s3ql filesystem stored on
>> it
>> > with about 600GB. I plugged in this external hard drive and mounted its
>> > s3ql filesystem in order to copy everything off the disk. I left my
>> > computer on overnight and when I woke up I found out that my computer
>> died
>> > (well, it just froze, I had to power it off and on). Now I'm trying to
>> > mount the s3ql filesystem again and it says I need to run fsck.s3ql
>> first.
>> > So I did that.
>> >
>> > There were several "Committing block 0 of inode 2967 to backend" type
>> > messages.
>>
>> In that case you must have modified files in the S3QL file system, and
>> not just copied files from it.
>>
>> > Eventually fsck died though. I would restart fsck and it would
>> > commit more inodes before dying again. Now fsck dies immediately, and
>> here
>> > is the output.
>> >
>> > donny@donny-lubuntu:~$ fsck.s3ql local:///media/donny/WDBLACK/s3ql/
>> > Enter file system encryption passphrase:
>> > Starting fsck of local:///media/donny/WDBLACK/s3ql
>> > Using cached metadata.
>> > Remote metadata is outdated.
>> > Checking DB integrity...
>> > Creating temporary extra indices...
>> > Checking lost+found...
>> > Checking cached objects...
>> > Committing block 0 of inode 2967 to backend
>> > Dropping temporary indices...
>> > Uncaught top-level exception:
>> > Traceback (most recent call last):
>> > File "/usr/bin/fsck.s3ql", line 9, in <module>
>> > load_entry_point('s3ql==2.13', 'console_scripts', 'fsck.s3ql')()
>> > File "/usr/lib/s3ql/s3ql/fsck.py", line 1272, in main
>> > fsck.check()
>> > File "/usr/lib/s3ql/s3ql/fsck.py", line 81, in check
>> > self.check_cache()
>> > File "/usr/lib/s3ql/s3ql/fsck.py", line 179, in check_cache
>> > hash_ = sha256_fh(fh)
>> > File "/usr/lib/s3ql/s3ql/common.py", line 220, in sha256_fh
>> > buf = fh.read(BUFSIZE)
>> > OSError: [Errno 5] Input/output error
>> > donny@donny-lubuntu:~$
>> >
>> > I just want to be able to mount the filesystem again so I can copy all
>> the
>> > data off of it. What can I do?
>>
>> Check your kernel message logs, and try to run
>>
>> $ ls -l ~/.s3ql/local*donny*s3ql*-cache/
>> $ cat ~/.s3ql/local*donny*s3ql*-cache/* > /dev/null
>>
>>
>> It looks as if the file system holding your cache directory is broken.
>>
>> Best,
>> -Nikolaus
>>
>> --
>> GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
>> Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
>>
>> »Time flies like an arrow, fruit flies like a Banana.«
>>
>
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
