The partition type is the important bit. During booting Grub does not use swap. Grub can boot a system with filing it cannot read using the technique called chainloading.
In your case I suggest you boot the 2nd Puppy system manually by typing one line at a time as follow Code:. Further to your advice I tried your advice with partial success by booting manually using the entering 3 separate lines of code from Grub. I thought if it might it be worthwhile if an exact copy of the text was pasted into Grub configuration menu.
Attached Files Puppy device dot map. Your 2nd Puppy boots as expected and the original error has been overcome. When a Linux boots to a panic state it is to do with the kernel and not the boot loader. To diagnose your new problem different info will be needed.
The kernel panic is more to do with the Puppy is being used in a state different to it original arrangement, say it was installed when there was only one hard disk or it has been moved from an internal hard disk to a USB disk. Although Puppy can be booted from different hard disk arrangement it should not be changed once installed or the installation was unsuccessful until you passed your last error. The quickest way is usually re-install the 2nd Puppy again if there is no useful information from it.
This could happen if your 2nd Puppy was installed in a standalone disk but now another disk has been added. Your Puppy the 2nd copy was installed in sda2 when its menu. I get this error with Grub, so it might be some reconfiguring of BIOS, connector-setup, or something else. This was a good buy, half of new price with warranty, but still I've heard of people doing just fine with Jmicron and many good reputated mainboard come with that controller, although it's not that kind to Linux.
Stand back, intruder, or i'll blast you out of space! I am Klixon and I don't want any dealings with you human lifeforms. Hi, Everyone I found on other forum replies that a problem seems to exist when migrating to SATA disks, or something.
Anyway, I then tried installing 8. I quit the install but impaired the size of my first partition, an unused W98 area. Is there any way to fix the Ubuntu boot error 21? I am not really literate in Linux command line syntax, so any very complicated fix will not be good for me. It may be that I should just wipe out my copied and pasted 8. I noticed that the installation for 8.
Perhaps this gives me the best of both worlds. Just a bit flummoxed here The results of that script will help clarify your setup and hopefully what the solution to your booting problem might be. Pumalite and CalJohn Thanks so much for your replies--I truly appreciate them. I will do as you indicate but have a couple of prior commitments just now. Thanks again, Casp. I've spent a good deal of time attempting to access the MBR information that the boot info script should give us.
I tried many more permutations than those, above, just for fun. Though the file downloaded just fine--and I am sending you this from the Live CD boot--I just can't seem to get things to run. Do you have any other suggestions? Thanks so much, C. I then try "root hd2 and get the error When I boot from the cd in rescue mode, and manualy install grub using "root hd2 setup hd2,0 , it sees the drive and installs the bootloader, but when I reboot I get the splash screen and then the machine reboots.
Any ideas? Board index All times are UTC.
0コメント