Failure to boot from HDD (Solved)
Failure to boot from HDD (Solved)
Hi
I'm running Puppy 6.3.0 from a pendrive on an HP Compaq Mini 110 successfully.
However, when I try to save it to the HDD and then reboot I get the following error message:
Decompressing Linux Parsing ELF done.
Booting the kernel.
Kernel panic - not syncing.
No working init found.
I'm not certain if this is a bug, but after a lot of searching I still haven't found a solution, This thread was the closest: http://www.murga-linux.com/puppy/viewto ... be0a342d67
Be gentle with me guys this is my first post I had Lubuntu installed previously, but it was a bit sluggish to say the least,
I'm running Puppy 6.3.0 from a pendrive on an HP Compaq Mini 110 successfully.
However, when I try to save it to the HDD and then reboot I get the following error message:
Decompressing Linux Parsing ELF done.
Booting the kernel.
Kernel panic - not syncing.
No working init found.
I'm not certain if this is a bug, but after a lot of searching I still haven't found a solution, This thread was the closest: http://www.murga-linux.com/puppy/viewto ... be0a342d67
Be gentle with me guys this is my first post I had Lubuntu installed previously, but it was a bit sluggish to say the least,
Hi Nelgun.
Sorry for your problem.
Usually, after a kernel panic, there's a few other informations.
Could you retry your boot and jot down some of those informations, however cryptic
they may appear, and recopy them here?
For example, if you get:
"kernel panic -- some numbers -- busybox not tainted"
It means that there's something wrong with the busybox program, usually a faulty or
incomplete copy in the initrd.
Another common example is if you have a copy of the main puppy.sfs anywhere
else on your disks, in addition to what exists on your usb stick, you'll get a "kernel
panic". It's not an error per se. It's just that the process has a built-in stop if it's
even slightly confused about where the necessary files are.
The solution to this one is easy: find the other file or copy of your Pup and push it
down a couple of sub-directories so it won't be in the top or 1st level of directories.
But there's a host of possible other bugs, and your transcript will help us help you.
Good luck. I'm eager to hear from you.
BFN.
Sorry for your problem.
Usually, after a kernel panic, there's a few other informations.
Could you retry your boot and jot down some of those informations, however cryptic
they may appear, and recopy them here?
For example, if you get:
"kernel panic -- some numbers -- busybox not tainted"
It means that there's something wrong with the busybox program, usually a faulty or
incomplete copy in the initrd.
Another common example is if you have a copy of the main puppy.sfs anywhere
else on your disks, in addition to what exists on your usb stick, you'll get a "kernel
panic". It's not an error per se. It's just that the process has a built-in stop if it's
even slightly confused about where the necessary files are.
The solution to this one is easy: find the other file or copy of your Pup and push it
down a couple of sub-directories so it won't be in the top or 1st level of directories.
But there's a host of possible other bugs, and your transcript will help us help you.
Good luck. I'm eager to hear from you.
BFN.
Last edited by musher0 on Tue 15 Mar 2016, 19:05, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hi musher0
I get the following:
Try pairing init= option kernel. See linux doc...
CPU: 1 PID: 1 Comm : swapper 10 not tainted 3.12.55 #1
Hardware name: ...
Call trace:...
Kernel offset:....
I've tried to include what I think you need, but if you need anything under hardware, call trace or kernel offset let me know.
Cheers
Neil
I get the following:
Try pairing init= option kernel. See linux doc...
CPU: 1 PID: 1 Comm : swapper 10 not tainted 3.12.55 #1
Hardware name: ...
Call trace:...
Kernel offset:....
I've tried to include what I think you need, but if you need anything under hardware, call trace or kernel offset let me know.
Cheers
Neil
...a full install...? Trust me when I tell you that starting over with a frugal install will leave you much, much better off...
Boot from USB.
Wipe drive and re-partition with Gparted.
Reinstall using the Universal Installer, or, if you wish, copy over anything ending in .sfs and the files 'initrd.gz' and 'vmlinuz' from the flash drive to the HDD.
Run grub4dos wizard. At the end, edit the menu.lst (that's menu dot list, not menu dot first!) file to remove useless junk and to make sure that the two (or three, if you needlessly keep Safe Mode) entries for Puppy have matching pmedia=atahd statements.
My menu.lst -- bear in mind I've got an SSD, not an HDD, so strictly speaking I should have pmedia=ataflash (but I've been bad). This really is all you need. Note that your partitions' UUIDs will necessarily be different. Don't just copy mine over! (Also -- the gfxmenu/message thing is kinda advanced. Best leave that out for now.)
Boot from USB.
Wipe drive and re-partition with Gparted.
Reinstall using the Universal Installer, or, if you wish, copy over anything ending in .sfs and the files 'initrd.gz' and 'vmlinuz' from the flash drive to the HDD.
Run grub4dos wizard. At the end, edit the menu.lst (that's menu dot list, not menu dot first!) file to remove useless junk and to make sure that the two (or three, if you needlessly keep Safe Mode) entries for Puppy have matching pmedia=atahd statements.
My menu.lst -- bear in mind I've got an SSD, not an HDD, so strictly speaking I should have pmedia=ataflash (but I've been bad). This really is all you need. Note that your partitions' UUIDs will necessarily be different. Don't just copy mine over! (Also -- the gfxmenu/message thing is kinda advanced. Best leave that out for now.)
Code: Select all
# menu.lst produced by grub4dosconfig-v1.9.2
timeout 10
default 0
gfxmenu /message
# Frugal installed Puppy
title X-Tahr 1b3 (sdb3)
uuid 5bad3aca-3128-4b25-a9ac-10f39decfa5d
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
title X-Tahr 1b3 (sdb3) RAM mode
uuid 5bad3aca-3128-4b25-a9ac-10f39decfa5d
kernel /vmlinuz pmedia=atahd pfix=ram
initrd /initrd.gz
# additionals
title Reboot computer
reboot
title Halt computer
halt
Installed Frugal and amended GRUB to:
Unfortunately no system files are detected at all! I'll try copying over manually.
Code: Select all
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Unknown (sda1)
uuid b27bde14-e07c-4383-91fb-627720ee1b02
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
title Unknown ()
find --set-root --ignore-floppies --ignore-cd /
kernel /vmlinuz pmedia=atahd pfix=fsck
initrd /initrd.gz
# additionals
title Reboot computer
reboot
title Halt computer
halt
Hi Flash
I am removing the USB, but I have made that mistake!
The installer has placed the files on the HDD in a folder called slacko6.3.0frugal, which GRUB does not seem to point to.
If I move the files in this folder up a level. GRUB launches the system but just produces a screen full of text, with no obvious error messages.
Sorry I'm definitely a newb with regards Puppy,
I am removing the USB, but I have made that mistake!
The installer has placed the files on the HDD in a folder called slacko6.3.0frugal, which GRUB does not seem to point to.
If I move the files in this folder up a level. GRUB launches the system but just produces a screen full of text, with no obvious error messages.
Sorry I'm definitely a newb with regards Puppy,
neigun. Sometimes, like a roadmap, it helps to give Grub4dos specific directions.
Try this. Use the directory name -slacko6.3.0frugal - then find and write to your menu.lst the exact location.
Here is one section from multiple Puppy mounts as an example, giving a direct location:
PS. First. Make a backup of your menu.lst - and keep it safe!
Try this. Use the directory name -slacko6.3.0frugal - then find and write to your menu.lst the exact location.
Here is one section from multiple Puppy mounts as an example, giving a direct location:
Change names and location in menu.lst as appropriate; see if the same style works for you.title Puppy-Lupo-Mini-528-6
find --set-root --ignore-floppies /Puppy-Lupo-Mini-5286/initrd.gz
kernel /Puppy-Lupo-Mini-5286/vmlinuz pmedia=atahd psubdir=Puppy-Lupo-Mini-5286 acpi=force pfix=fsck
initrd /Puppy-Lupo-Mini-5286/initrd.gz
PS. First. Make a backup of your menu.lst - and keep it safe!