[Post-Install] Broken disk?

[nilsA]

On one of tree old PCs, after a week or so, the install is broken.

It boots into:

GNU GRUB version 2.14
Minimal BASH-like line editing is supported
...
...''

grub>

When I do

ls

I get

(hd0) (HD0,mscos|) (HD0,msdos2) (HD0, msds3) (hd0, mosdos4)

But when I do

ls (msdos0)

I get

Device hd0: No known filesystem detected - sector size 512B - Total size 488386584KiB

And the PC will not boot from CD or USB, whatever I do in the BIOS.

Is the disk bad? OR can I rescue this?

[oshunluvr]

You have to supply the entire path and there is no "msdos0". Only (msdos1), 2, 3, etc.

So not "ls (msdos0), but "ls (hd0,msdos1)"

[die.boer]

Not necessarily a bad disk. The fact that GRUB can still see the drive and its partitions is actually a good sign.

A few observations: 1. The partition names are probably not what you're typing


Your ls output should be something like:(hd0) (hd0,msdos1) (hd0,msdos2) (hd0,msdos3) (hd0,msdos4) , like oshunluvr said.
GRUB partition numbering starts at 1, not 0.

try :

ls (hd0,msdos1)/

ls (hd0,msdos2)/

ls (hd0,msdos3)/

ls (hd0,msdos4)/

One of them may show directories such as:
boot/
etc/
home/
or
vmlinuz
initrd.img
If so, the filesystem is still readable.
next: Check whether GRUB can find Linux

search.file /boot/grub/grub.cfg

or

search.file /grub/grub.cfg

If it returns a partition, note it.

then

set root=(hd0,msdosX)

configfile /boot/grub/grub.cfg

(replace X with the partition found)
If GRUB loads the menu, your installation may be completely intact and only the bootloader configuration is damaged.

If every partition says "unknown filesystem" for all partitions, then possibilities include:
Corrupted partition table
Corrupted filesystem
Failing hard drive
Loose SATA cable (surprisingly common on old PCs)

At that point I would strongly suspect disk trouble.

---

[nilsA]

You have to supply the entire path and there is no "msdos0". Only (msdos1), 2, 3, etc.

So not "ls (msdos0), but "ls (hd0,msdos1)"

Sorry, typo - it should read:

ls (hd90)

[nilsA]

Not necessarily a bad disk. The fact that GRUB can still see the drive and its partitions is actually a good sign.

A few observations: 1. The partition names are probably not what you're typing


Your ls output should be something like:(hd0) (hd0,msdos1) (hd0,msdos2) (hd0,msdos3) (hd0,msdos4) , like oshunluvr said.
GRUB partition numbering starts at 1, not 0.

try :

ls (hd0,msdos1)/

ls (hd0,msdos2)/

ls (hd0,msdos3)/

ls (hd0,msdos4)/

One of them may show directories such as:
boot/
etc/
home/
or
vmlinuz
initrd.img [/QUOTE)

The same files, including /boot, / /home /etc are all partitions.

(QUOTE)

If so, the filesystem is still readable.
next: Check whether GRUB can find Linux

search.file /boot/grub/grub.cfg

or

search.file /grub/grub.cfg

If it returns a partition, note it.

then

This does not find anything.

[die.boer]

This does not find anything.

what command/s exactly doesn't find anything?

[oshunluvr]

Sorry, typo - it should read:

ls (hd90)

That would be appropriate if you have 91 drives attached. Seems unlikely.

Devices (drives) are numbered from 0 and up and labeled with hd. The first disk is hd0, the second hd1, and so on.

Partitions are numbered from 1 and up and labeled with the partition type - either msdos or gpt.

With your typos corrected you have: (hd0) (hd0,msdos1) (hd0,msdos2) (hd0, msdos3) (hd0, msdos4)

So the first drive has 4 msdos type partitions. It's likely that the first partition is where your install is located. If so, ls (hd0,msdos1)/boot should reveal the files needed to boot - vmlinuz and initrd.img

Assuming the above is correct, search the internet for Booting from GRUB rescue and follow the directions.

Fair warning; grub rescue mode will not tolerate or correct even the smallest of typos. You must type each entry precisely or it will not work and you have to start over.

Assuming you eventually get it to boot, you must re-install GRUB and update it before rebooting or shutting down, or you will be right back where you started.

[nilsA]

what command/s exactly doesn't find anything?

This (and for the next 3 up to msdos4.)

ls (hd0,msdos1)/