fstab woes

Greetings,
I recently installed 12.3 after using 11.4 for years. When I migrated my fstab all hell broke lose.
Any device that was not attached would hang the system which didn’t happen ion 11.4. Previously, if I connected a device, it would automount according to my fstab settings. How can I do the same in 12.3? Also 2 of my 3 phones are not recognized at all in 12.3 but are still recognized if I boot to 11.4

Below is the fstab. All the commented lines are the lines that work in 11,4 but makes 12.3 hang.

/dev/disk/by-id/ata-Hitachi_HTS725050A9A364_100529PCK404VLHYPRWJ-part4 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-Hitachi_HTS725050A9A364_100529PCK404VLHYPRWJ-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK3255GSX_497MT0I9T-part1 /mnt/300g ext3 nofail 1 2
/dev/disk/by-id/ata-Hitachi_HTS725050A9A364_100529PCK404VLHYPRWJ-part5 /mnt/installs ext4 defaults 1 2
#/dev/disk/by-id/ata-Hitachi_HTS725050A9A364_100529PCK404VLHYPRWJ-part2 /mnt/old_suse ext4 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0

#/dev/disk/by-uuid/6464-3534 /mnt/tecnot3 vfat user,rw 0 0
#/dev/disk/by-uuid/27C4-F59B /mnt/tecnot8 vfat user,rw 0 0
#/dev/disk/by-uuid/FC30-3DA9 /mnt/tecnot9 vfat user,rw 0 0
#/dev/disk/by-uuid/D852-7FF8 /mnt/4g vfat user,rw,suid,dev,exec,auto,async 0 0
#/dev/disk/by-uuid/B4E4-FB09 /mnt/16g vfat user,rw,suid,dev,exec,auto,async 0 0
#/dev/disk/by-uuid/2C24-FB9E /mnt/ipod vfat user,rw,suid,dev,exec,auto,async 0 0
#/dev/disk/by-uuid/3a3f0245-abec-429c-85ba-e248d862462a /mnt/500g ext3 user,rw,suid,dev,exec,auto,async 0 0
#/dev/disk/by-uuid/91e82790-1052-43a9-acbf-0314b2516924 /mnt/1000g ext3 user,rw,suid,dev,exec,auto,async 0 0
#/dev/disk/by-uuid/2C24-FB9E /mnt/ipod vfat user,rw,suid,dev,exec,auto,async 0 0
#/dev/sr0 /mnt/dvd udf user,ro,suid,dev,exec,auto,async 0 0
#/dev/sr1 /mnt/dvd2 udf user,ro,suid,dev,exec,auto,async 0 0

First, welcome to the openSUSE forum!

Second, when you post such information, make sure to place it inside of a code # tags (just as I did above) using the advanced forum message editor.

Third, I have a bash script that when downloaded and set executable, will allow you to edit any system file as root. Have a look at the following link: SYSEdit - System File Editor - Version 1.50 - Blogs - openSUSE Forums , Try it and you will like it.

Forth, for any USB drive you want to add to your fstab file but may not be there at boot, you must add in the** nofail **load option. There are no exceptions now.

Fifth, there is really no reason to add in a fstab entry for temporary connections as they will be handled automatically for you.

Sixth, we suggest you use the /dev/disk/by-id which contains the name of the hard drive being used which is then not affected by moving drives around.

Seventh, Never use any folder names used automatically by the automount function for your own use, that will mess up the system.

I can come up with many more things, but lets adsorb the ones I have already mentioned for now.

Thank You,

On 2013-08-11 11:56, iomari wrote:
> Below is the fstab. All the commented lines are the lines that work in
> 11,4 but makes 12.3 hang.

It is almost unreadable, as the lines have wrapped round, and this is
crucial in fstab. Please use code tags for printouts and commands (the
‘#’ button). Posting in Code Tags - A Guide


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Thanks for your help. The nofail is what I was looking for. As for the other remarks, I use the folders (/mnt/xxx) because I have been using thme for many years now and have many scripts and apps looking for specific files in those places. The new mount points in 12x are a nightmare for me and for many other people I know. But thanks for the nofail and by-id tips, they are very useful.

I was very happy to help. Please take time to check out my bash script SysEdit when you get the time.

Thank You,

I’ll download it now. Thanks again

On 2013-08-11 23:16, iomari wrote:

> Thanks for your help. The nofail is what I was looking for. As for the
> other remarks, I use the folders (/mnt/xxx) because I have been using
> thme for many years now and have many scripts and apps looking for
> specific files in those places.

But it is not typical to use /mnt for disks that are always mounted. It
is used for partitions mounted temporarily or manually.

> The new mount points in 12x are a
> nightmare for me and for many other people I know.

Indeed :slight_smile:

There is a trick to make mounts got /media instead, like before, if you
want.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

I would like to know this trick though it still poses a problem for me since I;ve been using /mnt since I first started in Linux many moons ago. But if you would be so kind as to enlighten me on this “trick”, I would be grateful.

On 2013-08-12 01:56, iomari wrote:
> I would like to know this trick though it still poses a problem for me
> since I;ve been using /mnt since I first started in Linux many moons
> ago. But if you would be so kind as to enlighten me on this “trick”, I
> would be grateful.

Right.

This works on 12.3 only. Dunno about later.

create or edit “/etc/udev/rules.d/99-correct-media-mount-point.rules”, with:


ENV{ID_FS_USAGE}=="filesystem|other|crypto",ENV{UDISKS_FILESYSTEM_SHARED}="1"

And run:


udevadm control --reload

This way mounts do not go to /run/…/user/mountpoint, but to
/media/mountpoint, like “always”. The snag is that /media is a physical
directory now, not a tmpfs, so mountpoints do not always get destroyed
on reboot, and you may get new mounts on mountpoint_1 and so.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

udisks2 is expected to respect /etc/fstab and use it (and options from it) to mount devices. I’m not exactly sure about how authentication is handled at this point though.

On 2013-08-12 04:56, arvidjaar wrote:
>
> udisks2 is expected to respect /etc/fstab and use it (and options from
> it) to mount devices. I’m not exactly sure about how authentication is
> handled at this point though.

So all desktops should behave the same in this respect. I have reported
several bugzillas about this in the past. Good! :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)