tran_2012
asked on
Linux : Booting Error after restoring image from OLD PC
HI
We had a really old Linux RedHat server, this server is playing up so, we have taken an image and restore onto new dell pc, Now the problem is its giving below error while booting,
ERROR: /bin/insmod exited abnormally!
Loading jbd.o module
Journalled Block Device driver loaded
Loading etx3.o module
Creating block devices
VFS Cannot open root device "LABEL-/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
We have no option to install the linux server from fresh, as we are running programming language called edacle and it not more exist, so, i need to have this image boot and working on new pc.
i did run manual grub boot sequestration and result are attached
Please help with most idiot proof steps as i am totally newbie to Linux,
The Grub Version 0.93
Thanks
IMG_20160420_092802.jpg
IMG_20160420_092926.jpg
fstab.png
We had a really old Linux RedHat server, this server is playing up so, we have taken an image and restore onto new dell pc, Now the problem is its giving below error while booting,
ERROR: /bin/insmod exited abnormally!
Loading jbd.o module
Journalled Block Device driver loaded
Loading etx3.o module
Creating block devices
VFS Cannot open root device "LABEL-/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
We have no option to install the linux server from fresh, as we are running programming language called edacle and it not more exist, so, i need to have this image boot and working on new pc.
i did run manual grub boot sequestration and result are attached
Please help with most idiot proof steps as i am totally newbie to Linux,
The Grub Version 0.93
Thanks
IMG_20160420_092802.jpg
IMG_20160420_092926.jpg
fstab.png
You might be fine to remove the UUID reference on the boot.
How the new system relate to the old I.e drive types the same sata? Or the two have different drive types the new sas the old sata?
How the new system relate to the old I.e drive types the same sata? Or the two have different drive types the new sas the old sata?
ASKER
Hi Arnold
I can not see any UUID reference on the boot options
The old system had LSI MEGA raid disk SCSI/SAS,
New System is Normal DELL i3 Machine with SATA Disks
I can not see any UUID reference on the boot options
The old system had LSI MEGA raid disk SCSI/SAS,
New System is Normal DELL i3 Machine with SATA Disks
Yor referencing in the path /etc/fstab is the issue
/dev/sda1
Look at what the new system drive naming convention is.
fdisk -l
If you had lvm, lvmdiskscan pvdisplay, vgdisplay, lvdisplay.
/dev/sda1
Look at what the new system drive naming convention is.
fdisk -l
If you had lvm, lvmdiskscan pvdisplay, vgdisplay, lvdisplay.
ASKER
hi arnold
See attached fdisk out put and let me know what to change in fstab file, i have attached fstab file as well
thanks
fdisk-Output.jpg
Boot-Screen.jpg
Boot-Options-Details.jpg
See attached fdisk out put and let me know what to change in fstab file, i have attached fstab file as well
thanks
fdisk-Output.jpg
Boot-Screen.jpg
Boot-Options-Details.jpg
When you specify the kernel command line you should use = not - in LABEL...
kernel ..... root=LABEL=/
the image shows root=LABEL-/
I guess is that this would work out. Don't edit /etc/fstab just yet, it is consistent with the kernel command line.
After booting you may need to setup grub again, check the file device.map in the grub has the right names.
On a different note: Why not install a modern linux as a host and run the original system in a VM (kvm should be fine).
Good chance is that your original system only had one core and used single core kernel, while a modern CPU definitely is multicore.
Using a single core kernel on a multicore system will degrade it to single core. (if the cpu is sufficiently more modern it should stilll be faster).
kernel ..... root=LABEL=/
the image shows root=LABEL-/
I guess is that this would work out. Don't edit /etc/fstab just yet, it is consistent with the kernel command line.
After booting you may need to setup grub again, check the file device.map in the grub has the right names.
On a different note: Why not install a modern linux as a host and run the original system in a VM (kvm should be fine).
Good chance is that your original system only had one core and used single core kernel, while a modern CPU definitely is multicore.
Using a single core kernel on a multicore system will degrade it to single core. (if the cpu is sufficiently more modern it should stilll be faster).
Your root partition most probably is the /dev/sda3 partition.
Use a livecd and mount /dev/sda3 as /mnt
Then look at /mnt/etc/fstab to see what you have there.
Does / corresponds to /dev/sda3 or it uses a different reference? It might use a label, UUID to / but that UUID is not the same on the restored partition as it was on the original system.
/dev/sda3 ext3 /. .....
Label= Ext3 /. .....
Do not delete entries, comment them out (# in the first column of the line) so that you can have/maintain the references.
Grub points to the bootable partition which seems to work.
Then look at /mnt/etc/fstab to see what you have there.
Does / corresponds to /dev/sda3 or it uses a different reference? It might use a label, UUID to / but that UUID is not the same on the restored partition as it was on the original system.
/dev/sda3 ext3 /. .....
Label= Ext3 /. .....
Do not delete entries, comment them out (# in the first column of the line) so that you can have/maintain the references.
Grub points to the bootable partition which seems to work.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
HI
See attached error after changing fstab file , still no luck with the boot
other hand i used VmWare Workstation and created a machine and restore the file to it, and its working. so the image i have from old pc is good
Also i notice while booting up they run thru many things one of those are
ide: Assuming 33MHz system bus speed for PI0 modes; override with idebus=xx
hda= C/H/S=0/0/0 from BIOS ignored
hdc= C/H/S=0/0/0 from BIOS ignored
(Above is from new PC)
Where, in VmWare Machine its says as below
ide: Assuming 33MHz system buz speed for PI0 modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x10c0-0x10c7, BIOS settings: hda: DMA, hdb:pio
ide1: BM-DMA at 0x10c8-0x10cf, BIOS settings: hdc:DMA, hdd:pio
hda: Vmware Virtual IDE Hard Drive, ATA DISK Drive
blk: queue c050bd40, I/O limit 4095mb (mask 0xffffffff)
hdc: Vmware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM Drive
See if this helps you to diagnose the issue and help me in good direction
After-FSTAB-Change.jpg
IMG_20160421_142559.png
IMG_20160421_143148.png
See attached error after changing fstab file , still no luck with the boot
other hand i used VmWare Workstation and created a machine and restore the file to it, and its working. so the image i have from old pc is good
Also i notice while booting up they run thru many things one of those are
ide: Assuming 33MHz system bus speed for PI0 modes; override with idebus=xx
hda= C/H/S=0/0/0 from BIOS ignored
hdc= C/H/S=0/0/0 from BIOS ignored
(Above is from new PC)
Where, in VmWare Machine its says as below
ide: Assuming 33MHz system buz speed for PI0 modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x10c0-0x10c7, BIOS settings: hda: DMA, hdb:pio
ide1: BM-DMA at 0x10c8-0x10cf, BIOS settings: hdc:DMA, hdd:pio
hda: Vmware Virtual IDE Hard Drive, ATA DISK Drive
blk: queue c050bd40, I/O limit 4095mb (mask 0xffffffff)
hdc: Vmware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM Drive
See if this helps you to diagnose the issue and help me in good direction
After-FSTAB-Change.jpg
IMG_20160421_142559.png
IMG_20160421_143148.png
The entry reports the drive as hda not sda,
You posted everything accept vfstab.
Try modifying vfstab transitioning/duplicating existing entries pointing to /dev/sda to reflect in the active line /dev/hda
The grub reference uses hd(0,1) so it is not impacted what the disk/partition label is.
You posted everything accept vfstab.
Try modifying vfstab transitioning/duplicating existing entries pointing to /dev/sda to reflect in the active line /dev/hda
The grub reference uses hd(0,1) so it is not impacted what the disk/partition label is.
ASKER
Hi Arnold
We do not have vfstab file on the system, if you mean by fstab then its is posted in my first post, also changing that to hda3 it did not help, same error
We do not have vfstab file on the system, if you mean by fstab then its is posted in my first post, also changing that to hda3 it did not help, same error
all errors shown until now have little to do with /etc/fstab! It is not reachable at that stage... (Driverloading is done from the initrd image).
The errors refer to the kernel commandline root= parameter.
grub determines the (hd*,*) values from a file [/boot]/grub/device.map
grub config file tells the kernel what to use...
Depending on the kernel ide devices are /dev/hda (older) or /dev/sda (recent) kernels.
The failures of the mpt_* symbols seem to indicate that the driver in your initrd image does not match the kernel you use, OR there is an error before that about something missing or so which prevented a driver from loading. The first error is needed.
You can experiment with the command line but the FIRST photo shows that the command line entered had
root=LABEL-/ which makes little sense. As that should have been root=LABEL=/
(note the - / = issue). It says later the device LABEL-/ is not found.. which is a correct errormessage.
to look for labels one needs a root=LABEL=<label> where in this case <label> = /
same in /etc/fstab, this also makes the configuration agnostic of what the actual devicename is.
Before tearing everything apart, can you try with the actual commandline like it is in the grub config file?
Also the initrd will need the right ide driver. (the mptscsi.ko driver might be the one needed for you previous raid array).
The errors refer to the kernel commandline root= parameter.
grub determines the (hd*,*) values from a file [/boot]/grub/device.map
grub config file tells the kernel what to use...
Depending on the kernel ide devices are /dev/hda (older) or /dev/sda (recent) kernels.
The failures of the mpt_* symbols seem to indicate that the driver in your initrd image does not match the kernel you use, OR there is an error before that about something missing or so which prevented a driver from loading. The first error is needed.
You can experiment with the command line but the FIRST photo shows that the command line entered had
root=LABEL-/ which makes little sense. As that should have been root=LABEL=/
(note the - / = issue). It says later the device LABEL-/ is not found.. which is a correct errormessage.
to look for labels one needs a root=LABEL=<label> where in this case <label> = /
same in /etc/fstab, this also makes the configuration agnostic of what the actual devicename is.
Before tearing everything apart, can you try with the actual commandline like it is in the grub config file?
Also the initrd will need the right ide driver. (the mptscsi.ko driver might be the one needed for you previous raid array).
What is "really old linux"? Distribution? Version?
Essentially you need to add driver for new disk while at old system into initrd
dometimes it is mkinitrd sometimes dracut, sometimes mix of both and config files in weirdest locations.
Essentially you need to add driver for new disk while at old system into initrd
dometimes it is mkinitrd sometimes dracut, sometimes mix of both and config files in weirdest locations.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
3) change it to vi /a/etc/fstab
ASKER
Hi
As I said, I am completely new to this Linux, I can get the screen shot which you can see and then let me know the steps,
the command suggested are incomplete, they came up with the help option and I could not progress further,
When I use option hda1 or 3 I get different error the option LEBEL,
I also can not see anywhere LEBEL-/ , all I see is LEBEL=/
Regarding the Linux version is as below output
uname -a
-----------------------
Linux ####### 2.4.21-32.ELsmp £1 SMP Fri Apr 15 21:17:59 EDT 2005 i686 i686
i386 GNU/Linux
#### was the computer name
cat /proc/version
-----------------------
Linux version 2.4.21-32.ELsmp (bhcompile@tweety.build.re dhat.com) (gcc version 3
.2.3 20030502 (Red Hat Linux 3.2.3-52)) £1 SMP Fri Apr 15 21:17:59 EDT 2005
cat /etc/*release
-----------------------
LSB_VERSION="1.3"
Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
lsb_release -a
-----------------------
Description: Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
Release: 3
Codename: TaroonUpdate5
As I said, I am completely new to this Linux, I can get the screen shot which you can see and then let me know the steps,
the command suggested are incomplete, they came up with the help option and I could not progress further,
When I use option hda1 or 3 I get different error the option LEBEL,
I also can not see anywhere LEBEL-/ , all I see is LEBEL=/
Regarding the Linux version is as below output
uname -a
-----------------------
Linux ####### 2.4.21-32.ELsmp £1 SMP Fri Apr 15 21:17:59 EDT 2005 i686 i686
i386 GNU/Linux
#### was the computer name
cat /proc/version
-----------------------
Linux version 2.4.21-32.ELsmp (bhcompile@tweety.build.re
.2.3 20030502 (Red Hat Linux 3.2.3-52)) £1 SMP Fri Apr 15 21:17:59 EDT 2005
cat /etc/*release
-----------------------
LSB_VERSION="1.3"
Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
lsb_release -a
-----------------------
Description: Red Hat Enterprise Linux ES release 3 (Taroon Update 5)
Release: 3
Codename: TaroonUpdate5
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This image shows: IMG_20160420_092802.jpg
root=LABEL-/
which is wrong, And it also starts your question, first photo on my list top post.
LEBEL != LABEL as in your latest remark.
Correct spelling would be: (as is in the screenshot from grub) root=LABEL=/
(equal sign not dash)
root=LABEL-/
which is wrong, And it also starts your question, first photo on my list top post.
LEBEL != LABEL as in your latest remark.
Correct spelling would be: (as is in the screenshot from grub) root=LABEL=/
(equal sign not dash)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi All
Thank you very much for all your help, currently we can use the same system thru VmWare workstation.
We can not setup new linux server and copy files and applications to new server, reason the application we are running is very old dacl system and not sure where to get this now a day
once again , thank you every one
Thank you very much for all your help, currently we can use the same system thru VmWare workstation.
We can not setup new linux server and copy files and applications to new server, reason the application we are running is very old dacl system and not sure where to get this now a day
once again , thank you every one
Just verify rpm integrity
You quickly get files changed on top of that....
Should not be killing to just copy them over to modern system.
You quickly get files changed on top of that....
Should not be killing to just copy them over to modern system.
You need to relabel the root filesystem, please see the details here:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/sec-sel-fsrelabel.html