Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-10-2010, 06:14 AM
|
#1
|
LQ Newbie
Registered: Nov 2004
Posts: 17
Rep:
|
"Stale NFS file handle" mount error on a non-NFS /boot partition after running lilo
Hello all,
When I run lilo (/sbin/lilo), it messes up my /boot partition. Next time I try to mount it after running lilo, I get an error: "mount: Stale NFS file handle" (I define -t ext2).
My /boot partition is ext2, mounted locally, and not nfs.
Then I do fsck /dev/sda1, and I get several: Free blocks count wrong for group #0 (7665, counted=5063). Fix<y>? I say yes to all and it works normally afterwards.
This happens only after I run lilo. Lilo is installed in MBR.
Here is relevant configuration:
Code:
root@darwin:/home/cabrilo# cat /etc/lilo.conf
append=" vt.default_utf8=0"
boot = /dev/sda
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
prompt
timeout = 30
change-rules
reset
vga = normal
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
This is my partition table:
Code:
root@darwin:/home/cabrilo# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8f800200
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 144 1052257+ 82 Linux swap
/dev/sda3 145 3432 26410860 83 Linux
/dev/sda4 3433 19457 128720812+ 83 Linux
And this is my fstab:
Code:
root@darwin:/home/cabrilo# cat /etc/fstab
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
/dev/sda4 /home ext4 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
Any ideas?
|
|
|
09-10-2010, 07:38 AM
|
#2
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
Have you checked your automounter setup? Perhaps you have / or /boot in there?
|
|
|
09-10-2010, 07:45 AM
|
#3
|
LQ Newbie
Registered: Nov 2004
Posts: 17
Original Poster
Rep:
|
Quote:
Originally Posted by MensaWater
Have you checked your automounter setup? Perhaps you have / or /boot in there?
|
Any particular automounter you think of? As far as I know, there is nothing trying to automatically mount them, but I'm not sure where to look.
|
|
|
09-10-2010, 08:16 AM
|
#4
|
LQ Guru
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
|
Look at the /etc/auto* files. However, if this is your own system that no one else ever has administered that's not likely to be the issue.
|
|
|
09-14-2010, 09:00 AM
|
#5
|
LQ Newbie
Registered: Nov 2004
Posts: 17
Original Poster
Rep:
|
Quote:
Originally Posted by MensaWater
Look at the /etc/auto* files. However, if this is your own system that no one else ever has administered that's not likely to be the issue.
|
These don't seem to be the problem.
The funny thing is, that only occurs after running lilo. In all likelyhood that's a bug to report to upstream lilo.
Meanwhile, I found a workaround:
in /etc/fstab, change this:
/dev/sda1 /boot ext2 defaults 1 2
to read:
/dev/sda1 /boot ext2 defaults 1 0
This means there is no checking when mounting. The partition still mounts fine, there is no operational problems, so I'll assume it's safe.
|
|
|
All times are GMT -5. The time now is 06:26 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|