Lately when I boot Puppy I get a message when bootup starts:
"ext2-fs (sdb4): error: ext-lookup: deleted inode referenced 798126"
I get this nine times in quick succession, with different numbers.
The sdb4 partition is formatted ext2, with various frugal installs of Puppy.
Does anyone know what's happening, and how to eliminate the messages?
"deleted inode referenced" on boot -- Solved!
"deleted inode referenced" on boot -- Solved!
Last edited by davec51 on Sat 03 Mar 2012, 21:02, edited 1 time in total.
Sounds like file corruption errors, maybe just be occurring at shutdown, and if it keeps happening, may indicate a flakey hard drive
Try copying your drive contents that you want to keep elsewhere, [DVD/USB HDD?] then reformat the drive, and dead/flakey sectors should get locked out
A quick simple check is to boot with
which does a full filesystem check
http://puppylinux.org/wikka/BootParametersPuppy
or, To check the save file, boot from the CD with puppy pfix=ram and go to the directory where the save file is.
In a console/terminal enter
...as checks cannot be made on a live/mounted savefile
http://oreilly.com/linux/command-direct ... h=e/e2fsck
more rarely -c can be used instead of -v for badblocks checks - as above
HTH
Aitch
Try copying your drive contents that you want to keep elsewhere, [DVD/USB HDD?] then reformat the drive, and dead/flakey sectors should get locked out
A quick simple check is to boot with
Code: Select all
Puppy pfix=purge
http://puppylinux.org/wikka/BootParametersPuppy
or, To check the save file, boot from the CD with puppy pfix=ram and go to the directory where the save file is.
In a console/terminal enter
Code: Select all
e2fsck -v <the name of your save file>.2fs
http://oreilly.com/linux/command-direct ... h=e/e2fsck
more rarely -c can be used instead of -v for badblocks checks - as above
HTH
Aitch
ran e2fsck
I ran e2fsck on the partition. Many errors to correct, but now no error messages.
-
- Posts: 91
- Joined: Fri 06 Jul 2012, 14:34
- Location: Nearly North Dakota.
- James186282
- Posts: 270
- Joined: Tue 08 Sep 2009, 19:14
- Location: Minnesota
e2fsck
I've got some inode problems on a compressed save file. I tried running puppy in ram only and running e2fsck on the unmounted compressed save file and it lists a series of errors mentioning compression and suggesting I need a newer version of e2fsck. Has anyone had success fixing a compressed volume and if so... How was it done? Thanks in advance for any wisdom on this.
Science is what we understand well enough to explain to a computer.
Art is everything else we do.
[i]Donald Knuth [/i]
Art is everything else we do.
[i]Donald Knuth [/i]