Re: Re: [SLE] [LILO,HD] BIG BIG EMERGENCY!
Do you actually have the hard drive attached as master drive in your first IDE channel (hda)?
Is the device file /dev/hda correct?
brw-rw---- 1 root disk 3, 0 May 21 08:21 /dev/hda
Did you try "gpart" yet?
I wouldn't recommend using that personally...in my experience it causes more problems than it solves (thank you N-curses :-)
Have you tried the rescue system from the first suse CD? It should be enough to boot your computer and examine the hard drive. Post the contents of /proc/partitions, post the output of "dmesg".
-- To unsubscribe send e-mail to suse-linux-e- unsubscribe@suse.com For additional commands send e-mail to suse-linux-e- help@suse.com Also check the FAQ at http://www.suse.com/support/faq and
dmesg &> $HOME/dmesg_output.txt && exec unix2dos $HOME/dmesg_output.txt should do the trick, but I fail to see how this helps, since dmesg mearly reports output from the "kernel ring" buffer, and will not give specifics on HDD failures. My advice would be to check "/var/log/messages" --Thomas Adam the
archives at http://lists.suse.com
Thomas Adam
"The Linux Weekend Mechanic" --
THOMAS ADAM schrieb:
Do you actually have the hard drive attached as master drive in your first IDE channel (hda)?
Is the device file /dev/hda correct?
brw-rw---- 1 root disk 3, 0 May 21 08:21 /dev/hda
Did you try "gpart" yet?
I wouldn't recommend using that personally...in my experience it causes more problems than it solves (thank you N-curses :-)
Have you tried the rescue system from the first suse CD? It should be enough to boot your computer and examine the hard drive. Post the contents of /proc/partitions, post the output of "dmesg".
dmesg &> $HOME/dmesg_output.txt && exec unix2dos $HOME/dmesg_output.txt
should do the trick, but I fail to see how this helps, since dmesg mearly reports output from the "kernel ring" buffer, and will not give specifics on HDD failures.
My advice would be to check "/var/log/messages"
--Thomas Adam
well all those advises are nothing since i told and wrote: i cannot access the whole partition. not read, not write not boot so i cannot test that. only thing i have been able to give you in the very first mail which I resend now is detailed error descriptions -- *º¤., ¸¸,.¤º*¨¨¨*¤ =Oliver@home= *º¤., ¸¸,.¤º*¨¨*¤ I http://www.bmw-roadster.de/Friends/Olli/olli.html I I http://www.bmw-roadster.de/Friends/friends.html I I http://groups.yahoo.com/group/VGAP-93 I I http://home.t-online.de/home/spacecraft.portal I
Telek0ma iBBMS - soon back online +49.4503.TRSi1/TRSi2 <<<
* Oliver Ob
THOMAS ADAM schrieb:
well all those advises are nothing since i told and wrote:
i cannot access the whole partition. not read, not write not boot so i cannot test that.
Yes, but please read what people suggested. can you boot of the rescue CD (that is, not booting of the DISK, but of the rescue CD) insert CD in drive, boot from CD now try if *FROM THAT CD* dmesg will list a /dev/hda &c &c ... Even so, it sounds like your harddisk died on you and you're SOL. But having said all that, could you please try to *BOOT OFF THE CD* ? I use the suse recue CDs for all kinds of hardware tricks (I've amnaged to get windows boxes booting again after booting from the rescue CD and fiddling around on the windows partitions .. I've mirrored windows disks by booting of the rescue CD and dd-ing disks. Rescue CD rules dood ;) [the books coming with Suse have a detailed bit about booting of the rescue CD, but the basic principle is 1) insert CD (suse CD 2 in 7.2 if I remember correctly, it was disk 1 in 6.4) 2) boot rescue system Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\<, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
Can you see the disk in BIOS setup ? -- Elton Machado info@ideiasdigitais.co.pt http://www.ideiasdigitais.co.pt PGP KEY # 69EBD43A Portugal *** O tempo pode ser o teu melhor amigo. Se tiveres tempo para o saberes. *** Powered by SuSE Linux 7.2 Professional Registered Linux On Monday, 1 de October de 2001 19:20, Oliver Ob wrote: # THOMAS ADAM schrieb: # > # > > Do you actually have the hard drive attached as master # > drive in your first # > > IDE channel (hda)? # > > # > > Is the device file /dev/hda correct? # > > # > > brw-rw---- 1 root disk 3, 0 May 21 # > 08:21 /dev/hda # > > # > > Did you try "gpart" yet? # > # > I wouldn't recommend using that personally...in my # > experience it causes more problems than it solves (thank # > you N-curses :-) # > # > > Have you tried the rescue system from the first suse CD? # > It should be # > > enough to boot your computer and examine the hard drive. # > Post the contents # > > of /proc/partitions, post the output of "dmesg". # > # > dmesg &> $HOME/dmesg_output.txt && exec unix2dos # > $HOME/dmesg_output.txt # > # > should do the trick, but I fail to see how this helps, # > since dmesg mearly reports output from the "kernel ring" # > buffer, and will not give specifics on HDD failures. # > # > My advice would be to check "/var/log/messages" # > # > --Thomas Adam # > # well all those advises are nothing since i told and wrote: # # i cannot access the whole partition. # not read, not write not boot # so i cannot test that. # # only thing i have been able to give you in the very first # mail which I resend now is detailed error descriptions
Elton Machado schrieb:
Can you see the disk in BIOS setup ?
Yes BIOS detects it properly! All CHS/LBA data is detected. -- *º¤., ¸¸,.¤º*¨¨¨*¤ =Oliver@home= *º¤., ¸¸,.¤º*¨¨*¤ I http://www.bmw-roadster.de/Friends/Olli/olli.html I I http://www.bmw-roadster.de/Friends/friends.html I I http://groups.yahoo.com/group/VGAP-93 I I http://home.t-online.de/home/spacecraft.portal I
Telek0ma iBBMS - soon back online +49.4503.TRSi1/TRSi2 <<<
participants (4)
-
Elton Machado -
Gerhard den Hollander -
Oliver Ob -
THOMAS ADAM