LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-10-2010, 06:14 AM   #1
cabrilo
LQ Newbie
 
Registered: Nov 2004
Posts: 17

Rep: Reputation: 0
"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?
 
Old 09-10-2010, 07:38 AM   #2
MensaWater
LQ Guru
 
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
Blog Entries: 15

Rep: Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669
Have you checked your automounter setup? Perhaps you have / or /boot in there?
 
Old 09-10-2010, 07:45 AM   #3
cabrilo
LQ Newbie
 
Registered: Nov 2004
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by MensaWater View Post
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.
 
Old 09-10-2010, 08:16 AM   #4
MensaWater
LQ Guru
 
Registered: May 2005
Location: Atlanta Georgia USA
Distribution: Redhat (RHEL), CentOS, Fedora, CoreOS, Debian, FreeBSD, HP-UX, Solaris, SCO
Posts: 7,831
Blog Entries: 15

Rep: Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669
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.
 
Old 09-14-2010, 09:00 AM   #5
cabrilo
LQ Newbie
 
Registered: Nov 2004
Posts: 17

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by MensaWater View Post
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.
 
  


Reply

Tags
lilo, mount



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ls: cannot access /etc/resolv.conf: stale nfs file handle - but i'm not using nfs schneidz Linux - General 4 10-02-2009 02:39 PM
Stale NFS file handle Error karthickmk2 Linux - Newbie 1 08-04-2009 06:40 PM
Can't get rid of "Stale NFS file handle" disciplepup Linux - Software 4 12-07-2008 07:44 PM
stale NFS file handle error hardian_97 Linux - Networking 0 10-02-2005 10:09 PM
Trying to mount W2k3 shareusing Samba 3.0.14a-Debian gives Stale NFS file handle lbclinux Debian 1 08-21-2005 07:07 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration