On Friday 24 September 2010 00:52:57 Felix Miata wrote:
On 2010/09/23 17:04 (GMT-0400) Stan Goodman composed:
On Thursday 23 September 2010 21:44:29 Felix Miata wrote:
On 2010/09/23 20:20 (GMT+0200) Stan Goodman composed:
But that still seems like the place where things hang. I went through the sequence of grub commands, beginning with root (hd1,5), and through loading the kernel. From there:
grub> initrd /boot/initrd<tab>.img initrd /boot/initrd.img
And it doesn't return to the GRUB promptl
Did you type in ".img"? If so, why?
I typed it in by way of trying to follow your directions in your message received here today at 16:27:29 (10:27 your time if you are on ET). Here
is your model:
grub> initrd /boot/init<tab>.img Possible files are: initrd.img-2.6.12 initrd.img
I understood from this that we were seeking a file with a name of the form "initrd*.img". Looking at your model just above, that is still what it seems to me to be saying quite clearly. Please correct me if I am misinterpreting.
You're trying as if the _model_ I provided was an exact clone of what you need to do. Since I'm not there looking at your screen I can't and didn't do that. I provided a model intended to function only as a model. Rather than interrupting my own work to find an approximation of an exact initrd filename match for 11.3, I chose a simpler and doable selection of a disk two with / on a single digit partition. If your installations' initrds do not end in .img, then you can't expect adding .img yourself could be in any way useful.
It is not easy to determine what your model means to be taken literally. I still do not see what else I could have understood from "initrd<tab>.img". Obvioiusly, the head is literal; there is no indication that the tail isn't also. What I hope we can agree about is that communication in these circumstances is difficult, and that even with both of us doing our best, there will be some failures.
grub> find /boot/initrd.img
grub> find /boot/initrd-2.6.34-12.3-desktop
grub> find /boot/initrd
There is an "initrd" on both disks. Presumably that is the file I need.
Agreed
Try proceeding only with an initrd that Grub found.
Alternatively, or after, try:
grub> initrd (hd1,5)/boot/initrdTAB
to see the initrd(s) that exist on (hd1,5), complete as desired if desired, then
grub> boot
I repeated the same sequence of commands as before, beginning with grub> root (hd1,5) and loading the kernel. Then, after grub> initrd /boot/initrd
Error 16:Inconsistent filesystem structure
Google seems to think you have a hardware problem, not a SUSE problem: http://www.linuxquestions.org/questions/linux-newbie-8/error-16-inconsi stent-filesystem-structure-595748/
His symptoms are a bit different (e.g. I don't have looping), but I will have to check into this. Later today I will examine the logs of both HDs. It's unfortunate that there isn't a list of what the various Error numbers mean, but that seems to be the universal practice. BTW, I have tried these experiments on both drives with the same result, so it would not seem that the drives themselves are at fault, and neither of them is really old. The MB, on the other hand, is long in the tooth (Pentium4) and I had been thinking of replacing it with a G41 chipset and E7500 CPU.
Can't you get anything to boot on any HD? http://www.ultimatebootcd.com/ has an iso with many different troubleshooting utilities. Boot it into the one that matches your brand of HD and see if it thinks your HD is OK. Optionally, get the single purpose test utility from the web site of whatever brand your HD is and run that. e.g. http://pcsupport.about.com/od/toolsofthetrade/tp/tophddiag.htm
I'm sure that live Fedora you tried before has something similar but generic, but I always use ultimatebootcd when trouble like this arises.
Many, many thanks, Felix. I'll get back to you here after I do some of these things. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org