lost grub...

Things were fine with the computer until we accidentally booted the
system with the root drive disconnected. Now the system does not boot.
It does not even load grub. It does not say OS not found. When I select
the option to boot from the hard drive (the install CD boots just fine)
I get a blank black screen. No error message, nothing. Here is a copy of
the fdisk -l.

Rescue:~ # fdisk -l

Disk /dev/sda: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003d28f

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap /
Solaris
/dev/sda2 * 263 1568 10490445 83 Linux
/dev/sda3 1569 8924 59087070 83 Linux

Disk /dev/sdb: 300.0 GB, 300000000000 bytes
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000856dc

Device Boot Start End Blocks Id System
/dev/sdb1 1 36472 292961308+ 83 Linux

Disk /dev/sdc: 300.0 GB, 300000000000 bytes
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009c218

Device Boot Start End Blocks Id System
/dev/sdc1 1 36472 292961308+ 83 Linux
Rescue:~ #

I look at it and the correct partition is marked to boot /dev/sda2. No
other partitions are active on any of the other drives.

during install, did you place grub in the MBR?
which operating system have you installed, exactly.

and, thanks for posting the same problem in a new thread (which i did
not see until AFTER i had typed out a long note into the old one)…


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio

DenverD wrote:
> during install, did you place grub in the MBR?
> which operating system have you installed, exactly.
>
> and, thanks for posting the same problem in a new thread (which i did
> not see until AFTER i had typed out a long note into the old one)…
>

Sorry about the repost but I realized that the situation was a little
different than people understood. I did read your long post. Thank you. :slight_smile:

What I saw (after I was able to get the remote KVM online for just a few
minutes) when I looked at the bios seems to disagree with the fdisk -l.
What I mean is the boot sequence of the bios give the option of booting
only one SAS drive. There are four of them. It seems that the drive
Linux picks as /dev/sda is not the same as the bios picks as its boot
drive. The techs are just getting up where that system is located and I
hope to have one try moving around the SAS data cables to see if that
shows a different boot drive in the bios.

The problem is possibly a confusion about which SAS drive is to boot.
The system was loaded with OpenSuse 10.3 (as is the current company policy).

Booting computers was easier when we toggled in the boot program but
they are a little fast now. :slight_smile:

DenverD wrote:
> during install, did you place grub in the MBR?
> which operating system have you installed, exactly.
>
> and, thanks for posting the same problem in a new thread (which i did
> not see until AFTER i had typed out a long note into the old one)…
>
A more formal answer to the question which Suse is the uname:

Linux migmar14 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC x86_64
x86_64 x86_64 GNU/Linux

I got that from one of the other two servers sitting next to the one
with the problem. This machine had an almost identical problem
yesterday. It had been running just fine for over a year. Then we tried
to add three additional SAS drives and remove one smaller SAS drive.
Adding the drive was no problem. Then when we removed the small SAS
drive it gave us the same problem, a blank black screen and not grub.
That machine was a in production so I had no choice but to quickly
reload the system. Which messed up the production department.

The current problem machine is not yet in production so I have a chance
to play with it. I would like to figure out what is the source of the
problem in case it happens again. Fixing the problem might be quite
simple and much quicker than a reload once I figure out the source of
the problem.

Ted

Ted Miglautsch wrote:
> Linux migmar14 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC
x86_64
> x86_64 x86_64 GNU/Linux

no, that is not what i asked for…but, you gave what i asked for in
another post: “OpenSuse 10.3 (as is the current company policy)”

and i can advise that personally i hope those machines are not
exposed to the internet or users with a grudge, because (unless you
are doing a lot of keeping up) they have not had a security patch
applied since last october when this community stopped supporting 10.3…

The following distributions have reached their end of life and should
not be used anymore: openSUSE 10.3 - October 31st 2009 (done)
cite: http://en.opensuse.org/SUSE_Linux_Lifetime

openSUSE releases have a nominal life of about 1.5 years, if you need
a longer life system you need to look around some…or, commit to a
fresh install about every year…

11.3 release is just around the corner…but a lot of commercial folks
with more to do that replace OSes every year use SUSE Enterprise Linux
Server, or Red Hat, or CentOS, or Debian or or or

ymmv

DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio

I suspected the BIOS in the other thread. Can you change the boot order in the BIOS back to the proper order. This should be able to be done with out changing the wiring which may confuse things even more.

And what DenverD has said is right. 10.3 is no longer supported. OpenSuse is a fast moving development edition. If you want stability you need to use the commercial Novell version.

