Unknown Partition 39;recovery.img 39;

[Lorri Dent]

editedto merge the thread and to turn images into links (i don't have a way to directly copy the text from the terminal right now and i don't want to type out all the terminal outputs by hand so you'll have to click on links instead

so i was gradually making the ntfs partition smaller and the ext4 one bigger using kde partition manager, and when i tried to delete the rest of the ntfs drive and resize the ext4 partition to fit it, it failed after moving the files to the left (by 700gb)

I found a testdisk partition table backup from the first time i tried it, and it lists a 134mb used / 128mb unknown partition and a 1153GB used out of 1074GB partition. Both of them display the same filesystem corrupted thing when i try to preview the files, but it lets me select both as primary. is there anything i can do with this?

Then try your luck with testdisk, and others... if you're lucky the original partition is still whole but it depends on what exactly that program was doing. If it died mid-move, there might not be a single partition but at least two segments of one... you could use dm-linear to map it but you'd have to identify those segments first. Testdisk doesn't handle that. If the kde partitioner does not have a resume and recovery function, then probably no other program handles it either. If it can be done at all, it will be a manual process.

The images in your posts are mostly text you could post in [ code ] tags. If you must post images, please read the General Guidelines and post only thumbnails or links to images. Please edit your previous posts to remove the huge images.

If it's a known file type (for example, Stardew Valley uses XML) you can try to search photorec for (text files with header tx?) type and then you'll have to check file contents yourself (take a known good savefile and grep for unique contents like specific xml tags).

As for recovering the filesystem itself, it may be possible in theory but there isn't a ready made tool for recovering a botched mid-move. If it can be done it'll be a manual process of identifying the data segments on disk.

My hard drive changed to raw, and now do not show in Windows! In the data manager, I can see that it exists. Unknown disk no initiated! Is anyone who has any idea how to format or restore it? I have my child's movie, photo and much more on it.

Undoubtedly, it is not an enjoyable thing to go through. Many users urgently need methods of data recovery from unknown partitions and how to recover unallocated partition, hoping to get rid of a data loss.

When facing the disk unknown not initialized issue, users may get panicked. After all, no one wants to lose the work they spent days or weeks working on, no one wants to lose his cherished memories with families or friends, and no one wants to pay too much for data recovery service.

Hi all, I apologise in advance if there is an article already similar to this that I couldn't find in the end. I've looked at (Boot Repair(the old dual boot drama)) and petsam's guide to chrooting Garuda Linux.

For context, my issue seems to be that I'm stuck in boot rescue as it can't find the efi I believe to boot and when trying ls on each partition it tells me "Filesystem is unknown" and trying set root=(hd0, gpt) etc and prefix with insmod=normal then boot it doesn't work as those commands aren't found.

This command should be pointed at the partition the system is installed on (not the EFI partition). In your case I believe that will be either nvme0n1p2 or nvme0n1p3. If you are not sure which partition it is, it would be best to mount them both and run lsblk -f again to help figure it out.

I'm unsure what file system I used but I'm 60% sure it was btrfs. But not sure why there is a FAT32 there. I know there was a file system when it was installed but for some reason reverted or file system got an issue and now partitions are unformated. I don't want to be too careless with repairing it as there isn't a whole lot that I'd lose but lots of time wasted if it does.

I'm a little confused, did you install fresh over the same drive and partition you are having issues with or on a separate drive or partition still trying to read the partition that you couldn't access before?

If you installed over the same drive and partition and still having issues my guess something about your drive might be going bad, something about your computer setup maybe a bios/UEFI settings might be causing issues or something is happening during install/initial boot corrupting the drive.

If it's a separate drive/partition at this point I would try a different Linux distribution to see if it's an issue with Garuda specifically or not. I would try a distribution with a wide support of file systems already pre-installed just so you can determine what file system is the one you are trying to access. There is a small chance that the file system you are trying to read may not be pre-installed on Garuda or an issue is causing Garuda not to see it.

Just a thought... You might want to check if there is a firmware update to your drive or even a bios update to your computer/motherboard just to make sure you are not chasing your tail over a such an issue. This is really a last ditch effort if nothing else works but worth a try.

I've tried testdisk and ddrescue but no luck in recovering. Tried other distributions but no luck for file types. I think it's just unrecoverable at the moment.

Not familiar with fixing partitions but should I just reinstall onto the partitions which overwrites it or should I change the partitions first?

Ah okay, sweet. Thanks for trying to help though. I think I know why it became like this. Basically after a certain update to the grub file the initrd command line with the amd_ucode.img and linux.img kept failing because there wasn't a space between them, there was either a ^ or something. But when separated with another initrd it would work. I think the repeated shutdown when the grub file changed and tried to boot might have corrupted it or something else. I'll just be more careful I think. Any recommendations for distributions garuda or otherwise? I tried dragonized but probably want a more lightweight/customizable one.

What made you think about this exactly? If such a thing is true, it is a very serious bug (if it is caused from a Garuda utility, or other Archlinux instruction/command).

Give more details and please write more facts and no assumptions.

Well I don't have my computer working still so I can't get screenshots but I think in /boot/grub.d (or conf.d)/grub.cfg when it gives you the boot list options for certain kernels like zen or lts and I think between x86 or 64 (around 4 different boot options) it has initrd with amd_ucode.img^(lts-kernel). If I ran my PC with this, it would not boot. If I separated with two initrd it would run. I only use lts, not sure what version. I can't give you facts, given I am not qualified enough to have known what caused this issue in the first place. All I know is that it wouldn't boot like this. If it was a bug, I'd have figured your forum would have something on it which it didn't so I figured it was just an issue for myself.

Although whenever I changed the file to be separated lines, next update to the system with pacman -Syu it would change it back.

Hai if you have bootable garuda usb..boot into garuda linux...Go to gparted. select the hard drive where boot is located..you will receive error message saying your harddrive primary gpt parition file is corrupted, but back up is loaded...select the boot partition and do right click to get options.. in that select manage flag option...select "bios_grub" flag. you may see your harddrive getting mounted. shutdown , remove bootable usb and start into garuda linux...This worked for me. hope it works for you as well...

I was able to break out of the network boot loop and poke around in u-boot and something I noticed was when I did "mmc part" it returned "unknown partition table type 0" and then listed no partitions.

I'll try a different SD card, since I suppose there could be a reason why the Armbian image isn't writing properly (even though it passes Etcher validation) but every other distro I've tried boots up just fine.

I had an issue with my router (linksys 1200ac) config so I tried to edit a file on the alternate partition (re-enabling dnsmasq) for that I ubiattach (or something like that) the mtd5 and 7 and many others. then I mounted mtd5 and edited the config. when via addvanced-reboot to the alternative partition which was shown as number and for its OS it said linksys/unknown (I think) , I rebooted the alternative partition.

now my device is bricked.

it just shows a power LED blinking every second.

3a8082e126