boot sector is lost !

engkemo2002 · 02-23-2014, 02:23 PM

Quote:

Originally Posted by Smokey_justme

. I'm guessing that there we're no errors thrown when you did that, right? If there was one it's important to mention it here.

First, ensure that when installing Suse you select to install GRUB (the bootloader) on the MBR (Master Boot Record).

Thanks Smokey_justme.
In fact, yes I did not got any errors, I got the folloing confirmation :
"
1000+0 records in
1000+0 records out
1024000 bytes(1.0MB) copied. 0.280142 seconds ,3.7MB/s.
"

but, If I install suse10 newly using my CD, how could I be sure that the GRUB is newly installed ? (attached is the CD options snap shot)

engkemo2002 · 02-23-2014, 02:30 PM

Quote:

Originally Posted by Smokey_justme

Btw, I found this: http://nozell.com/blog/2004/05/08/so...oliant-server/
I think it describes your problem..

excellent link !
this corresponds excatly to my hw configurations (HP smart array + Proliant G5)
but in my case I think the boot device should be /dev/cciss/c1d0 ...
have others suggestions ?

Rgds,
engkemo

Smokey_justme · 02-23-2014, 02:31 PM

I'm not sure what the Rescue System does, but if it provides a bash cli with minimal tools, then it's perfect. Start that, mount your partition somewhere (use 'fdisk -l' to find out what that's the name of your partition) and follow the instructions from the link I gave you (this one). Like I said, that blog post describes your problem and provides a solution.

Also, please be careful that whenever you run that dd command from your first post, you will need to reinstall everything, so you can forget that one..

If you fell lost or don't understand something, please feel free to ask.

LE: I did not see your last post when I made this one.. :P

Smokey_justme · 02-23-2014, 02:35 PM

Quote:

Originally Posted by engkemo2002

but in my case I think the boot device should be /dev/cciss/c1d0 ...

Yup, it should.. if you have more than one disk installed, be careful on what's in /boot/grub/device.map and/or further commands..

engkemo2002 · 02-23-2014, 02:52 PM

Quote:

Originally Posted by Smokey_justme

I'm not sure what the Rescue System does, but if it provides a bash cli with minimal tools, then it's perfect. Start that, mount your partition somewhere (use 'fdisk -l' to find out what that's the name of your partition) and follow the instructions from the link I gave you

Yes, Rescue system give ma CLI , but what if I could not find /boot/grub/grub.conf and /boot/grub/grub.conf files... ?

syg00 · 02-23-2014, 04:29 PM

Those instructions are (very) old, and somewhat specific to Redhat - try /boot/grub/menu.lst
The rest of the instructions should be o.k.

sundialsvcs · 02-24-2014, 05:59 PM

Unfortunately, you "went and did something" before asking us first.

At this point, it looks like you obliterated, not only the boot sector, but a large swath of the disk. Of course, if your intent was to "quickly wipe" the drive prior to a clean installation on that drive, this would actually be a pretty reasonable way to go about doing that, because it would wipe the file-management data structures without taking the time to actually zero all of the blocks on the disk.

The only thing that you can reasonably do now is to reformat the drive, then install the operating system (and everything else ...) onto this now-virgin media.