DenverD wrote:
> Ted Miglautsch wrote:
> > Linux migmar14 2.6.22.5-31-default #1 SMP 2007/09/21 22:29:00 UTC
> x86_64
>> x86_64 x86_64 GNU/Linux
>
> no, that is not what i asked for…but, you gave what i asked for in
> another post: “OpenSuse 10.3 (as is the current company policy)”
>
> and i can advise that personally i hope those machines are not
> exposed to the internet or users with a grudge, because (unless you
> are doing a lot of keeping up) they have not had a security patch
> applied since last october when this community stopped supporting 10.3…
>
> The following distributions have reached their end of life and should
> not be used anymore: openSUSE 10.3 - October 31st 2009 (done)
> cite: http://en.opensuse.org/SUSE_Linux_Lifetime
>
> openSUSE releases have a nominal life of about 1.5 years, if you need
> a longer life system you need to look around some…or, commit to a
> fresh install about every year…
>
> 11.3 release is just around the corner…but a lot of commercial folks
> with more to do that replace OSes every year use SUSE Enterprise Linux
> Server, or Red Hat, or CentOS, or Debian or or or
>
> ymmv
All those machines have such bad security that the passwords usually
match the user name. Talk about easy to hack. :slight_smile: However, you would
need to go through several firewalls to get to them from the Internet or
use a key to the door. Do not worry about their security.

Though I wish you people would stop removing the existing repositories
for older versions. You tell me that it is because of space. That is a
joke. The older version repositories are not that large and disk space
is rather cheap. For us stable running databases are the most important.
Once we get a stable configuration we cannot be changing our machines
every week with new upgrades. We still have some computers running
software 10 years old. It works and is much faster that the current
bloated versions.

gogalthorp wrote:
> I suspected the BIOS in the other thread. Can you change the boot order
> in the BIOS back to the proper order. This should be able to be done
> with out changing the wiring which may confuse things even more.
>
> And what DenverD has said is right. 10.3 is no longer supported.
> OpenSuse is a fast moving development edition. If you want stability you
> need to use the commercial Novell version.
>
>

By the way, I did fix find a solution to the boot problem. I reset the
bios and also only allowed the DVD to boot. The DVD was then able to
find the correct drive. Then I again allowed the hard drive to boot if
the DVD boot failed and it continues to boot fine.

I found the Novell version less stable if you do not have their support
contract. After a very bad experience with red hat many years ago I
stopped using any OS that requires a support contract.

Hi
I have SLES and SLED running here fine, I only get the updates, no
support contract involved…

The files for older versions are still available, just only on a few
mirrors;
http://en.opensuse.org/Mirror_Selection#Discontinued_releases_mirrors


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.12-0.7-default
up 6 days 14:16, 2 users, load average: 0.32, 0.32, 0.32
GPU GeForce 8600 GTS Silent - Driver Version: 195.36.31

The point is that there is no more fixes for 10.3 if a serious hole is found though it is now your responsibility to fix it if you want it fixed. You can still get to a repository that has the final 10.3 patches. There are just never ever going to be any new ones.

Hi
Correct, the OP was not happy that the repositories with the final
updates and install rpm’s was not available, hence the link to the
mirrors…


Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.12-0.7-default
up 6 days 15:43, 2 users, load average: 0.03, 0.07, 0.08
GPU GeForce 8600 GTS Silent - Driver Version: 256.35

malcolmlewis wrote:
>

> Hi
> Correct, the OP was not happy that the repositories with the final
> updates and install rpm’s was not available, hence the link to the
> mirrors…
>
Thank you (gogalthorp) for the link to the old stuff. We are not worried
about new patches. :slight_smile: Our important servers need almost no security.
They just crunch data (trillions of records) all day and night.

Ted Miglautsch wrote:
> Though I wish you people would stop removing the existing repositories
> for older versions. You tell me that it is because of space. That is a
> joke. The older version repositories are not that large and disk space
> is rather cheap.

heh! when was the last time your company made a contribution to the
openSUSE (or any open source) Community to buy some cheap disk space
and keep it spinning??

actually, almost all of our mirrors are not on anything we own, but
instead is donated space…and, why should a university near you want
to keep repos of 10.3, 10.2, 10.0, 9.3 etc etc they KNOW are no longer
supported, are UNPATCHED and the distributors (us) say don’t use it!

now, here is another way to look at it: since disk space is so cheap
how come you don’t have a company owned disk spinning with the entire
10.3 code base…i mean, “older version repositories are not that
large” so make yourself a mirror of unpatched stuff and run it…

> For us stable running databases are the most important.
> Once we get a stable configuration we cannot be changing our machines
> every week with new upgrades. We still have some computers running
> software 10 years old. It works and is much faster that the current
> bloated versions.

i do not disagree, not at all…in fact, i’m running 10.3 on this
machine, but that is my business and i’ll not recommend you or anyone
else do likewise…


DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio