[opensuse] renaming disks
hi all, Can anyone give me a clue where the naming of disk devices is defined? For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules Is there an equivalent for sata-drives? On my file server, i had five drives, the original sda (where i boot from and contained the 11.3) and four others in softread-10. Unfortunately, two weeks ago, my sda "expired", so i bought a new one. As a precaution i disconnected the all data-drives during the installation of 12.2. After completion, i powered down the machine, connected the data drives, powered up and after a "vgchange -ay" the secondary volumegroup was detected and i could manually mount all LV's again, and i started recovering. Alas, after last nights reboot, the disks holding the OS now appears as "SDE" instead of "SDA", and my secondary volume-group remains invisible. I had the impression that suse was doing the mount by UUID by default. but obviously i'm mistaken? For any suggestions i'm more than welcome: As i was still recovering from previous "event", last changes were not on backup ;-( Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hans Witvliet wrote:
hi all,
Can anyone give me a clue where the naming of disk devices is defined? For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules
Is there an equivalent for sata-drives?
Not that I am aware of.
On my file server, i had five drives, the original sda (where i boot from and contained the 11.3) and four others in softread-10.
Unfortunately, two weeks ago, my sda "expired", so i bought a new one. As a precaution i disconnected the all data-drives during the installation of 12.2. After completion, i powered down the machine, connected the data drives, powered up and after a "vgchange -ay" the secondary volumegroup was detected and i could manually mount all LV's again, and i started recovering.
Alas, after last nights reboot, the disks holding the OS now appears as "SDE" instead of "SDA", and my secondary volume-group remains invisible.
I guess your secondary VG uses /dev/sda?
I had the impression that suse was doing the mount by UUID by default. but obviously i'm mistaken?
Check your fstab.
For any suggestions i'm more than welcome:
It sounds it is really in LVM you have a problem? That your PV that used to be /dev/sda is now called /dev/sde. -- Per Jessen, Zürich (16.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2012-09-22 at 15:36 +0200, Per Jessen wrote:
Hans Witvliet wrote:
hi all,
Can anyone give me a clue where the naming of disk devices is defined? For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules
Is there an equivalent for sata-drives?
Not that I am aware of.
On my file server, i had five drives, the original sda (where i boot from and contained the 11.3) and four others in softread-10.
Unfortunately, two weeks ago, my sda "expired", so i bought a new one. As a precaution i disconnected the all data-drives during the installation of 12.2. After completion, i powered down the machine, connected the data drives, powered up and after a "vgchange -ay" the secondary volumegroup was detected and i could manually mount all LV's again, and i started recovering.
Alas, after last nights reboot, the disks holding the OS now appears as "SDE" instead of "SDA", and my secondary volume-group remains invisible.
I guess your secondary VG uses /dev/sda? No the other way round, The primary vg uses sda2 (/boot is using sda1) sdb, sdc, sdd and sde are glued together with soft-raid10 And ontop of that i made my secondary VG
I had the impression that suse was doing the mount by UUID by default. but obviously i'm mistaken?
Check your fstab.
For any suggestions i'm more than welcome:
It sounds it is really in LVM you have a problem? That your PV that used to be /dev/sda is now called /dev/sde.
Strangest thing however is, after i replaced the malfunctioning system disk (sda) with an other, the system booted and named that as sda. And i was still able to use sdb|c|d|e. When i boot now, my systemdisk has become sdE, ad the data-disk became sd-A|B|C|D. afaicr, the raid-description lays in the first area of the disks themselves, and i'll guess the renaming of the disks is causing md not recognizing what belongs to which disk. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hans Witvliet wrote:
On Sat, 2012-09-22 at 15:36 +0200, Per Jessen wrote:
I guess your secondary VG uses /dev/sda?
No the other way round, The primary vg uses sda2 (/boot is using sda1) sdb, sdc, sdd and sde are glued together with soft-raid10 And ontop of that i made my secondary VG
If that is invisible, try vgscan. There is a bugreport on problems with lvm on startup, but I can't access buzilla riught now.
It sounds it is really in LVM you have a problem? That your PV that used to be /dev/sda is now called /dev/sde.
Strangest thing however is, after i replaced the malfunctioning system disk (sda) with an other, the system booted and named that as sda. And i was still able to use sdb|c|d|e.
When i boot now, my systemdisk has become sdE, ad the data-disk became sd-A|B|C|D.
The order depends on the ordering of the driver modules.
afaicr, the raid-description lays in the first area of the disks themselves, and i'll guess the renaming of the disks is causing md not recognizing what belongs to which disk.
Uh, you have a problem with your RAID setup now? That wasn't clear from your first posting. AFAIK, MD-Raid does not rely on the device names. -- Per Jessen, Zürich (14.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-23 12:20, Per Jessen wrote:
Uh, you have a problem with your RAID setup now? That wasn't clear from your first posting. AFAIK, MD-Raid does not rely on the device names.
When my machine boots it tries to activate raid from definitions such as /dev/sdc11, /dev/sdb10, etc. I don't know why, but I know it is so because it prints a message about failing. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBe/70ACgkQIvFNjefEBxqGZgCgoRSQBZ/igAeYI4aUXfUZ6Pwu yjoAnjN35P5MgUmUp2aAB4tRhsENtztM =GWV4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-23 12:20, Per Jessen wrote:
Uh, you have a problem with your RAID setup now? That wasn't clear from your first posting. AFAIK, MD-Raid does not rely on the device names.
When my machine boots it tries to activate raid from definitions such as /dev/sdc11, /dev/sdb10, etc. I don't know why, but I know it is so because it prints a message about failing.
sdc11 and sdb10 are partitions. Check what /etc/mdadm.conf contains. -- Per Jessen, Zürich (18.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-23 14:57, Per Jessen wrote:
Carlos E. R. wrote:
When my machine boots it tries to activate raid from definitions such as /dev/sdc11, /dev/sdb10, etc. I don't know why, but I know it is so because it prints a message about failing.
sdc11 and sdb10 are partitions.
I know.
Check what /etc/mdadm.conf contains.
Telcontar:~ # cat /etc/mdadm.conf DEVICE containers partitions ARRAY /dev/md0 UUID=825b22e8:af550e83:93727666:fb8987fd Telcontar:~ # and: Telcontar:~ # l /dev/disk/by-uuid/ | grep 825b22e8 Telcontar:~ # l /dev/disk/by-uuid/ | grep md0 lrwxrwxrwx 1 root root 9 Sep 18 22:29 451fb568-860a-4ee3-b238-1423bfb0a034 -> ../../md0 - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBfEVwACgkQIvFNjefEBxpjsACeLvVRNyETREtUPWcpweI9vc1/ P7YAniTRkOiG/zKsUL/gywYRPMxmXYd4 =YbNt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-23 14:57, Per Jessen wrote:
Carlos E. R. wrote:
When my machine boots it tries to activate raid from definitions such as /dev/sdc11, /dev/sdb10, etc. I don't know why, but I know it is so because it prints a message about failing.
sdc11 and sdb10 are partitions.
I know.
I presume they are not type 0xFD?
Check what /etc/mdadm.conf contains.
Telcontar:~ # cat /etc/mdadm.conf DEVICE containers partitions ARRAY /dev/md0 UUID=825b22e8:af550e83:93727666:fb8987fd Telcontar:~ #
and:
Telcontar:~ # l /dev/disk/by-uuid/ | grep 825b22e8 Telcontar:~ # l /dev/disk/by-uuid/ | grep md0 lrwxrwxrwx 1 root root 9 Sep 18 22:29 451fb568-860a-4ee3-b238-1423bfb0a034 -> ../../md0
Yeah, the uuid in madm.conf doesn't match /dev/disk/by-uuid/ - I don't know if they are meant to match. -- Per Jessen, Zürich (19.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-23 15:58, Per Jessen wrote:
Carlos E. R. wrote:
sdc11 and sdb10 are partitions.
I know.
I presume they are not type 0xFD?
Yes, they are. Telcontar:~ # fdisk -l | grep raid Disk /dev/md0 doesn't contain a valid partition table /dev/sdb10 148022973 173196764 12586896 fd Linux raid autodetect /dev/sdc13 450012843 475186634 12586896 fd Linux raid autodetect /dev/sda11 294824943 319998734 12586896 fd Linux raid autodetect
Yeah, the uuid in madm.conf doesn't match /dev/disk/by-uuid/ - I don't know if they are meant to match.
It is possible that the file belongs to an older raid that disappeared. Maybe I have to recreate the raid again in yast. Funny that the raid is mounted, anyway :-) [...] yast says: Device: Device: /dev/md0 Size: 24.01 GB Encrypted: No Device ID 1: md-uuid-825b22e8:af550e83:93727666:fb8987fd Device ID 2: md-name-Telcontar:0 Notice that "md-uuid", it matches. Funny :-? - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBfGyIACgkQIvFNjefEBxpAMwCgoGB1Twpl+lm9VqFpd6NSknmP HMkAoIk9BIhmUB083j8GLJnQDTxvWQL5 =Ja98 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2012-09-23 15:58, Per Jessen wrote:
Carlos E. R. wrote:
sdc11 and sdb10 are partitions.
I know.
I presume they are not type 0xFD?
Yes, they are.
Telcontar:~ # fdisk -l | grep raid Disk /dev/md0 doesn't contain a valid partition table /dev/sdb10 148022973 173196764 12586896 fd Linux raid autodetect /dev/sdc13 450012843 475186634 12586896 fd Linux raid autodetect /dev/sda11 294824943 319998734 12586896 fd Linux raid autodetect
But if they are not in a RAID config, why do they have that type?
Yeah, the uuid in madm.conf doesn't match /dev/disk/by-uuid/ - I don't know if they are meant to match.
It is possible that the file belongs to an older raid that disappeared. Maybe I have to recreate the raid again in yast. Funny that the raid is mounted, anyway :-)
I'm guessing that the superblocks have been found, which is enough. -- Per Jessen, Zürich (19.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2012-09-23 at 17:25 +0200, Per Jessen wrote:
I presume they are not type 0xFD?
Yes, they are.
Telcontar:~ # fdisk -l | grep raid Disk /dev/md0 doesn't contain a valid partition table /dev/sdb10 148022973 173196764 12586896 fd Linux raid autodetect /dev/sdc13 450012843 475186634 12586896 fd Linux raid autodetect /dev/sda11 294824943 319998734 12586896 fd Linux raid autodetect
But if they are not in a RAID config, why do they have that type?
Well, I do have a raid 5 with those partitions, and it mounts (later). The "problem" is those messages during early boot. Perhaps if the raid were needed for booting I would have problems. Or perhaps because of that error things work, because the boot messages I refer to happen during the early boot before the kernel sees that there is a suspended image in swap and that it must restore it. If it attempted to mount that raid r/w it would be a fine problem. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlBjcE8ACgkQtTMYHG2NR9WwEQCeNox20J2b0pvYVnTJR0o9DF3b 74kAoIO0mUQKvV8Qyw9xUL2wJsNtdsq6 =i56W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-22 15:16, Hans Witvliet wrote:
hi all,
Can anyone give me a clue where the naming of disk devices is defined? For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules
Is there an equivalent for sata-drives?
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBdzMQACgkQIvFNjefEBxoPggCfeBXeDl6hor2/eHRJmBYpT+Qn fAMAnRVExnTRmoAjGVtCu/qHEi0M9d/h =Tk3p -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-22 15:16, Hans Witvliet wrote:
hi all,
Can anyone give me a clue where the naming of disk devices is defined? For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules
Is there an equivalent for sata-drives?
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later.
Disks are named - sda, sdb, sdc etc. -- Per Jessen, Zürich (14.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-22 16:42, Per Jessen wrote:
Carlos E. R. wrote:
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later.
Disks are named - sda, sdb, sdc etc.
They have a name based on the time the bios sees them first. They are not "named" used as an action verb, you can not name a disk as sda if you so wish. - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBd1d0ACgkQIvFNjefEBxrHSQCeI3kBfE00vWq518FVnZ9vV5gz 4z4An2knrTyV4ofks5WwBhZj3Nh3wAlB =B560 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-22 16:42, Per Jessen wrote:
Carlos E. R. wrote:
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later.
Disks are named - sda, sdb, sdc etc.
They have a name based on the time the bios sees them first.
Actually, they're are given device names when they are discovered - for instance when you plug them in (USB etc), or when the driver is loaded (SCSI etc).
They are not "named" used as an action verb, you can not name a disk as sda if you so wish.
You're right, "you" cannot name them, but the kernel can and does. Block devices are given a device _name_ depending on the sequence in which they are seen/discovered. I'm pretty certain this is calling "naming", see e.g. http://tldp.org/HOWTO/Partition-Mass-Storage-Definitions-Naming-HOWTO/x99.ht... -- Per Jessen, Zürich (14.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-22 17:53, Per Jessen wrote:
Carlos E. R. wrote:
They have a name based on the time the bios sees them first.
Actually, they're are given device names when they are discovered - for instance when you plug them in (USB etc), or when the driver is loaded (SCSI etc).
Yes.
They are not "named" used as an action verb, you can not name a disk as sda if you so wish.
You're right, "you" cannot name them, but the kernel can and does. Block devices are given a device _name_ depending on the sequence in which they are seen/discovered. I'm pretty certain this is calling "naming", see e.g.
Uncertainties of human languages :-) Yes, the kernel names them in the order it finds them, and we have no control over those names. That's why other naming schemes exist, such as id, uuid, label, path... - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBd4h8ACgkQIvFNjefEBxq54ACgp9D8KZczwiad+NXYMkTi972H 7YQAoJ3m+cSStudWoLRPj+AY3plYwzJH =syyo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/22/2012 05:53 PM, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-22 16:42, Per Jessen wrote:
Carlos E. R. wrote:
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later. Disks are named - sda, sdb, sdc etc. They have a name based on the time the bios sees them first. Actually, they're are given device names when they are discovered - for instance when you plug them in (USB etc), or when the driver is loaded (SCSI etc).
They are not "named" used as an action verb, you can not name a disk as sda if you so wish. You're right, "you" cannot name them, but the kernel can and does.
Just to confuse the matter further, all the kernel uses to know which device is which is the major and minor number. You can rename the device nodes to anything you want as long as you keep the same major and minor number, things will still work, the only thing that will fail is that programs won't know to look for your new name, but you could do mv /dev/sdc /dev/mydisk and then mount /dev/mydisk on some mount point Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anders Johansson wrote:
On 09/22/2012 05:53 PM, Per Jessen wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-09-22 16:42, Per Jessen wrote:
Carlos E. R. wrote:
AFAIK, disks are not named, but partitions are. When you create a filesystem you can assign a label, or do it later. Disks are named - sda, sdb, sdc etc. They have a name based on the time the bios sees them first. Actually, they're are given device names when they are discovered - for instance when you plug them in (USB etc), or when the driver is loaded (SCSI etc).
They are not "named" used as an action verb, you can not name a disk as sda if you so wish. You're right, "you" cannot name them, but the kernel can and does.
Just to confuse the matter further,
Arrgh, Anders, we had just managed to sort this out in a nice and understandable form :-) -- Per Jessen, Zürich (13.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Sep 22, 2012 at 03:16:59PM +0200, Hans Witvliet wrote:
Can anyone give me a clue where the naming of disk devices is defined?
The links in /dev/disk/by-id/ are maintained by the kernel and are derivated from the device ID the manufacturer defined at production time.
For network interfaces you have: /etc/udev/rules.d/70-persistent-net.rules
Is there an equivalent for sata-drives? On my file server, i had five drives, the original sda (where i boot from and contained the 11.3) and four others in softread-10.
Unfortunately, two weeks ago, my sda "expired", so i bought a new one. As a precaution i disconnected the all data-drives during the installation of 12.2. After completion, i powered down the machine, connected the data drives, powered up and after a "vgchange -ay" the secondary volumegroup was detected and i could manually mount all LV's again, and i started recovering.
Alas, after last nights reboot, the disks holding the OS now appears as "SDE" instead of "SDA", and my secondary volume-group remains invisible.
I guess this is caused by two independent issues. Have you modified anything in between the reboots? Either on the BIOS or on the cabeling level? Connecting SATA disks to different SATA ports might result in a changed order.
I had the impression that suse was doing the mount by UUID by default. but obviously i'm mistaken?
The default is mount by UUID. Check your /etc/fstab and you'll know. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-09-22 22:15, Lars Müller wrote:
I had the impression that suse was doing the mount by UUID by default.
but obviously i'm mistaken? The default is mount by UUID.
Check your /etc/fstab and you'll know.
What about the members of the volume-groups? - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBeIE8ACgkQIvFNjefEBxr4agCgzosUZhgwB4wW2j1io9JA4wgn 9JEAmwVQdoLXnNv1AVBjVorKeg3IbFi7 =DlxX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lars Müller wrote:
I had the impression that suse was doing the mount by UUID by default. but obviously i'm mistaken?
The default is mount by UUID.
Just as a matter of curiosity, when did that change? Ubuntu mounts by UUID but openSUSE used to mount by disk-id -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anders Johansson -
Carlos E. R. -
Dave Howorth -
Hans Witvliet -
Lars Müller -
Per Jessen