LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   One of my file systems failed to auto-mount on boot (https://www.linuxquestions.org/questions/linux-newbie-8/one-of-my-file-systems-failed-to-auto-mount-on-boot-778735/)

taylorkh 12-29-2009 01:13 PM

One of my file systems failed to auto-mount on boot
 
Ubuntu 9.10 64 bit on a Dell Studio XPS 8000 i7-860, 150 GB and 750 GB hard drives.

This has happened twice in the week or so I have owned the machine. The 750 GB drive has a partition which should be auto-mounted as "quitelarge". From /etc/fstab

Quote:

# /quitelarge was on /dev/sdb2 during installation
UUID=1b47a45b-40e0-405b-858c-86c031f1d7d9 /quitelarge ext3 defaults
When I just now rebooted to change the cable on my second monitor I noticed that /quitelarge was empty. I manually mounted it and all the data is present.

I have looked at several logs (messages, dmesg, bootstrap) and even a grep of /var/log and can find no reference to /var/sdb2. Perhaps I need to search on UUID. Can someone please point me to the appropriate log or logs to search for evidence as to why the file system does not want to mount?

Thanks,

Ken

cg40oz 12-29-2009 01:45 PM

The error should be in /var/log/messages. You can also do a mount -a, which will re-read /etc/fstab and remount the filesystems. Can you post your /etc/fstab? Is there a # in front of the /quitelarge entry?

lieqie 12-29-2009 01:51 PM

try to change 'defaults' to remount-ro

taylorkh 12-29-2009 02:55 PM

Thanks cg40oz,

There is no reference to /dev/sdb2 nor quitelarge in the message log. (My typo on the original post re. /var/sdb2.)

I will add mount -a to my things to remember list!

The applicable entry from /etc/fstab is in the original post. Uguntu uses the UUID of each resource when it writes the fstab during installation. The commented line shows that the file system in question is on /dev/sdb2. The line with the UUID is used to mount the file system as I understand. I generally remove the UUID and mount to the traditional /dev/sdb2 reference - I don't recall exactly why except that UUIDs hosed up my backup and restore strategy some years ago :-(

I had not done that on the new machine yet when the problem occurred. I have now and will reboot again to make sure everything mounts.

Thanks lieqie,

I don't really want the file system mounted read only. Perhaps
Quote:

defaults,error=remount-ro
is what I need?

Ken

cg40oz 12-29-2009 03:04 PM

taylorkh,

Try commenting out the whole line with the UUID. I have never used it and from reading the man for fstab it is form of label for the drive. That means if you do a backup and restore to a different computer it may not mount.

Try adding this to the fstab:
/dev/sdb2 /quitelarge ext3 defaults 1 2

taylorkh 12-29-2009 03:11 PM

Thanks again cg40oz,

Here is my un-UUID-ed fstab

Quote:

# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 errors=remount-ro 0 1
/dev/sda3 /data ext3 defaults 0 2
/dev/sda5 /home ext3 defaults 0 2
/dev/sdc2 /quitelarge ext3 defaults 0 2
/dev/sda6 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sdb1 /pgpdisks ext3 defaults 0 2
It seems to work OK. Yes, I believe it had to do with restoring to a different hard drive or a reformatted hard drive - a new UUID was assigned to the partition and it would not mount until I tweaked the fstab. I can see how UUIDs would be of value for a removable medium however, for a fixed mounted drive I do not see the attraction.

Ken


All times are GMT -5. The time now is 12:34 AM.