I am having problems with Mondo Rescue. I have two drives. One 20 gig, one 300 gig.

Initializing...
See /var/log/mondo-archive.log for details of backup run.
Checking sanity of your Linux distribution
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3 doesn't contain a valid partition table
Done.
Fatal error... output folder does not exist - please create it
---FATALERROR--- output folder does not exist - please create it
If you require technical support, please contact the mailing list.
See http://www.mondorescue.org for details.
The list's members can help you, if you attach that file to your e-mail.
Log file: /var/log/mondo-archive.log
FYI, I have gzipped the log and saved it to /tmp/MA.log.gz
Mondo has aborted.
Execution run ended; result=254
Type 'less /var/log/mondo-archive.log' to see the output log

fdisk -l

Disk /dev/dm-0: 6308 MB, 6308233216 bytes
255 heads, 63 sectors/track, 766 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 973 MB, 973078528 bytes
255 heads, 63 sectors/track, 118 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 299.5 GB, 299573968896 bytes
255 heads, 63 sectors/track, 36421 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-2 doesn't contain a valid partition table

Disk /dev/dm-3: 22.4 GB, 22481469440 bytes
255 heads, 63 sectors/track, 2733 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-3 doesn't contain a valid partition table

looks like the data on your disks is broken. period.

not sure what the question is here.

Disk /dev/sda: 160.0 GB, 160041885696 bytes
116 heads, 43 sectors/track, 62666 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xfd7382ed

Device Boot Start End Blocks Id System
/dev/sda1 * 43 188067551 94033754+ 7 HPFS/NTFS
/dev/sda2 188067552 188476567 204508 83 Linux
/dev/sda3 188476568 312578007 62050720 8e Linux LVM

Disk /dev/dm-0: 62.4 GB, 62444797952 bytes
255 heads, 63 sectors/track, 7591 cylinders, total 121962496 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 1040 MB, 1040187392 bytes
255 heads, 63 sectors/track, 126 cylinders, total 2031616 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x30307800

Disk /dev/dm-1 doesn't contain a valid partition table


Okay, now the question I have is; 1. what does this mean, and 2. how do I repair the partition?

I don't remember what I did to fix it.

I use g4u now instead. http://www.feyrer.de/g4u/

Maybe fdisk doesn't know how to talk LVM. The errors I get with fdisk all point to the logical volumes.

Isnt /dev/dm-x a device mapper virtual mount point?

I only use those for mounting flash drives, and mapping encrypted partitions.

Sorry, i dont do LVM anymore, after a small problem lost me 300GB of data. Its much easier to backup.

How to remove them?

You don't remove them. Just don't look at them. Seriously. Those are device mapper devices. They usually are associated with LVM and correspond to the logical volumes. But those devices can also appear in the fdisk report when things such as flash drives and camera memory are connected to the computer. Anyway, they're normal.

This has been very helpful to me. I found this thread by Goggle on
dm-0 because I also got the no partition table error message. Here is what
I think:
When the programs fdisk and sfdisk are run with the option -l and no argument, e.g.
# /sbin/fdisk -l
they look for all devices that can have cylinders, heads, sectors, etc.
If they find such a device, they output that information to standard
output and they output the partition table to standard output. If there is
no partition table, they have an error message (also standard output).
One can see this by piping to 'less', e.g.
# /sbin/fdisk -l | less
the error messages disappear.
/dev/dm-0 ... /dev/dm3 on my fedora C5 system seem to be device mappers
associated with LVM. RAID might also require device mappers.

Well, I got the "/dev/dm-0" messages when I had simply removed partitions containing LVM.
I then removed the VGs and PVs and I didn't get the messeges anymore when running "fdisk -l".

0 members found this post helpful.