On Thursday 23 September 2010 23:04:05 you wrote:
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.
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.
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
At this point in the thread, as I understand it, the source of the problem was thought to be in either GRUB or hardware. Since there is a GRUB on each of the two HDs, the latter seems more probable to me. Now I have a reply from DFSee, containing the following:
The GRUB info on that bootsector looks OK to me: +++++++++++++ Bootsector format : GRUB, GRand Unified Bootloader, stage1 code PC style BPB info : not present GRUB stageX @PSN : 0x01293010 Located on : /dev/hda6 /boot/grub PID: 03 StageX segm:addr : 0800:8000 Forcing LBA : Yes Stage1 install by : 3.2 Boot Disk # : 0xff = disknr : 1 StageX install by : 3.2 LoadSegment : 0x0820 = stage 2 code GRUB code version : 0.97 Code size : 0x0000005F = 47.5 KiB GRUB Config file : /boot/grub/menu.lst +++++++++++++
The GRUB code for disk 2 looks good too: +++++++++++++ Bootsector format : GRUB, GRand Unified Bootloader, stage1 code PC style BPB info : not present GRUB stageX @PSN : 0x02142630 Located on : /dev/hdb6 /boot/grub PID: 09 StageX segm:addr : 0800:8000 Forcing LBA : Yes Stage1 install by : 3.2 Boot Disk # : 0xff = disknr : 2 StageX install by : 3.2 LoadSegment : 0x0820 = stage 2 code GRUB code version : 0.97 Code size : 0x000000C7 = 99.5 KiB GRUB Config file : /boot/grub/menu.lst +++++++++++++
I have to wonder why the size of the little GRUB code on one drive is twice as large as on the other one. That seems to narrow things down to hardware. And seems also to leave me no choice but to replace the MB. I only hope that I can salvage the data from the 11.1 installation. For the new replacement sysem, I am seriously considering sticking with v11.1; I don't really care if people call me an old fogy. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org