Puppy Linux Discussion Forum

Sage · Joined: 04 Oct 2005 Posts: 4767 Location: GB

To, too, two, tutu.
Which?

rdog · Joined: 18 Oct 2010 Posts: 19 Location: Quesnel, BC, Canada

I decided to try Fatdog64-611-firefox.iso and Fatdog64-611-seamonkey.iso and I am getting the same error from both while attempting to boot from a frugal install using grub. Booting from the iso burned to a DVD+RW works fine. The downloaded ISO's md5sum to the correct values.

Let me explain...
# pwd
/mnt/sda2/fd64
# ls -la
total 207072
drwxr-xr-x 2 root root 4096 Feb 5 11:52 .
drwxr-xr-x 10 root root 4096 Feb 6 08:37 ..
-rw-r--r-- 1 root root 208261680 Dec 14 12:50 initrd
-rw-r--r-- 1 root root 3767056 Dec 14 12:50 vmlinuz

# cat /mnt/sda2/boot/grub/menu.lst
# GRUB configuration file '/boot/grub/menu.lst'.
#
# Start GRUB global section
default 0
#timeout 5
timeout 5
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 5.4.3 (hard disk hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 5.4.3 pfix=ram (no pupsave file loaded, HD as hd0,1)
root (hd0,1)
kernel /puppy54/vmlinuz pfix=ram psubdir=puppy54
initrd /puppy54/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 version 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64/vmlinuz
initrd /fd64/initrd
# Linux bootable partition config ends
# Linux bootable partition config begins
title FatDog64 Seamonkey 611 (hard disk hd0,1)
rootnoverify (hd0,1)
kernel /fd64Sea/vmlinuz
initrd /fd64Sea/initrd
# Linux bootable partition config ends

# grub --version
grub (GNU GRUB 0.97)

When booting and selecting either FatDog64 option I get the error:
Error 16: Inconsistent filesystem structure

I tried the root option and later changed it to rootnoverify with no change.

My puppy 5.4.3 boot works fine from grub. I'm not sure if I'm explaining this right :/

Thanks,
Rob

rcrsn51 · Posted: Wed 06 Feb 2013, 14:31 Post subject:

rdog · Joined: 18 Oct 2010 Posts: 19 Location: Quesnel, BC, Canada

rdog · Joined: 18 Oct 2010 Posts: 19 Location: Quesnel, BC, Canada

rcrsn51 · Posted: Wed 06 Feb 2013, 15:51 Post subject:

There are a couple of possibilities.

1. Your sda2 partition has some corruption. What filesystem does it have?

2. The initrd file did not get copied correctly.

3. Your BIOS or your version of GRUB cannot handle Fatdog's humongous initrd. I have a problem when booting Fatdog off a USB drive.

rdog · Joined: 18 Oct 2010 Posts: 19 Location: Quesnel, BC, Canada

kirk · Joined: 11 Nov 2005 Posts: 1365 Location: florida

rdog,

I've had that problem with Grub-0.97 on somebody's laptop. Not sure what causes it. I think I just copied the file, deleted the original and then renamed the copy and fixed it. Something up with the filesystem I guess, though fsck didn't help. Maybe it's some kind of fragmentation.

galen

I had sound, now I do not, no panel volume
tried the control panel script, never completes.
sound card works via vlc device selection.
seems init script is dead

galen

jamesbond · Joined: 26 Feb 2007 Posts: 1877 Location: The Blue Marble

galen, please try [url="http://murga-linux.com/puppy/viewtopic.php?t=84372"]620beta1[/url] and post your test there. Btw I saw you posted a bug report in the bug report system. Just want to let you know that we've just moved the fossil repository so your bug report is deleted.

galen

noticed if fatdog is installed to the hard drive and you select grub install,
the menu.lst is corrupt, the installed will find other distros on the hard drive but list them all on one line and then ask you for a title.
something like this
found linux on [/dev/sda1][/dev/sda2][dev/sda4] what title would like

grub4dos works quite well but it not detected by other distros grub or grub2 (yuk)

I do prefer to use grub4dos on MBR and chainload into grub or grub2 for other distros

technowar · Joined: 15 Sep 2008 Posts: 10

I have a Toshiba Satellite C850 - A825 with a Realtek 8723AE wireless device.

My question is, will my wifi work? I have had problems with Debian and Ubuntu for the past few days.

smokey01 · Joined: 30 Dec 2006 Posts: 1792 Location: South Australia

Cups has stopped working and I've also noticed seamonkey-spot has stopped too.

When running seamonkey-spot from a terminal I get:

# seamonkey-spot
su: can't chdir to home directory '/root/spot'
su: can't execute '/bin/dash': Permission denied
#

Cups also stopped working when I loaded a Firefox SFS. When I unloaded Firefox, Cups began working again but not now.

The Cups home is displayed in seamonkey @ http://localhost:631/ ,
not via the spot script.

If I select Admin I get Internal Server Error.
Classes and Printers gives a permission denied error.

Any ideas?

Thanks

jamesbond · Joined: 26 Feb 2007 Posts: 1877 Location: The Blue Marble

Smokey01,

I think the savefile may have been corrupted. "/bin/dash" is the lightweight shell I use for interpreting shell scripts (because its fast), if you can't execute it something must have gone terrible wrong (either it is deleted, or corrupted and not accessible). You can copy the file back from /aufs/pup_ro/bin/dash (that's the read-only Fatdog SFS copy) to /bin/dash, but looking at the seriousness of the problem I doubt you can recover much.

One other alternative you can try is to boot kernel command line "dofsck" (that "do-fsck" without the dash), this is Fatdog's equivalent of "pfix=fsck" in Puppy. I can't remember when it started to be supported though, all I know is recent Fatdogs support it.

cheers!