Linux not booting anymore after mac os formatting

intzepatorii · February 11, 2015, 8:35am

Hi,

I have created another mac partition on a different disk from the one where linux is installed and this made linux not booting anymore.
Both the usual grub entry and failsafe entry enter some kind of loop.
Is it a fix or I have to reinstall linux…
The other grub entries still work.

Thanks,
intze

wolfi323 · February 11, 2015, 10:30am

My first guess would have been that you mount some partition from the other disk via /etc/fstab, but because of the re-partitioning that partition is not found any more/cannot be mounted. So you’d have to modify /etc/fstab accordingly to fix your Linux system.

But then, you say “the other grub entries still work”. What “other” grub entries are you talking about?
Entries for other operating systems, or the entries for openSUSE that boot a different kernel?
If it’s the latter, the problem can’t really be the fstab, and probably is not related at all to your changes to the other disk.
Please clarify.

Also, as you speak of “failsafe” entry: What openSUSE version are you using? What grub are you using, grub1 or grub2? With grub2, there normally is no “failsafe” entry. It’s rather called “openSUSE … (Recovery Mode)” and hidden below “Advanced Options”.

intzepatorii · February 11, 2015, 11:04am

Thank you for the reply.
I’m using GRUB1 and Windows and Hackintosh work very well.

I formatted from Hackintosh a MAC OS Extended (journaled) partition on another disk… I didn’t think it could be a problem for linux.
I’d also prefer to keep the current linux installation as I lost some time with the customization…

I have a backup, restored the root and home partitions but still can’t boot.
How can I modify modify /etc/fstab? Can you please advise?

wolfi323 · February 11, 2015, 11:56am

Ok, GRUB1 does indeed have a “failsafe” entry.
So with “other entries” that work well you meant Windows and Hackintosh?
And you don’t have a way to boot openSUSE, right?

I formatted from Hackintosh a MAC OS Extended (journaled) partition on another disk… I didn’t think it could be a problem for linux.
I’d also prefer to keep the current linux installation as I lost some time with the customization…

Normally it shouldn’t be a problem for linux.
But if a partition is specified to be mounted in /etc/fstab (without the “nofail” option), the boot will stop if it cannot be mounted.
A partition that’s specified in /etc/fstab with “nofail” is regarded as necessary for booting the system.

Normally the system should drop to emergency mode where you could fix the problem, but there was a problem in openSUSE 13.1 that caused it to enter an endless loop instead under certain circumstances.

I have a backup, restored the root and home partitions but still can’t boot.

Your backup of /etc/fstab is probably the same.

How can I modify modify /etc/fstab? Can you please advise?

Just edit it with a text editor.
There are several ways to do this:

if you can access the Linux root partition from outside (you should be able to mount it in MacOS I suppose, or depending on the filesystem type even in Windows with some additional software, or you could boot from a LiveCD or the installation medium), just open it from there and modify it accordingly
if you boot Linux, it should enter “emergency mode”. After you enter the root password, you should be able to modify it there. But “emergency mode” might not work for you because of the problem mentioned above (which you seem to experience, according your description)
select openSUSE in the boot menu (with the cursor keys, but DON’T press RETURN yet), enter “init=/bin/sh” into the text field and press RETURN then to boot. You should get into a minimal text system, where you should be able to modify /etc/fstab.

Regarding 2 and 3, there should be at least two text editors available in text mode: vim and pico. vim is a bit unorthodox to use and may be confusing if you don’t know it, so I’d recommend to use pico.
Anyway, you should be able to edit fstab with either:

pico /etc/fstab

or

vim /etc/fstab

