[ale] fstab question

[Sean]

Damned if I know!  The system seems to be operating normally after the boot
sequence completes. Obviously /, /home, and swap are mounting normally. I am
assuming that /boot is also mounted as the message pops up at the beginning of
the boot process, which scrolls along normally.
<mount> reports that /boot is mounted on /sda1; /home is on /sda6; / is on /sda5.
 I have no idea what might have happened to /sda2-4. :)

But just in case it might be useful, here is what <mount> reports:

kilpatms at pfc:~$ mount
/dev/sda5 on / type ext3 (rw,relatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda1 on /boot type ext3 (rw,relatime)
/dev/sda6 on /home type ext3 (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/kilpatms/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=kilpatms)

TIA

Sean

---------------------------------------------------------------------------------

On Tue Nov  3 15:58 , Jim Kinney <jim.kinney at gmail.com> sent:

>which line failed to mount?
>
>On Tue, Nov 3, 2009 at 3:39 PM, Sean kilpatms at speakeasy.net> wrote:
>> Upgraded Ubuntu last night on this netbook. Have one sorta odd glitch.
>> On boot, the OS reports it cannot mount one of the lines in the fstab file.
>>
>> I have copied the file below. I have never seen an fstab file that looked like
>> this one.
>>
>> Can I solve this problem by simply commenting out the first line? Or should I
>> just ignore the warning?
>>
>> Sean
>>
>>
--------------------------------------------------------------------------------------
>>
>> # /etc/fstab: static file system information.
>> #
>> # Use 'vol_id --uuid' to print the universally unique identifier for a
>> # device; this may be used with UUID= as a more robust way to name devices
>> # that works even if disks are added and removed. See fstab(5).
>> #
>> #                
>> proc            /proc           proc    defaults        0       0
>> # / was on /dev/sda5 during installation
>> UUID=99b3cc22-ba4b-4333-b7ea-2c05be080bd0 /               ext3
>> relatime,errors=remount-ro 0       1
>> # /boot was on /dev/sda1 during installation
>> UUID=1866e268-96e3-4aaf-b727-b66140d931a3 /boot           ext3    relatime
>>  0       2
>> # /home was on /dev/sda6 during installation
>> UUID=f66626c0-a831-4fda-bf8d-a2898383439a /home           ext3    relatime
>>  0       2
>> # swap was on /dev/sda7 during installation
>> UUID=c5279109-2f3b-4214-8c02-f5ee54550104 none            swap    sw
>>  0       0
>>
>>
>>
>>
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>>
>
>
>
>-- 
>-- 
>James P. Kinney III
>Actively in pursuit of Life, Liberty and Happiness
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://mail.ale.org/mailman/listinfo/ale
>See JOBS, ANNOUNCE and SCHOOLS lists at
>http://mail.ale.org/mailman/listinfo
>