[opensuse-factory] snapshot 20180502: /sysroot not mounted after update
I updated to snapshot 20180502 today and had to fiddle my /etc/fstab. I had root mounted on /dev/md1, /boot on /dev/md0, and /home on /dev/md2. I had to change /etc/fstab to use UUID insted of /dev/* because I got "failed to mount /sysroot" in the boot process. As I hav not seen any other error messages on this, is it likely to be a raid related problem? Kind regards Berthold -- A: Weil es die Lesbarkeit des Textes verschlechtert. F: Warum ist TOFU so schlimm? A: TOFU F: Was ist das größte Ärgernis im Usenet? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2018-05-04 21:33, Berthold Höllmann wrote:
I updated to snapshot 20180502 today and had to fiddle my /etc/fstab. I had root mounted on /dev/md1, /boot on /dev/md0, and /home on /dev/md2. I had to change /etc/fstab to use UUID insted of /dev/* because I got "failed to mount /sysroot" in the boot process.
As I hav not seen any other error messages on this, is it likely to be a raid related problem?
If you rely on arrays having certain names (such as "md0"), there ought to be a /etc/mdadm.conf saying so. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt
On Friday 2018-05-04 21:33, Berthold Höllmann wrote:
I updated to snapshot 20180502 today and had to fiddle my /etc/fstab. I had root mounted on /dev/md1, /boot on /dev/md0, and /home on /dev/md2. I had to change /etc/fstab to use UUID insted of /dev/* because I got "failed to mount /sysroot" in the boot process.
As I hav not seen any other error messages on this, is it likely to be a raid related problem?
If you rely on arrays having certain names (such as "md0"), there ought to be a /etc/mdadm.conf saying so.
You mean like: ,---- | pchoel:~ # ls -l /etc/mdadm.conf | -rw-r--r-- 1 root root 308 4. Aug 2013 /etc/mdadm.conf | pchoel:~ # cat /etc/mdadm.conf | MAILADDR berhoel@gmail.com | | DEVICE partitions | DEVICE /dev/sd[abc][134] | | ARRAY /dev/md1 metadata=1.0 name=pchoel:1 UUID=f45fac90:8d0eeefa:f4fa1ad4:287565b2 | ARRAY /dev/md0 metadata=0.90 UUID=9ba91dd1:7038e682:e989b5b4:ec36ae3b | ARRAY /dev/md2 metadata=1.0 name=pchoel:2 | UUID=1b80906c:c9302804:68cf4628:d2beaada `---- which worked for some (almost 5) years now? Kind regards Berthold Höllmann
On Freitag, 4. Mai 2018 21:33:53 CEST Berthold Höllmann wrote:
I updated to snapshot 20180502 today and had to fiddle my /etc/fstab. I had root mounted on /dev/md1, /boot on /dev/md0, and /home on /dev/md2. I had to change /etc/fstab to use UUID insted of /dev/* because I got "failed to mount /sysroot" in the boot process.
As I hav not seen any other error messages on this, is it likely to be a raid related problem?
There was a recent problem in mount point handling related to kdump, also see https://lists.opensuse.org/opensuse-factory/2018-05/msg00009.html which might also impact you here. If you are dropped to an emergency shell you can call `systemctl status` to find out which services failed, or `systemctl --failed`. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Berthold Höllmann -
berthold-tumbleweed＠xn--hllmanns-n4a.de -
Jan Engelhardt -
Oliver Kurz