[Bug 367686] New: Cannot install on SATA disk
https://bugzilla.novell.com/show_bug.cgi?id=367686 Summary: Cannot install on SATA disk Product: openSUSE 11.0 Version: Alpha 2plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: fehr@novell.com ReportedBy: trenn@novell.com QAContact: jsrain@novell.com CC: jblunck@novell.com Found By: Development The installation was started with autoyast and ssh on. It seems the system detects the one Disk as a Raid: ls /dev/mapper/ control ddf1_496e74656c202020100004118086350133102d2fbe875e63_part1 ddf1_496e74656c202020100004118086350133102d2fbe875e63 ddf1_496e74656c202020100004118086350133102d2fbe875e63_part2 inst-sys:~ # cat /proc/partitions major minor #blocks name 7 0 16788 loop0 7 1 41460 loop1 7 2 28 loop2 8 0 488386584 sda 8 1 104391 sda1 8 2 1959930 sda2 8 3 1 sda3 8 5 4891761 sda5 8 6 4891761 sda6 8 7 4891761 sda7 8 8 4891761 sda8 8 9 466752478 sda9 253 0 487304192 dm-0 253 1 104391 dm-1 253 2 1959930 dm-2 Hmm, sda partitioning is correct, we set up our machines in that way. But I wonder why there exist dm partitions 0-2. I could disable SATA Raid support in BIOS and it would work... I agree it is a bit stupid to have it switched on with only one disk, but shouldn't we be able to handle this gracefully? The machine hast one 500 GB hard drive. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c1 --- Comment #1 from Thomas Renninger <trenn@novell.com> 2008-03-06 02:23:22 MST --- Created an attachment (id=199059) --> (https://bugzilla.novell.com/attachment.cgi?id=199059) Screenshot of the hang... when trying to format swap partition -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User fehr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c2 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |trenn@novell.com --- Comment #2 from Thomas Fehr <fehr@novell.com> 2008-03-06 02:25:22 MST --- Hang itself looks more like a kernel problem than a problem in YaST2. Need y2log files. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c3 --- Comment #3 from Thomas Renninger <trenn@novell.com> 2008-03-06 02:27:41 MST --- Created an attachment (id=199061) --> (https://bugzilla.novell.com/attachment.cgi?id=199061) /var/log/Yast2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User fehr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c5 --- Comment #5 from Thomas Fehr <fehr@novell.com> 2008-03-06 02:43:59 MST --- The devices ddf... come from a DMRAID setup detectd by dmraid: # > dmraid -s -c -c -c ddf1_496e74656c202020100004118086350133102d2fbe875e63:974608384:128:stripe:ok:0:1:0 /dev/sda:ddf1:ddf1_496e74656c202020100004118086350133102d2fbe875e63:stripe:ok:974608384:0 As long as this dmraid device is present you cannot use /dev/sda since the kernel will refuse access to e.g. /dev/sda2 with "Device or resource busy". Question is why this DMRAID setup is there. Is it intentional? If yes, why did you not use the DMRAID for installation. If no, why didn't you remove the DMRAID device before trying to use /dev/sda which is part of the RAID. Nevertheless there seems to be also a bug in yast2-storage since ot should not allow usage of /dev/sda at all if there is an active DMRAID set where /dev/sda belongs to. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User fehr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c6 Thomas Fehr <fehr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@novell.com, mkoenig@novell.com AssignedTo|fehr@novell.com |mkoenig@novell.com Status|NEEDINFO |NEW Info Provider|trenn@novell.com | --- Comment #6 from Thomas Fehr <fehr@novell.com> 2008-03-06 03:01:57 MST --- ok, dmraid crashes when YaST2 tries to get data on the dmraid set. inst-sys:~ # dmraid -s -c -c ddf1_496e74656c202020100004118086350133102d2fbe875e63 Segmentation fault inst-sys:~ # This is cause for the lack of YaST2 to detect the fact that /dev/sda is not usable for installation as on as the raid set is active. I think Matthias needs to have a look at this. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c7 Thomas Renninger <trenn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ug@novell.com --- Comment #7 from Thomas Renninger <trenn@novell.com> 2008-03-06 05:22:01 MST ---
As long as this dmraid device is present you cannot use /dev/sda Ehh, yes. This probably is a autoyast issue, forgot about this. I expect autoyast is not yet capable of using dmraid devices out of the box?
I tried some time ago and autoyast worked fine when the /dev/mapper/xy device, in this case: /dev/mapper/ddf1_496e74656c202020100004118086350133102d2fbe875e63 is passed to be the disk it has to install on. For this you need to boot/install twice, one time to get the string, then add it to autoyast xml file, then try again. But I expect we also want to track down the dmraid segfault? I'll open a new bug for the autoyast dmraid issue: https://bugzilla.novell.com/show_bug.cgi?id=367734 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User fehr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c8 --- Comment #8 from Thomas Fehr <fehr@novell.com> 2008-03-06 06:57:56 MST --- Yes, there might be issues with autoyast and dmraid. This is something Uwe needs to have a look at. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c9 --- Comment #9 from Matthias Koenig <mkoenig@novell.com> 2008-03-07 07:10:19 MST --- Yes, it would be nice to track down the segfault. However I cannot reproduce it, using the same command as Thomas F. in comment #6. inst-sys:~ # dmraid -s -cc ddf1_496e74656c202020100004118086350133102d2fbe875e63:974608384:128:stripe:ok:0:1:0 I am confused. Did you change something on the machine in the meanwhile? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User fehr@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c10 --- Comment #10 from Thomas Fehr <fehr@novell.com> 2008-03-09 12:26:49 MST --- There is a linebreak added by bugzilla in my comment #6. I used the version of the dmraid command where you give the raid name on the command line. The crashing command was: "dmraid -s -c -c ddf1_496e74656c202020100004118086350133102d2fbe875e63" not like yours: "dmraid -s -cc" -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c11 --- Comment #11 from Thomas Renninger <trenn@novell.com> 2008-03-10 04:21:31 MST --- Hmm, I need to keep Yast open on my machine (started remotely after logging in with ssh -X ...). But I do not really mind, tell me if the machine's state changed (theoretically someone else could reboot it if he sees it hanging, but that should not happen...). I can also reproduce the segfault: dmraid -s -c -c ddf1_496e74656c202020100004118086350133102d2fbe875e63 Segmentation fault I tried to get a backtrace with a coredump, but the segfault seem to happen in a library... Maybe this is already enough? If not I can try to add some libraries (libdevmapper?) to get out more... I kept some warings, for reference, hope this helps: gdb -c /extern/trenn/tmp/core dmraid Using host libthread_db library "/lib64/libthread_db.so.1". warning: Can't read pathname for load map: Input/output error. warning: .dynamic section for "/lib64/libdevmapper.so.1.02" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib64/libc.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib64/ld-linux-x86-64.so.2" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: relocation results for %s : No such file or directory. Core was generated by `/tmp/dmraid -s -c -c ddf1_496e74656c202020100004118086350133102d2fbe875e63'. Program terminated with signal 11, Segmentation fault. #0 0x00007f24cf2c3a20 in ?? () (gdb) bt #0 0x00007f24cf2c3a20 in ?? () #1 0x000000000040b8dd in group_set (lc=0x2051010, name=0x7fffd76fde2f "ddf1_496e74656c202020100004118086350133102d2fbe875e63") at metadata/metadata.c:657 #2 0x000000000040492f in build_sets (lc=0x2051010, sets=<value optimized out>) at toollib.c:69 #3 0x0000000000403fb1 in perform (lc=0x2051010, argv=0x7fffd76fd348) at commands.c:648 #4 0x0000000000403a93 in main (argc=<value optimized out>, argv=0x7fffd76fd348) at dmraid.c:34 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c12 --- Comment #12 from Thomas Renninger <trenn@novell.com> 2008-03-10 04:23:23 MST --- FYI: I rebuild dmraid from stable, if something has been checked in meanwhile, the backtrace might not exactly match 11.0 Alpha2plus code... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c13 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #13 from Matthias Koenig <mkoenig@novell.com> 2008-03-10 08:14:10 MST --- Ah, I missed the linebreak in comment #6. Can reproduce it now. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c14 --- Comment #14 from Matthias Koenig <mkoenig@novell.com> 2008-03-10 10:53:37 MST --- The segfault is not happening in a library. #0 0x00007f24cf2c3a20 in ?? () comes from an invalidly dereferenced function pointer rd->fmt->group. Seems that the list of raid devices is corrupted somehow: $91 = {list = {next = 0x7f17fa3379e0, prev = 0xe3ff90}, devs = {next = 0x0, prev = 0x0}, name = 0xe27420 ".ddf1_disks", di = 0xe27450, fmt = 0x6281c0, status = s_ok, type = t_group, offset = 0, sectors = 974608384, areas = 8, meta_areas = 0xe27530, private = {ptr = 0x0, n32 = 0, n64 = 0}} The list->next pointer is obviously bogus. (gdb) p rd $92 = (struct raid_dev *) 0x7f17fa3379e0 (gdb) p rd->fmt->group $93 = (struct raid_set *(*)(struct lib_context *, struct raid_dev *)) 0x7f17fa337a20 which results in the call which segfaults. Needs still some more debugging time, but I see some progress. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=367686 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=367686#c15 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #15 from Matthias Koenig <mkoenig@novell.com> 2008-03-12 09:33:36 MST --- dmraid seems to create a superset called ".ddf1_disks". Since this does not match the requested set ddf1_496e74656c202020100004118086350133102d2fbe875e63 it is going to be freed, together with a pointer to the raid_dev already in use. This results in the usage of an invalid function pointer. I have now an ugly hack, skipping the ddf1 superset in the decision logic of group_set, so the segfault is avoided. I guess, this really needs to be fixed sometime in a more sane way. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com