LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   "Stale NFS file handle" mount error on a non-NFS /boot partition after running lilo (http://www.linuxquestions.org/questions/slackware-14/stale-nfs-file-handle-mount-error-on-a-non-nfs-boot-partition-after-running-lilo-831349/)

cabrilo 09-10-2010 07:14 AM

"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?

MensaWater 09-10-2010 08:38 AM

Have you checked your automounter setup? Perhaps you have / or /boot in there?

cabrilo 09-10-2010 08:45 AM

Quote:

Originally Posted by MensaWater (Post 4093397)
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.

MensaWater 09-10-2010 09:16 AM

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.

cabrilo 09-14-2010 10:00 AM

Quote:

Originally Posted by MensaWater (Post 4093432)
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 08:50 PM.