Thanks Jim, for the only reply that is relevant I did try this option without success. The boot partition is hda and the bootloader option showed this partition as correct. What I need are 2 things. 1. How do I dismount all the drives to run fsck at Xterm? 2. How do I use fdisk to re-write MBR from xterm? The second one might be difficult as there is plently of info on re-creating a LiLO MBR but not GRUB on the internet Yes I have run other utils off the CD1 menu, some work and yet some indicate 1 error with 1 file (smpt?) from memory but can not repair it. I chose the option to recover lost files and the NTFS partitions were re-created - I have formatted ALL HDD 4-6 times since I ever had an NTFS partition!!!!!!!!!!!?????????? I have check the the bootloader file and all is in order via YAST. I am running clamAV with freshclam at the moment from xterm as the GUI is all stuffed up with an error "unable to parse option" just in case. Background - The unit is my F/S ( I have backups) it has been running for over 18month non stop without issue. The error started when I suspended the unit to HDD after that the MBR was screwed. I have tried all 3 disks to hold the MBR and I cannot believe all HDD have faulty track 0 cylinder 1 all physically damaged. Scott Jim Flanagan wrote:

Registration Account wrote:

...

I have 3 HDD in my PC. No matter which Disk I partition to be the boot drive via the GUI Partitioner, I cannot boot the PC from HDD. I am sure the MBR is corrupted - I am using GRUB with NO NTFS Partitions. I cannot find many clear directions on how to re-write the MBR. Can some one please help me with a few clear directions on how to correct this - Perhaps after replying to me you might like to consider writing a SDB page on this as there is little info on this Thanks Scott

Boot from your opensuse install disk. Select 'installation' (you will not do a complete install). Select your language, accept license. At that point select 'other options>repair installed system'. Then select 'expert options', then 'install new boot loader'. That should do it.

Jim

On 8/3/07, Registration Account wrote:

Sorry I forgot to mention I am using ex2 File system and I have 1 RAID0 containing 3 partitions

sorry for not advising you before.

Scott

So, is this software or hw raid? -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 8/4/07, Registration Account wrote:

Software

What exactly is the layout of your partitions (on every drive, and on the RAID volume as well)? Are the root and boot partitions on the RAID volume? Please provide the output from fdisk -l for every drive, as well as copy of your fstab. Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I have successfully installed 10.2. I thought I would explain what the problem was and how it was fixed. Firstly I need to go over the IDE hardware setup. There are 2 IDS BUS connectors. The first has 2 LBA IDE HDD, however the disk at the end of the ribbon is hardware configured as the slave and the master is hardware configured between the two ends of the ribbon. The second IDE connector had the CD hardware configured at the end of the ribbon and another LBA HDD hardware configured as a slave between the two ends of the ribbon. The other complexity, whilst not causing a problem, is interesting as the system BIOS has a specification for which HDD are the first, second, third and fourth devices (NOTHING TO DO WITH BOOT ORDER) As All HDD are the same model and capacity the 1st Master HDD was positioned as the second device which is correct in so far as its physical location on the cable. The settings for the Boot preference priority was set to CD/HDD/FDD which is true and correct as despite a bootable image being loaded in the CD and the CD nominated at the 1st priority; if the BIOS recognises that the current CD media is bootable it ALWAYS asked "hit any key to boot from CD". If media is present in the CD and there is no bootable image and despite the priority being set as above; no question is asked of the user. Therefore I partitioned the second HDD, which was in fact the 1MHDD with a root mount point and gate it 20GB formatted with ex3. I created a second partition with a home mount point formatted with ex3 and a swap partition formatted as such. I created and formatted a swap partition of 1SHDD and 2MHDD. System installed and up and running. (This is an overhang that came from the first PC which had only 1 FDD - one was A and the other B. The A drive ALWAYS had the O/S the B the DATA. The convention that no matter logically where drives are the only drive which will boot is the First device and it matter not what size (in the case of floppies) or placement on the ribbon. How I discovered the wrong physical location of the 1MHDD was to install Windoze XP - Its install program formatted and copied files to the 1MHDD despite me setting fdisk to format 1SHDD as drive C. That lead me to think the same "1st Drive" concept in DOS and Windows applied to Linux and there is logic behind this. One day I will physically move the 1MHDD to the end of the ribbon and the 1SHDD to the middle. Lesson for me - even the teko shop sometimes gets things wrong when putting in new HDD. Thanks to all who have offered their suggestions to help Scott Jerry Feldman wrote:

On Sat, 04 Aug 2007 11:52:34 +1000 Registration Account wrote:

...

What I need are 2 things.

1. How do I dismount all the drives to run fsck at Xterm?

2. How do I use fdisk to re-write MBR from xterm?

The second one might be difficult as there is plently of info on re-creating a LiLO MBR but not GRUB on the internet

The best way is to boot a rescue or disk or live CD, but... Another way is to shutdown to single user mode. This should unmount all but the root file system. You can always do a umount -a.

Make sure root is mounted read-only. (If I recall, in SuSE when shutting down to single-user, it mounts read-only, but Fedora did not. So, what I do is try to write to root, and if it fails I'm read-only.

The command to mount root readonly is: mount -o remount,ro /

At this point you can run fsck. I generally run fsck on a single partition at a time in this mode, but you can also run multiples.

Probably the simplest way to fix the MBR is to go to YaST/System/Boot Loader. Stepping through this, should cause the MBR to be rebuilt. Another way is to use the grub(8) command. Check the grub info page: info grub There is a section "3.2 Installing GRUB natively" This will also rewrite the MBR.