1 Topic by Stroke_Papy (edited by Stroke_Papy 2022-10-17 09:46:32)

  • Stroke_Papy
  • New member
  • Offline
  • Registered: 2022-10-11
  • Posts: 5

Topic: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

I'm on MX Linux, the updates are done.

In GParted I see the partition /dev/sda5 is unknown

if I do Search for file systems on /dev/sda

The disk scan by gpart did not find any recognizable file systems on this disk.

But in

root@yoko:/home/yoko# parted /dev/sda unit s print
Model: ATA OCZ-VERTEX4 (scsi)
Disk /dev/sda: 250069680s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start       End         Size        Type      File system  Flags
 1      2048s       239820799s  239818752s  primary   ext4
 4      239824896s  250068991s  10244096s   extended
 5      239826944s  250068991s  10242048s   logical

root@yoko:/home/yoko# fdisk -l -u /dev/sda
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: OCZ-VERTEX4     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8f4a4f29

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048 239820799 239818752 114.4G 83 Linux
/dev/sda4       239824896 250068991  10244096   4.9G  5 Extended
/dev/sda5       239826944 250068991  10242048   4.9G  b W95 FAT32

On https://gparted.org/h2-fix-msdos-pt.php the case is not specified

How to recover data from /dev/sda5 partition

Thanks alot

2 Reply by mfleetwo

  • mfleetwo
  • Developer
  • Offline
  • Registered: 2012-05-18
  • Posts: 477

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

What file system do you expect to be in /dev/sda5?  (FAT32, EXT4, etc)

What actions lead up to it's loss?

Run these query commands as root:

blkid /dev/sda5
dd if=/dev/sda5 bs=1M count=1 | hexdump -C | head -30

3 Reply by Stroke_Papy

  • Stroke_Papy
  • New member
  • Offline
  • Registered: 2022-10-11
  • Posts: 5

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

mfleetwo wrote:

What file system do you expect to be in /dev/sda5?  (FAT32, EXT4, etc)]

FAT32


mfleetwo wrote:

What actions lead up to it's loss?]

all the data


mfleetwo wrote:

Run these query commands as root:

blkid /dev/sda5
dd if=/dev/sda5 bs=1M count=1 | hexdump -C | head -30

I think the data of  PTUUID="f6eab51b" and PARTUUID="8f4a4f29-05" corrupt

root@yoko:/home/yoko# blkid /dev/sda5
/dev/sda5: PTUUID="f6eab51b" PTTYPE="dos" PARTUUID="8f4a4f29-05"
root@yoko:/home/yoko# dd if=/dev/sda5 bs=1M count=1 | hexdump -C | head -30
1+0 records in
1+0 records out
00000000  fa b8 00 10 8e d0 bc 00  b0 b8 00 00 8e d8 8e c0  |................|
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0106748 s, 98.2 MB/s00000010  fb be 00 7c bf 00 06 b9  00 02 f3 a4 ea 21 06 00  |...|.........!..|

