I recently bought a new solid state drive. I copy several partitions to this drive and all seemed to go well.
All of a sudden (for no reason I can understand) the system has been mounting the old “Home” partition and one other old partition to the system at start-up.
I have used the “system/partitioner” program in YaST to unmount the old partitions which allows the correct partitions to mount. They are there, but they are marked with an asterisk (*). This does not seem to re-write the “fstab” so the next time I start my system I’m back to where I started before.
Is there some way to re-write the “fstab” to reflect current state of mounted partitions or something else I can do? Previously I have simply edited the “fstab” but this is full UUID numbers which I do not understand well enough.
I even did a re-install of the system to a new partition but the same problem has followed me.
On 29/04/16 11:36, dcurtisfra wrote:
>
> aperahama;2776638 Wrote:
>>
>> Sorry, I am not sure how to post my fstab to this forum
>>
> You could do the following from a normal user’s terminal prompt:
>
> Code:
> --------------------
>
> > cat /etc/fstab
> /dev/disk/by-id/ata-OCZ-VERTEX2_OCZ-HC8068405854W13J-part2 swap swap defaults 0 0
> /dev/disk/by-id/ata-OCZ-VERTEX2_OCZ-HC8068405854W13J-part1 / ext4 defaults,noatime,acl,user_xattr 1 1
> /dev/disk/by-id/ata-ST3500418AS_Z2AENPNG-part3 /home xfs defaults,noquota 1 2
> /dev/disk/by-id/ata-WDC_WD10EZEX-60M2NA0_WD-WCC3F5AYCJL7-part2 /home01 xfs defaults,noquota 1 2
> /dev/disk/by-id/ata-ST3500418AS_Z2AENPNG-part2 /srv ext4 defaults,noatime,acl,user_xattr 1 2
> /dev/disk/by-id/ata-ST3500418AS_Z2AENPNG-part1 /tmp ext4 defaults,noatime,acl,user_xattr 1 2
> /dev/disk/by-id/ata-WDC_WD10EZEX-60M2NA0_WD-WCC3F5AYCJL7-part1 /var ext4 defaults,noatime,acl,user_xattr 1 2
> >
>
> --------------------
>
> The example /etc/fstab is from a 13.2 system with an SSD and 2
> rotational disks.
>
>
If any of the problem partitions are identified as UUID= or LABEL= in
fstab, change them to by-id mounts (in YAST/Partitioner). If you used a
cloning program, the partition copy will have the same UUID and LABEL as
the source partition and they will be “randomly” selected for mounting
at start up.
–
PeeGee
MSI m/b 890A-G43, AMD FX6300, 8GB, openSUSE 13.2/13.1 KDE x86_64 dual
boot + Win7 Premium 64bit in VBox
MSI m/b 870-C45, AMD Athlon II X3 445, 8GB, openSUSE 13.2 KDE
x86_64/Win7 Premium 64bit dual boot
If any of the problem partitions are identified as UUID= or LABEL= in
fstab, change them to by-id mounts (in YAST/Partitioner). If you used a
cloning program, the partition copy will have the same UUID and LABEL as
the source partition and they will be “randomly” selected for mounting
at start up.
–
PeeGee
Thank you PeeGee, I followed your advice to change the “Mount in /fstab” from “UUID” to “Device Name” (in YAST/Partitioner) and all is well.