Comment out the partition on the other disk (by putting a ‘#’ character at the beginning of the line), or add “nofail” to the mount options, and your system should boot again.
If you’re unsure, please post the contents of /etc/fstab for further advise.

PS: on second thought, better post the contents anyway before you change anything. Maybe you have some system-critical partition on the other disk (without knowing)…

intzepatorii · February 11, 2015, 1:17pm

thank you wolfi and by the way you were right with everything.
I cannot edit it from windows or hackintosh and I wouldn’t install other application in order to access the fstab file… I will follow your 3rd advice.

I also have an old puppy linux CD, I used it to play with windows boot files.
I’ll come back in the evening with the fstab lines.

intzepatorii · February 11, 2015, 6:52pm

I installed ext2 volume manager and opened the fstab file with MS Word…

/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part6 swap swap defaults 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part7 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part5 /boot ext4 acl,user_xattr 1 2
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part8 /home ext4 acl,user_xattr 1 2
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 /windows/D ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part3 /windows/E ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part1 /windows/F ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part2 /windows/G ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part9 /windows/H ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,umask=0002 0 0

the problem is I can’t see any of the mac drives, one is an old partition of ST31000528AS, which didn’t create problems (part3 probably).
the other one is a new partition of Samsung, probably part4. however the order is not respected.

Ext2 is seeing 4 partitions on samsung and 8 partitions on seagate, just like windows computer management.

I’ll use puppy to check if the mac lines are there, maybe it’s because of windows…

wolfi323 · February 11, 2015, 7:03pm

Well, if one of those partitions cannot be mounted, the system will fail to boot.

So I would start with disabling all of them that are not on your Linux disk, i.e. change the file to this: (changes are in red)


/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part6 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part7 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part5 /boot                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part8 /home                ext4       acl,user_xattr        1 2
#/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part1 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
#/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
#/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part3 /windows/E           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
#/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part1 /windows/F           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
#/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part2 /windows/G           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
#/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part9 /windows/H           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,umask=0002 0 0

(but you should not use Word to edit that file, if you want to do it in Windows, use WordPad)
Your system should boot then again, which would make the rest easier.

Boot to Linux then and post the output of:

sudo /usr/sbin/fdisk -l

This should show all existing partitions and provide a clue which one is giving the problem.
And please also post the output of this so we are able to relate the /dev/disk/by-id/xxx to the /dev/sdXY identifiers:

ls -l /dev/disk/by-id/

intzepatorii · February 11, 2015, 7:21pm

booted with puppy… same map.
very weird, i remember i played with the download folder of hackintosh in linux, I included it in the download from windows (partition with umask=0002).
how is it possible to disappear the working partition too?
I’ll edit in puppy… it is well aligned, just like in your text field.

ps: thanks for your very quick reply.

intzepatorii · February 11, 2015, 7:58pm

from openSUSE!

Disk /dev/sda: 250.1 GB, 250059350016 bytes, 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xd2ee5fc8

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 411647 204800 7 HPFS/NTFS/exFAT
/dev/sda2 411648 150120447 74854400 7 HPFS/NTFS/exFAT
/dev/sda3 150120448 274843647 62361600 af HFS / HFS+
/dev/sda4 274843648 439742831 82449592 7 HPFS/NTFS/exFAT

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x68802c7a

Device Boot Start End Blocks Id System
/dev/sdb1 63 103426469 51713203+ 7 HPFS/NTFS/exFAT
/dev/sdb2 * 103426470 310472189 103522860 7 HPFS/NTFS/exFAT
/dev/sdb3 310472704 378054655 33790976 af HFS / HFS+
/dev/sdb4 378058689 1953520064 787730688 5 Extended
/dev/sdb5 378058752 380157951 1049600 83 Linux
/dev/sdb6 380160000 384356351 2098176 82 Linux swap / Solaris
/dev/sdb7 384358400 405329919 10485760 83 Linux
/dev/sdb8 405331968 445638655 20153344 83 Linux
/dev/sdb9 445643163 1953520064 753938451 7 HPFS/NTFS/exFAT

ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 Feb 11 20:50 ata-Optiarc_DVD_RW_AD-7261S → …/…/sr0
lrwxrwxrwx 1 root root 9 Feb 11 20:50 ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R → …/…/sda
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part1 → …/…/sda1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 → …/…/sda2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part3 → …/…/sda3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part4 → …/…/sda4
lrwxrwxrwx 1 root root 9 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T → …/…/sdb
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part1 → …/…/sdb1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part2 → …/…/sdb2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part3 → …/…/sdb3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part4 → …/…/sdb4
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part5 → …/…/sdb5
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part6 → …/…/sdb6
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part7 → …/…/sdb7
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part8 → …/…/sdb8
lrwxrwxrwx 1 root root 10 Feb 11 20:50 ata-ST31000528AS_5VP4MQ2T-part9 → …/…/sdb9
lrwxrwxrwx 1 root root 9 Feb 11 20:50 scsi-1ATA_Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R → …/…/sda
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part1 → …/…/sda1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 → …/…/sda2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part3 → …/…/sda3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part4 → …/…/sda4
lrwxrwxrwx 1 root root 9 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T → …/…/sdb
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part1 → …/…/sdb1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part2 → …/…/sdb2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part3 → …/…/sdb3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part4 → …/…/sdb4
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part5 → …/…/sdb5
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part6 → …/…/sdb6
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part7 → …/…/sdb7
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part8 → …/…/sdb8
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-1ATA_ST31000528AS_5VP4MQ2T-part9 → …/…/sdb9
lrwxrwxrwx 1 root root 9 Feb 11 20:50 scsi-SATA_Samsung_SSD_840_S1DBNSCF395744R → …/…/sda
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_Samsung_SSD_840_S1DBNSCF395744R-part1 → …/…/sda1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_Samsung_SSD_840_S1DBNSCF395744R-part2 → …/…/sda2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_Samsung_SSD_840_S1DBNSCF395744R-part3 → …/…/sda3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_Samsung_SSD_840_S1DBNSCF395744R-part4 → …/…/sda4
lrwxrwxrwx 1 root root 9 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T → …/…/sdb
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part1 → …/…/sdb1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part2 → …/…/sdb2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part3 → …/…/sdb3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part4 → …/…/sdb4
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part5 → …/…/sdb5
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part6 → …/…/sdb6
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part7 → …/…/sdb7
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part8 → …/…/sdb8
lrwxrwxrwx 1 root root 10 Feb 11 20:50 scsi-SATA_ST31000528AS_5VP4MQ2T-part9 → …/…/sdb9
lrwxrwxrwx 1 root root 9 Feb 11 20:50 wwn-0x5000c500242ece74 → …/…/sdb
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part1 → …/…/sdb1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part2 → …/…/sdb2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part3 → …/…/sdb3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part4 → …/…/sdb4
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part5 → …/…/sdb5
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part6 → …/…/sdb6
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part7 → …/…/sdb7
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part8 → …/…/sdb8
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x5000c500242ece74-part9 → …/…/sdb9
lrwxrwxrwx 1 root root 9 Feb 11 20:50 wwn-0x50025388a034c879 → …/…/sda
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x50025388a034c879-part1 → …/…/sda1
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x50025388a034c879-part2 → …/…/sda2
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x50025388a034c879-part3 → …/…/sda3
lrwxrwxrwx 1 root root 10 Feb 11 20:50 wwn-0x50025388a034c879-part4 → …/…/sda4

wolfi323 · February 11, 2015, 8:29pm

Alright. I suppose you freshly created partition 3 (marked in red)?
So the old partition 3 is now partition 4.
But you still have /dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part3 in your fstab. As this is now HFS, it cannot be mounted as NTFS…

As all your Windows partition are not really essential for booting Linux, you should add “nofail” to the mount options for all of them as already mentioned. A problem with one of them will not break your boot then.

So you should change your fstab to this, I’d say:

/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part6 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part7 /                    ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part5 /boot                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part8 /home                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part1 /windows/C           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0
/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part4 /windows/E           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part1 /windows/F           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part2 /windows/G           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0
/dev/disk/by-id/ata-ST31000528AS_5VP4MQ2T-part9 /windows/H           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,umask=0002,nofail 0 0

Another probable optimization would be to mount by “label” instead of id. You can give each partition a label (called “Volume Name” in Windows I think) that you can choose, and this won’t change if you move partitions around, create new, delete some, or even clone them to a different disk.
The easiest way to change this would be with YaST I suppose, enter the Partitioner, edit each of your partitions and set “Mount by label”. You can also set/change the label directly there.

Still, I’d recommend to add “nofail”, as there may also be other problems with those partitions preventing them from being mounted, an unclean shutdown of Windows e.g.

intzepatorii · February 11, 2015, 9:37pm

I have done the corrections in red and booting was fine, thanks a lot wolfi!

the partitions already had labels… I think I had already set them in windows or hackintosh… it seems they are not of great help, or maybe I made another mistake.
anyway nice to see my last days work not vanishing!

PS: ramdisks are already enabled by default in openSUSE? no need to move temp files, caches?
I’m planning to move linux on ssd too…

wolfi323 · February 11, 2015, 10:05pm

Well, you have to specify the label in fstab to mount a partition by its label.
E.g. instead of your existing line:

/dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNSCF395744R-part2 /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0

you would write something like:

LABEL=WINDOWS_DATA /windows/D           ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail 0 0

This means: mount the partition with the label “WINDOWS_DATA” to /windows/D (with the given mount options).
You can also use /dev/disk/by-label/WINDOWS_DATA (or similar) instead, “ls /dev/disk/by-label/” should list all your labelled partitions.

But as I said, using YaST->Partitioner is probably the easiest way to switch the way of mounting.

PS: ramdisks are already enabled by default in openSUSE? no need to move temp files, caches?
I’m planning to move linux on ssd too…

Well, some things are kept in a ram disk (or tmpfs actually… ).
But on a default openSUSE installation, /tmp is not in a tmpfs, nor are most caches.

It’s not difficult to change that, there are two ways basically:

mount them as tmpfs in fstab
create a systemd unit that mounts them as tmpfs

There have been threads about this already, please use the search function.
One of them is here: https://forums.opensuse.org/showthread.php/503886-tmpfs-under-openSUSE-13-2

intzepatorii · February 11, 2015, 10:16pm

thanks again wolfi323!