device is missing in df
 

I have installed Ubuntu 7.10 from CD on a SATA-drive:
Everthing seemed OK until I looked at the drive with GParted which complained about missing mountpoint for /dev/sda1.

fdisk -l gives:

Device Boot Start End Blocks Id System
/dev/sda1 * 1 60424 485355748+ 83 Linux
/dev/sda2 60425 60801 3028252+ 5 Extended
/dev/sda5 60425 60801 3028221 82 Linux swap / Solaris

/etc/fstab gives:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=0e21f8c5-6e90-4434-96dc-d98a0b9ce7ee / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=ca1df9d2-e38d-4ef4-830a-d63ea1be4426 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0

but ...

df -h gives:

Filesystem Size Used Avail Use% Mounted on
varrun 505M 240K 505M 1% /var/run
varlock 505M 0 505M 0% /var/lock
udev 505M 72K 505M 1% /dev
devshm 505M 0 505M 0% /dev/shm
lrm 505M 34M 471M 7% /lib/modules/2.6.22-14-generic/volatile


Where is /dev/sda1 in df listing

Someting is very wrong but I can't figure out how to correct it ...

What do you get when you run:

$ mount

That should show all mounted file systems and their mountpoints. You are using UUIDs instead of device files for mounting in fstab. That may be causing the confusion with df and gparted.

mount gives:

proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.22-14-generic/volatile type tmpfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

still no device ... hmmm ... what I don't understand is following: I have another Linux box in my network that don't give me any alarm from GParted and df, mount is OK and fstab is also using UUID.
Here is the system that is OK:

fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=fbadb609-e209-4502-a4ca-acc939d8a8c3 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=feabf38d-0ff6-45d3-ab11-fa7149a3bfc5 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

mount:

/dev/sda1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.22-14-generic/volatile type tmpfs (rw)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

df -h:

Filesystem Size Used Avail Use% Mounted on
/dev/sda1 224G 32G 181G 16% /
varrun 2.0G 240K 2.0G 1% /var/run
varlock 2.0G 4.0K 2.0G 1% /var/lock
udev 2.0G 88K 2.0G 1% /dev
devshm 2.0G 0 2.0G 0% /dev/shm
lrm 2.0G 38M 1.9G 2% /lib/modules/2.6.22-14-generic/volatile

I cannot see what is the difference between the system that gives me problems and the system that is OK when it comes to fstab.
The 'problem system' is running as a nfs-server ... could that cause the problem ?

What do you recommend ?

Problem SOLVED.

The problem occured when I install a new system (since I upgraded my disk) and restored my backup ... unfortunately with the old fstab (all my mountpoints were there).
What happen was that the UUID in /boot/grub/menu.lst and UUID in /etc/initramfs-tools/conf.d/resume differed from UUID from old fstab.
Changing UUID:s in fstab made a difference ... now I am airborne again