On Jun 24, 2014, at 11:53 PM, Mike Hartman m...@hartmanipulation.com wrote:
Does this version's btrfs-image allow you to make an image of the file
system?
Nope, same errors and no output.
https://btrfs.wiki.kernel.org/index.php/Restore
Your superblocks are good according to btrfs
I don't know all states of this file system, and copies you have. Right now
the earliest copy is obviously broken, and the latest copy is probably more
broken because at the least its csum tree has been blown away meaning there's
no checksums to confirm whether any data extracted/copied
On Jun 25, 2014, at 1:32 PM, Mike Hartman m...@hartmanipulation.com wrote:
I don't know all states of this file system, and copies you have. Right now
the earliest copy is obviously broken, and the latest copy is probably more
broken because at the least its csum tree has been blown away
Chris Murphy posted on Mon, 23 Jun 2014 23:19:37 -0600 as excerpted:
I zeroed out the drive and ran every smartctl test on it I could find
and it never threw any more errors.
Zeroing SSDs isn't a good way to do it. Use ATA Secure Erase instead.
The drive is overprovisioned, so there are
On Jun 23, 2014, at 11:39 PM, Mike Hartman m...@hartmanipulation.com wrote:
https://github.com/kdave/btrfs-progs.git integration-20140619
Thanks. I pulled that version and retried everything in my original
transcript, including the btrfs check --init-csum-tree
--init-extent-tree. Results
On Jun 23, 2014, at 11:49 PM, Mike Hartman m...@hartmanipulation.com wrote:
I zeroed out the drive and ran every smartctl test on it I could find
and it never threw any more errors.
Zeroing SSDs isn't a good way to do it. Use ATA Secure Erase instead. The
drive is overprovisioned, so
Does this version's btrfs-image allow you to make an image of the file system?
Nope, same errors and no output.
https://btrfs.wiki.kernel.org/index.php/Restore
Your superblocks are good according to btrfs rescue super-recover. And
various tree roots are found by btrfs-find-root including a
On Jun 23, 2014, at 4:18 PM, Mike Hartman m...@hartmanipulation.com wrote:
Can anyone offer any suggestions? Is this data really unrecoverable? I
have no idea what could have gone so severely wrong.
btrfs check --repair /media/mint/usb_data/sda6_check.img
btrfs check --repair --init-csum-tree
On 06/24/2014 09:17 AM, Chris Murphy wrote:
On Jun 23, 2014, at 4:18 PM, Mike Hartman m...@hartmanipulation.com wrote:
Can anyone offer any suggestions? Is this data really unrecoverable? I
have no idea what could have gone so severely wrong.
btrfs check --repair
I have a dd image, but not a btrfs-image. I ran the btrfs-image
command, but it threw the same errors as everything else and generated
a 0 byte file.
I agree that it SOUNDS like some kind of media failure, but if so it
seems odd to me that I was able to dd the entire partition with no
read
I have no particular desire to use it. I just tried everything else
first and thought it was worth a shot.
If you think that version would help, can you point me to the git
repo? The one I grabbed was
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git.
On Mon, Jun 23, 2014 at
Hi Mike,
On 06/24/2014 11:04 AM, Mike Hartman wrote:
I have no particular desire to use it. I just tried everything else
first and thought it was worth a shot.
If you think that version would help, can you point me to the git
repo? The one I grabbed was
On Jun 23, 2014, at 8:58 PM, Mike Hartman m...@hartmanipulation.com wrote:
I have a dd image, but not a btrfs-image. I ran the btrfs-image
command, but it threw the same errors as everything else and generated
a 0 byte file.
I agree that it SOUNDS like some kind of media failure, but if so
Of course it could just be a bug so it's worth trying David's integration
branch.
I'll try that shortly.
* Firmware Version: 0006
Firmware 0007 is current for this SSD.
I assume that's probably not something I should mess with right now
though, right?
6 0x008 4
On Jun 23, 2014, at 10:34 PM, Mike Hartman m...@hartmanipulation.com wrote:
Firmware 0007 is current for this SSD.
I assume that's probably not something I should mess with right now
though, right?
I would deal with that later. A firmware change now might make things worse if
you care
My two cents:-)
If you really want to use btrfs check --init-csum-tree
--init-extent-tree,
i'd suggest you use
David Latest btrfs-progs branch which includes some latest bug fixes.
I have no particular desire to use it. I just tried everything else
first and thought it was worth a shot.
I zeroed out the drive and ran every smartctl test on it I could find
and it never threw any more errors.
Zeroing SSDs isn't a good way to do it. Use ATA Secure Erase instead. The
drive is overprovisioned, so there are pages without LBAs assigned, which
means they can't be written to by
17 matches
Mail list logo
