Mailinglist Archive: opensuse-bugs (7823 mails)
| < Previous | Next > |
[Bug 461673] xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Thu, 5 Feb 2009 00:41:00 -0700 (MST)
- Message-id: <20090205074100.34A47245391@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=461673
User dbt@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=461673#c23
Tobias Kronwitter <dbt@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 - High |P4 - Low
--- Comment #23 from Tobias Kronwitter <dbt@xxxxxxxxx> 2009-02-05 00:40:54 MST
---
@ pgnet - mounting the devices "by-id" is an excellent idea - thank you.
Sometimes you have to leave your old paths and habits and think innovative :-))
Assuming, that the UUID of the md-devices remain constant, and all the md
devices find their physical devices by conventional device-path (true in my
case) all I had to change, was the /etc/fstab:
#/dev/md1 /boot ext3 acl,user_xattr 1 2
#/dev/md1 swap swap defaults 0 0
/dev/disk/by-id/md-uuid-081a1bd5:d2cfebd3:3d5369e9:2c7af0a6 /boot
ext3 acl,user_xattr 1 2
/dev/disk/by-id/md-uuid-6c203ec1:9360f8ba:da20cf36:64ef942c swap
swap defaults 0 0
/dev/root_dg/root_dg_vol00 / ext3 acl,user_xattr
1 1
The workaround works. The XEN-kernel (Dom0) is up and running !! :-))
The original md0-device (still present in non-xen kernel) however is still
missing and a new md-device md127 is appeard:
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [linear]
md127 : active raid1 sda1[0] sdb1[1]
200704 blocks [2/2] [UU]
md2 : active raid1 sda3[0] sdb3[1]
139243264 blocks [2/2] [UU]
md1 : active (auto-read-only) raid1 sda2[0] sdb2[1]
4192896 blocks [2/2] [UU]
unused devices: <none>
The /etc/mdadm.conf is unchanged:
DEVICE partitions
ARRAY /dev/md0 level=raid1 UUID=081a1bd5:d2cfebd3:3d5369e9:2c7af0a6
ARRAY /dev/md1 level=raid1 UUID=6c203ec1:9360f8ba:da20cf36:64ef942c
ARRAY /dev/md2 level=raid1 UUID=96498c7c:8cac6295:1f678b78:d723672a
I was hesitating, using the UUID's of the physical devices within the md-config
because of one big disadvantage:
In case of a disk replacement of the raid-systems, it would be more cumbersome
to fix the raid-devices.
The patch for setup-md.sh did not solve my original problem, the missing
md0-device. From my perspective it neither harms nor helps applying the
setup-md.sh patch (Attachment 262365 Details for Bug 461673).
Let's see, what the official solution will look like.
Thank you for your help
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User dbt@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=461673#c23
Tobias Kronwitter <dbt@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 - High |P4 - Low
--- Comment #23 from Tobias Kronwitter <dbt@xxxxxxxxx> 2009-02-05 00:40:54 MST
---
@ pgnet - mounting the devices "by-id" is an excellent idea - thank you.
Sometimes you have to leave your old paths and habits and think innovative :-))
Assuming, that the UUID of the md-devices remain constant, and all the md
devices find their physical devices by conventional device-path (true in my
case) all I had to change, was the /etc/fstab:
#/dev/md1 /boot ext3 acl,user_xattr 1 2
#/dev/md1 swap swap defaults 0 0
/dev/disk/by-id/md-uuid-081a1bd5:d2cfebd3:3d5369e9:2c7af0a6 /boot
ext3 acl,user_xattr 1 2
/dev/disk/by-id/md-uuid-6c203ec1:9360f8ba:da20cf36:64ef942c swap
swap defaults 0 0
/dev/root_dg/root_dg_vol00 / ext3 acl,user_xattr
1 1
The workaround works. The XEN-kernel (Dom0) is up and running !! :-))
The original md0-device (still present in non-xen kernel) however is still
missing and a new md-device md127 is appeard:
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [linear]
md127 : active raid1 sda1[0] sdb1[1]
200704 blocks [2/2] [UU]
md2 : active raid1 sda3[0] sdb3[1]
139243264 blocks [2/2] [UU]
md1 : active (auto-read-only) raid1 sda2[0] sdb2[1]
4192896 blocks [2/2] [UU]
unused devices: <none>
The /etc/mdadm.conf is unchanged:
DEVICE partitions
ARRAY /dev/md0 level=raid1 UUID=081a1bd5:d2cfebd3:3d5369e9:2c7af0a6
ARRAY /dev/md1 level=raid1 UUID=6c203ec1:9360f8ba:da20cf36:64ef942c
ARRAY /dev/md2 level=raid1 UUID=96498c7c:8cac6295:1f678b78:d723672a
I was hesitating, using the UUID's of the physical devices within the md-config
because of one big disadvantage:
In case of a disk replacement of the raid-systems, it would be more cumbersome
to fix the raid-devices.
The patch for setup-md.sh did not solve my original problem, the missing
md0-device. From my perspective it neither harms nor helps applying the
setup-md.sh patch (Attachment 262365 Details for Bug 461673).
Let's see, what the official solution will look like.
Thank you for your help
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |