> My mistake, the same printks are printed when the encryption key is > incorrect, I've seen that here. > It looks like you have some ugly hardware errors. > The kernel cannot read from the drive, so it cannot guess the file system on > it. > If the data is valuable, you could try to ddrescue the drive to a bigger one. > (>750GB... and that will take time...) and attempt to mount the rescued data. > If the drive is in an USB enclosure, you could plug it directly via SATA to > the system (maybe it has issues?).
The hard drive is brand new, I also plugged it directly via eSATA and checked the SMART data and run some tests and it succeeded in all, if I format the drive again I have a working file-system for sure but some of my data that is not on the backup disk will be gone.. I had some time ago on opensuse tumbleweed a encrypted btrfs system and it was gone some time ago like this external hard drive, I also had various btrfs hard drives without encryption and they never failed, and I will make a image of the disk but that will be later because I don't have a backup hard drive bigger than 750gb, maybe btrfs fsck can restore my disk when it is officially released? -- Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
