>On Sat, Feb 26, 2005 at 11:55:19PM -0500, Harry Cochran wrote: >> Fourth try to identify error: ...
On Sat, Feb 26, 2005 at 1:12AM -0500, Grant Grundler wrote: >How about reading "palo --help"? I have it pasted on my wall :-). >> SinoHub5:/etc# cat palo.conf >> --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ >> --format-as=2 >> --update-partition=/dev/sda >> SinoHub5:/etc# palo >> palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 >> OK we're doing a format as ext2 >> ipl: addr 16384 size 36864 entry 0x0 >> Warning!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >> Boot loader header version is 3, I only know how >> to handle version 4. It MIGHT work anyway. >Could you replace "--update-partition=" with "--init-partition="? Done. Now palo doesn't give an error. >I'm expecting palo to blow everything on f0 away and build a new >ext2 file system. THen you can: >o mount /dev/sda1 /mnt >o copy /boot/* /mnt >o edit /etc/fstab so /dev/sda1 is mounted on /boot. Done. And it boots 2.6.8-2-32-smp! >If that boots, then: >o unmount /boot No ... umount /boot or umount -f /boot comes back with: "device is busy" >o rm /boot/* >o mount /boot Is there a problem leaving the redundant /boot on sda3? >As you might guess, the order is important. :^) >> This, plus 10 tries at booting, all tells me that: >> >> 1. You can't specify a recovery kernel with this method (not very comforting >> ... but palo "finds" 2.4.27-32 every time anyway). I was wondering why you >> didn't specify one in your example. Now I know. >One isn't needed. palo can list the contents of an ext2 directory. >So any vmlinux/initrd can be used if palo can list it. >> 2. initrd has nothing to do with the v3 vs. v4 problem >right >> 3. I can't find the magic in front of the symlinks vmlinux and initrd.img to >> get 2.6 to load. I get "failed to load ram disk" every time with 10 tries at >> initrd=x, where x is 0/initrd.img, 1/initrd.img, 1/boot/initrd.img, >> /boot.initrd.img, etc. Or maybe it's something else entirely. >Can you dump the following info (cut/paste to a shell): >fdisk -l /dev/sda SinoHub5:/# fdisk -l /dev/sda Disk /dev/sda: 64 heads, 32 sectors, 17366 cylinders Units = cylinders of 2048 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 95 97264 f0 Linux/PA-RISC boot /dev/sda2 96 1072 1000448 82 Linux swap /dev/sda3 1073 17366 16685056 83 Linux >mount SinoHub5:/# mount /dev/sda3 on / type ext2 (rw,errors=remount-ro) proc on /proc type proc (rw) /dev/sda1 on /boot type ext2 (rw) /dev/sdb1 on /var type ext3 (rw) >cat /etc/palo.conf SinoHub5:/# cat /etc/palo.conf --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --update-partition=/dev/sda >ls -l /boot SinoHub5:/# ls -l /boot total 0 >The "ls" command assumes the f0 partition is mounted on /boot. Well I was feeling pretty good until I saw ls -l /boot come back with total 0. I assume that's bad news. You didn't say to change init-partitioned to update-partitioned, so maybe I screwed up there. Should I have just gotten rid of that line? >> Having an f0 >> partition and an e2 /boot is looking pretty good right now! >/boot on f0 partition definitely works. >I'm certainly not the only one using it. >hth, >grant Thanks again Grant. This is very close now. I just need one more push to complete. I hope you have time to reply today. Best regards, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
