Opened 12 years ago
Closed 8 years ago
#633 closed defect (worksforme)
No filesystem could mount root during restore
Reported by: | Victor | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | highest | Milestone: | 3.2.2 |
Component: | mondo | Version: | 3.0.1 |
Severity: | blocker | Keywords: | |
Cc: |
Description (last modified by )
I am trying to restore a RedHat6.2 image created by mondorescue(3.0.1). During PXE network boot, I got following error:
List of all partitions:
No filesystem could mount root, tried: iso9660 kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(1,0) Pid: 1, comm: swapper Not tainted 2.6.32-220.el6.x86_64 #1 Call Trace:
I basically followed README.pxe.
It works fine with RedHat5.
During mondoarchive, I noticed "Disk /dev/mapper/vg_dcvops01-lv_root doesn't contain a valid partition table" poped up, which showed up on 'fdisk -l'.
[Redhat 6.2]# fdisk -l Disk /dev/sda: 53.7 GB, 53687091200 bytes 255 heads, 63 sectors/track, 6527 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0009758d Device Boot Start End Blocks Id System /dev/sda1 * 1 64 512000 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 64 6528 51915776 8e Linux LVM Disk /dev/mapper/vg_dcvops01-lv_root: 48.9 GB, 48930750464 bytes 255 heads, 63 sectors/track, 5948 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/mapper/vg_dcvops01-lv_root doesn't contain a valid partition table [Redhat 5]# fdisk -l Disk /dev/sda: 214.7 GB, 214748364800 bytes 255 heads, 63 sectors/track, 26108 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 65 522081 83 Linux /dev/sda2 66 26108 209190397+ 8e Linux LVM
Victor Feng
Attachments (8)
Change History (31)
comment:1 by , 12 years ago
by , 12 years ago
Attachment: | mondoarchive.log added |
---|
by , 12 years ago
comment:2 by , 12 years ago
Hi Bruno,
The PXE restore hang from the very beginning. So there is no mondorestore.log. The screenshot shows where the restore hang.
Thank you Victor
comment:3 by , 12 years ago
Description: | modified (diff) |
---|---|
Status: | new → assigned |
comment:4 by , 12 years ago
Ok, so can you share your PXE conf file please, so I have an idea of how you call mondo at restore time at least.
comment:5 by , 12 years ago
Have you tested MondoRescue on RedHat6(6.2)? Did it work for you?
Here is the PXE conf which is recommended in README file of Mondo. It worked fine for RedHat 5.
[root@prvkck01 pxelinux.cfg]# cat dcvops01 default mondo label mondo kernel img/dcvops01/vmlinuz append initrd=img/dcvops01/initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=131072 rw roo t=/dev/ram iso_mode acpi=off apm=off devfs=nomount exec-shield=0 pxe prefix=dcvops01-20120621-arch ive nfsmount=10.142.111.21:/mondo [root@prvkck01 pxelinux.cfg]#
comment:6 by , 12 years ago
Could you try increasing the ramdisk size, as it seems to not been recognized correctly, so maybe you lack memory.
Try:
ramdisk_size=1000000
comment:8 by , 12 years ago
To answer to a previsou question yes, I did multiple RHEL6.x tests without particualr issue. However, I remarked that you were using 3.0.1. Could you update to 3.0.2 or the beta of 3.0.3 instead ?
Same for mindi which is 2.1.1 to 2.1.3.
Also ensure you have mindi-busybox 1.18.5 as previous version also had an error related to what you mention (sorry didn't thought to that first).
comment:9 by , 12 years ago
Hi Bruno,
I upgraded to 3.0.2. mindi to 2.1.3. mindi-busybox to 1.18.5 in the client box. During the PXE install, I ran into "The mondorestore command was not found on your backup media" error. Please see the attachment "mondorestore was not found".
Victor
comment:10 by , 12 years ago
could you look upper in your screen, has there should a problem with the NFS mount IMO
by , 12 years ago
Attachment: | No filesystem could mount root2.doc added |
---|
mondorestore was not found 2
comment:11 by , 12 years ago
I did not. But I did see Can't find CD's /mnt/cdrom/images/all.tar.gz.
Please see the attachment.
comment:12 by , 12 years ago
When you increase the ramdisk, then you go further (it does make a difference). But not enough and mondorestore is not found as your NFS mount point is not mounted correctly. THat's this error tha would be interesting to see.
by , 12 years ago
Attachment: | No filesystem could mount root3.doc added |
---|
comment:13 by , 12 years ago
I increased it to 5G, and got same error. I noticed error "udevd: specified group 'cdrom' unknown". Please see the attachment.
default mondo label mondo
kernel img/dcvops01/vmlinuz append initrd=img/dcvops01/initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=5000000 rw root=/dev/ram iso_mode acpi=off apm=off devfs=nomount exec-shield=0 pxe prefix=dcvop
s01-archive-20121025 nfsmount=10.142.111.21:/mondo
comment:14 by , 12 years ago
You have 2 types of errors. One linked to the lack of memory, another onelinked to the fact you do not mount your NFS share (or at least that's what I guess with the info you gave).
With 5GB you don't see your kernel crashing don't you ? So find the NFS error on the screen (go back with Shuft PgUp if needed) and fix what is not working if you can or report why it's not working at that moment.
udev prints tons of such error msgs which are harmless.
by , 12 years ago
Attachment: | mondorestore was not found4.doc added |
---|
comment:15 by , 12 years ago
I could not Shift PageUp to the very begining. I could go up to about 10 pages. Attached is the page where could not go further. I did not see kernel crashing, nor NFS error.
comment:17 by , 11 years ago
How can I confirm that?
It is the same virtual machine running RHT5 and RHT6, and I used same command mondoarchive. When it is RHT5, restore succeeds. When it is RHT6, it does not.
Victor
comment:18 by , 11 years ago
From your log you seem to be using an Intel e1000 NIC. The driver seems to be included in the backup:
Adding lib/modules/2.6.32-220.el6.x86_64/kernel/drivers/net/e1000/e1000.ko (292 KB) to the rootfs
Can you try to relaunch the start-nfs script manually in the console and report the errors seen there.
comment:19 by , 11 years ago
Could you try again with the latest version of MondoRescue to see whether you stil lhave the issue ?
comment:20 by , 10 years ago
I just downloaded the latest MondoRescue 3.0.4 today. It does not work when I tried to restore. But the error is different:
"The mondorestore command was not found on your backup media"
Please the attached screenshot.
victor
by , 10 years ago
Attachment: | mondorestore command not found.doc added |
---|
comment:22 by , 9 years ago
Milestone: | 3.0.5 → 3.2.2 |
---|
Could you verify again with the new 3.2.1 please ?
comment:23 by , 8 years ago
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
Could you share the /var/log/mondoarchive.log and /var/log/mondorestore.log files so I can see better what is happenin in your env ?