Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Encrypted debian testing HDD crashed

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
tharumus
Posts: 3
Joined: 2017-08-07 23:30

Encrypted debian testing HDD crashed

#1 Post by tharumus »

The other day my HDD completely crashed. I tried to go into system recovery to run

Code: Select all

 fsck /dev/sdb5
but was denied permission as the OS was unable to use sudo. All of the horrible noise and ext4 errors tell me it's probably toast.

I attempted to follow some steps to recover data from the drive from my ubuntu HDD, but have hit a snag. It seems the file system on the drive is also gone. I followed the top answer from this post: https://askubuntu.com/questions/653408/ ... om-live-cd

Let me post some outputs.

From

Code: Select all

fdisk -l
:

Code: Select all

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0d728cd1

Device     Boot  Start        End    Sectors  Size Id Type
/dev/sdb1         2048     499711     497664  243M 83 Linux
/dev/sdb2       501758 3907028991 3906527234  1.8T  5 Extended
/dev/sdb5       501760 3907028991 3906527232  1.8T 83 Linux

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/sdb5_crpyt: 1.8 TiB, 2000139845632 bytes, 3906523136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/xavi--vg-root: 28 GiB, 29997662208 bytes, 58589184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/xavi--vg-swap_1: 16 GiB, 17108566016 bytes, 33415168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/xavi--vg-home: 1.8 TiB, 1953031520256 bytes, 3814514688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
When trying to mount

Code: Select all

mount /dev/xavi-vg/root /mnt/
:

Code: Select all

mount: wrong fs type, bad option, bad superblock on /dev/mapper/xavi--vg-root,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
Is there anything else to try?


tharumus
Posts: 3
Joined: 2017-08-07 23:30

Re: Encrypted debian testing HDD crashed

#3 Post by tharumus »

I have my important files backed up already, but never made one for my complete system. If the drive is completely gone (ie. no hope of getting anything from it), it's not too big of a deal. That said, if there was a chance to pull out my home directory, it would save me the effort of setting up a fresh install.

User avatar
dasein
Posts: 7680
Joined: 2011-03-04 01:06
Location: Terra Incantationum

Re: Encrypted debian testing HDD crashed

#4 Post by dasein »

tharumus wrote:I... never made one for my complete system.
A dispassionate observer might imagine that anything worth encrypting in the first place is also worth backing up.
tharumus wrote:If the drive is completely gone...
You're the one reporting horrible noises from an intentionally pre-corrupted drive. You seriously imagining that there's a lot to be done here?

tharumus
Posts: 3
Joined: 2017-08-07 23:30

Re: Encrypted debian testing HDD crashed

#5 Post by tharumus »

dasein wrote:
tharumus wrote:I... never made one for my complete system.
A dispassionate observer might imagine that anything worth encrypting in the first place is also worth backing up.
tharumus wrote:If the drive is completely gone...
You're the one reporting horrible noises from an intentionally pre-corrupted drive. You seriously imagining that there's a lot to be done here?
I'm not really sure why you're being so snark. If you don't have anything to offer why even comment?

Post Reply