Timeline for How to recover data from EBS volume showing no partition or filesystem?
Current License: CC BY-SA 4.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19 at 8:41 | history | edited | Kusalananda♦ | CC BY-SA 4.0 | More info about issue in title, minor mods to text to fix markup and grammar |
| May 19 at 5:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 15 at 18:09 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 11, 2024 at 9:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 12, 2024 at 22:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 12, 2024 at 21:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 31, 2023 at 0:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 1, 2023 at 21:08 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 2, 2022 at 12:48 | answer | added | Biapy | timeline score: -1 | |
| Nov 10, 2021 at 8:36 | history | edited | HelloWorld | CC BY-SA 4.0 | edited body |
| Nov 9, 2021 at 9:03 | comment | added | HelloWorld | It cannot be garbage. It is just a volume restored for a healthly EBS snapshot made by AWS Backup. The encryption point is valid though, the disk is encrypted! But I am attaching the respective managed EBS KMS key to the volume provided by AWS | |
| Nov 9, 2021 at 8:03 | comment | added | muru | "The volume has data inside: /dev/nvme1n1: data"... no, that just means file couldn't identify what the contents are. It could be garbage for all we know. It might be an encrypted volume. Nothing so far shows you have a valid filesystem there. | |
| Nov 9, 2021 at 7:55 | history | edited | HelloWorld | CC BY-SA 4.0 | added 647 characters in body |
| Nov 9, 2021 at 7:54 | comment | added | HelloWorld | I am aware of the post that you linked. I appended the output of fsck to the question. | |
| Nov 8, 2021 at 21:09 | comment | added | Valentin Bajrami | dmesg is explicitly mentioning EXT4-fs (nvme1n1): VFS: Can't find ext4 filesystem . The nvme0n1 has indeed the boot partition on ext4 but we don't have to deal with that. I see there are some related posts like yours here: unix.stackexchange.com/questions/315063/… Please have a look there but don't run mkfs or anything like this because this might cause data loss. Running fsck can help and won't harm. | |
| Nov 8, 2021 at 16:06 | comment | added | HelloWorld | Why do you think it is ext4 though? If you look above Error: /dev/nvme1n1: unrecognised disk label. /dev/nvme0n1 which is the root is ext4. Is there a case this confused you? | |
| Nov 8, 2021 at 16:05 | comment | added | HelloWorld | Same error with dmesg [11877.345591] EXT4-fs (nvme1n1): VFS: Can't find ext4 filesystem | |
| Nov 8, 2021 at 14:50 | comment | added | Valentin Bajrami | @Dimitris. Did you try the -r flag? What does the dmesg show you then? | |
| Nov 8, 2021 at 13:53 | comment | added | HelloWorld | @ValentinBajrami Right. I did try to mount the whole disk as an ext4 with sudo mount /dev/nvme1n1 mount_point/ -t ext4 and it failed with the same message. Do I get something wrong? | |
| Nov 8, 2021 at 13:45 | comment | added | Valentin Bajrami | @Dimitris there is no nvme1n1p1 . Here p1 would refer to the first partition on the block device which you don't have as I mentioned in my previous comments which I deleted. You need to mount the whole disk since the partition (it seems ) has been created on the whole disk. | |
| Nov 8, 2021 at 13:43 | comment | added | HelloWorld | sudo mount /dev/nvme1n1p1 ctf/ -t ext4 results to mount: /home/ubuntu/ctf: special device /dev/nvme1n1p1 does not exist. | |
| Nov 8, 2021 at 13:25 | comment | added | Valentin Bajrami | Alright, before jumping into performing disk checks and stuff, I think you could try the following: mount -r -t ext4 /dev/nvme1n1 /some/mountpoint which will mount the disk read-only and in this case (since dmesg is showing ext4) it most probably is an ext4 file system. | |
| Nov 8, 2021 at 13:18 | comment | added | HelloWorld | Added at the bottom too. | |
| Nov 8, 2021 at 13:18 | history | edited | HelloWorld | CC BY-SA 4.0 | added 300 characters in body |
| Nov 8, 2021 at 12:51 | comment | added | HelloWorld | @ValentinBajrami Added the output of the command to the question! | |
| Nov 8, 2021 at 12:50 | history | edited | HelloWorld | CC BY-SA 4.0 | added 557 characters in body |
| Nov 8, 2021 at 12:08 | history | asked | HelloWorld | CC BY-SA 4.0 |