RH server reboot stop at Non-System disk or disk error

[Gary L]

Hi

One of my physcial (DL380G3) server (RHES4U4) its file system became "read-only" today, I could not do vi-wq and touch etc write comands. So, I reboot it. But the system stop at Non-System disk or disk error, details are as follows:

reboot the system via iLO interface, system try to "Attempting Boot From CD-ROM", "Attempting Boot From Hard Drive (c:)" , "Attempting Boot From NIC", Nothing happend. System detect MAC address and went to "Non-System disk or disk error, replace and strike any key when ready" error message. It didn't ran the GRUB kernel, PV VG detect.

I could go into the rescue mode, could connect the network. df -h, pvscan, vgscan, lvscan are all ok. Done the "fsck", but it still doesn't work.

How to fix this problem. If disk physical damage, I think I could not see the system in rescue mode.

Any answers will be very appreciate.

BTW:
For heal the crash system, could someone list some commands that could be used in rescue mode. You know, I only know: fsck, badblocks and backup the data.

Merry Christmas.

[Steven E. Protter · Accepted solution]

Shalom,

Happy Holidays.

Your system disk is no longer bootable.

To fix that I have the following suggestions:

use grub in rescue mode to try and re-establish boot capabilities.

This procedure covers two disk mirroing but provides the basics.



1. boot redhat cd 1
2. enter "linux rescue" at isolinux prompt
3. no networking, mount drives
4. at shell prompt, type "grub"
5. find /grub/stage1
6. root (hd0,0)
7. setup (hd0)
8. root (hd1,0)
9. root (hd1)
10. klingon deathgrip

Otherwise back up data and configuration and reinstall the OS.

SEP

[skt_skt]

Try following from rescue mode to confirm if any LVM disks are getting detected.

#lvmdiskscan
#vgchange -ay

[Gary L]

Hi SEP and Santhosh

Thank you very much for your help and good suggestions.

I will follow your steps to rebulid the boot capability and confirm the LVM disks.

Merry Christmas everybody

[Gary L]

Hi SEP

I met some problems when I tried rebuild boot capacity according as your steps:
1. boot -- ok
2. linux rescue mode -- ok
3. no networking
chroot /mnt/sysimage
df -h -- ok, all the mount points were mounted, inlcude /
4. grub -- ok, GNU GRUB version 0.95
5. find /grub/stage1
(hd1,0)
6. root (hd0,0)
Error 5: Partition table invalid or corrupt
7. setup (hd0)
Error 12: Invalid device requested
8. root (hd1,0)
Filesystem type is ext2fs, partition type 0x83
setup (hd1)
Checking if "/boot/grub/stage1" exists ...no
Checking if "/grub/stage1" exists...yes
Checking if "/grub/stage2" exists...yes
Checking if "/grub/e2fs_stage1_5" exists...yes
Running "embed /grub/e2fs_stage1_5(hd1)"... 16 sectors are embedded successded
Running "install /grub/stage1 (hd1) (hd1)1+16 p (hd1,))/grub/stage2 /grub/grub.conf" ... succeeded
Done.
9. root(hd1)
Filesystem type unknown, using whole disk
10. klingon deathgrip ?

reboot the system, still the same error message, Non-System disk.. could not boot from HD.

[Gary L]

Hi Santhosh

In rescue mode, I ran the commands vgchange -a y and lvmdiskscan, all the LVM disk, VGs and LVs could be detected, include / root /dev/vg00/lvol00.

-Gary

[Gary L]

Hi SEP

If rebuild boot doesn't work.
I plan to reinstall the OS, question: which file(s) need be backup for system configuration backup, i mean, after I reinstall the OS, done the same partitions, LVMs, and upload backup data to each mount points; restore which files could let the new system totally the same as the old system. whole "/etc" direcotry?

[Gary L]

BTW,
I have tried upgarded the OS from RHES4 upudate 4 to update 6 (OS upgrade could save and protect disk original data), but it doesn't work

-Gary

[skt_skt]

I am not good at the restaging systems.. But you may keep a note of the below..
fstab_hostname_122107
group_hostname_122107
hosts_hostname_122107
exports_hostname_122107
passwd_hostname_122107
shadow_hostname_122107
mount_hostname_122107
df_hostname_122107
swapinfo_hostname_122107
scsi_hostname_122107
oracle_inst_hostname_122107
lspci_hostname_122107
lshw_short_hostname_122107
ifconfig_hostname_122107
fdisk_ERROR_hostname_122107
crontab_hostname_122107
rpm_hostname_122107
netstat_nr_hostname_122107
fdisk_hostname_122107

[Gary L]

Thanks Santhosh

question:

what's the mean of fdisk_ERROR_hostname_122107?
# fdisk command? ERROR option? .... 122107 Date?

How to use your above list?
command + option + date?