00000020  00 be be 07 38 04 75 0b  83 c6 10 81 fe fe 07 75  |....8.u........u|
00000030  f3 eb 16 b4 02 b0 01 bb  00 7c b2 80 8a 74 01 8b  |.........|...t..|
00000040  4c 02 cd 13 ea 00 7c 00  00 eb fe 00 00 00 00 00  |L.....|.........|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  00 00 00 00 00 00 00 00  1b b5 ea f6 00 00 00 00  |................|
000001c0  01 20 0c 03 d0 ff 00 08  00 00 00 f8 03 00 00 00  |. ..............|
000001d0  01 00 83 fe ff ff 00 00  04 00 00 60 98 03 00 00  |...........`....|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00100000

Thank you very much for spending time for me

4 Reply by mfleetwo

  • mfleetwo
  • Developer
  • Offline
  • Registered: 2012-05-18
  • Posts: 477

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

You have misunderstood my question.  "All the data" is the answer to what was lost.  I asked how was it lost?

The contents of the partition sda5 is an MSDOS partition table from a 31 GB device, not a FAT32 file system.  It looks like this:

# fdisk -l /dev/loop0

Disk /dev/loop0: 5243 MB, 5243928576 bytes, 10242048 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xf6eab51b

      Device Boot      Start         End      Blocks   Id  System
/dev/loop0p1            2048      262143      130048    c  W95 FAT32 (LBA)
/dev/loop0p2          262144    60579839    30158848   83  Linux

5 Reply by Stroke_Papy

  • Stroke_Papy
  • New member
  • Offline
  • Registered: 2022-10-11
  • Posts: 5

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

Hello
First of all I had a stroke, and lost things, I don't master the partition table and my mother tongue and not English!!!!!!

My memories I made two partitions to cut my disk one for MxLinux and another for data. I created the second partition in NTFS or FAT32

After playing for months, I no longer found the data partition, now the data partition is no longer recognized

I tried attempt data rescue, but without success. How to rescue lost data


root@yoko:/home/yoko# fdisk -l -u /dev/sda
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: OCZ-VERTEX4
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: back
Disk identifier: 0x8f4a4f29

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 239820799 239818752 114.4G 83 Linux
/dev/sda4 239824896 250068991 10244096 4.9G 5 Extended
/dev/sda5 239826944 250068991 10242048 4.9G b W95 FAT32

Thanks a lot

6 Reply by mfleetwo

  • mfleetwo
  • Developer
  • Offline
  • Registered: 2012-05-18
  • Posts: 477

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

https://translate.google.com/ can be used to translate many languages.

An MSDOS partition table belongs at sector 0 of a drive.  No partition tool, including GParted, will write an MSDOS partition table anywhere else.  However the start of partition sda5 contains an MSDOS partition table.  To me that strongly suggests it was copied there manually.  Which further suggests that the rest of partition sda5 has been overwritten and anything it use to contain is lost.

Run this command to see what is in the second MiB of data in partition sda5.

dd if=/dev/sda5 bs=1M skip=1 count=1 2> /dev/null | hexdump -C | head -30

7 Reply by Stroke_Papy

  • Stroke_Papy
  • New member
  • Offline
  • Registered: 2022-10-11
  • Posts: 5

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

root@yoko:/home/yoko# dd if=/dev/sda5 bs=1M skip=1 count=1 2> /dev/null | hexdump -C | head -30
00000000  eb 58 90 6d 6b 66 73 2e  66 61 74 00 02 01 20 00  |.X.mkfs.fat... .|
00000010  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 08 00 00  |........?.......|
00000020  e0 f7 03 00 d1 07 00 00  00 00 00 00 02 00 00 00  |................|
00000030  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  80 01 29 7e ff c4 cd 42  4f 4f 54 20 20 20 20 20  |..)~...BOOT     |
00000050  20 20 46 41 54 33 32 20  20 20 0e 1f be 77 7c ac  |  FAT32   ...w|.|
00000060  22 c0 74 0b 56 b4 0e bb  07 00 cd 10 5e eb f0 32  |".t.V.......^..2|
00000070  e4 cd 16 cd 19 eb fe 54  68 69 73 20 69 73 20 6e  |.......This is n|
00000080  6f 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 64 69  |ot a bootable di|
00000090  73 6b 2e 20 20 50 6c 65  61 73 65 20 69 6e 73 65  |sk.  Please inse|
000000a0  72 74 20 61 20 62 6f 6f  74 61 62 6c 65 20 66 6c  |rt a bootable fl|
000000b0  6f 70 70 79 20 61 6e 64  0d 0a 70 72 65 73 73 20  |oppy and..press |
000000c0  61 6e 79 20 6b 65 79 20  74 6f 20 74 72 79 20 61  |any key to try a|
000000d0  67 61 69 6e 20 2e 2e 2e  20 0d 0a 00 00 00 00 00  |gain ... .......|
000000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200  52 52 61 41 00 00 00 00  00 00 00 00 00 00 00 00  |RRaA............|
00000210  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000003e0  00 00 00 00 72 72 41 61  70 a1 01 00 5f 04 00 00  |....rrAap..._...|
000003f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000400  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00000c00  eb 58 90 6d 6b 66 73 2e  66 61 74 00 02 01 20 00  |.X.mkfs.fat... .|
00000c10  02 00 00 00 00 f8 00 00  3f 00 ff 00 00 08 00 00  |........?.......|
00000c20  e0 f7 03 00 d1 07 00 00  00 00 00 00 02 00 00 00  |................|
00000c30  01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000c40  80 00 29 7e ff c4 cd 42  4f 4f 54 20 20 20 20 20  |..)~...BOOT     |
00000c50  20 20 46 41 54 33 32 20  20 20 0e 1f be 77 7c ac  |  FAT32   ...w|.|
root@yoko:/home/yoko#

I use all the time https://translate.google.be/ thank you

8 Reply by mfleetwo

  • mfleetwo
  • Developer
  • Offline
  • Registered: 2012-05-18
  • Posts: 477

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

That is a FAT file system starting in the second MiB of partition sda5.

Mount it read-only so you can access all the files.

mount -o ro,offset=$((1024 * 1024)) /dev/sda5 /mnt

You should copy all the files you want somewhere else.

When done unmount.

umount /mnt

9 Reply by Stroke_Papy

  • Stroke_Papy
  • New member
  • Offline
  • Registered: 2022-10-11
  • Posts: 5

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

Hello

It works thank you very much but a question !!! Why in 

lsblk

command I don't see the mounted disk but  loop0 ???


root@yoko:/mnt# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0   4.9G  1 loop /mnt
sda      8:0    0 119.2G  0 disk 
├─sda1   8:1    0 114.4G  0 part /
├─sda4   8:4    0   512B  0 part 
└─sda5   8:5    0   4.9G  0 part 
sr0     11:0    1  1024M  0 rom

Thanks again for spending time with me.

10 Reply by mfleetwo

  • mfleetwo
  • Developer
  • Offline
  • Registered: 2012-05-18
  • Posts: 477

Re: [Solved] Fix Unable to Satisfy MS DOS Partition Tables

The offset parameter to mount implies the use of losetup to create a loop device to implement.  The loop device will be automatically removed when the file system is unmounted.  Run losetup -a to display.  Read about the offset parameter in the mount manual page.