| Summary: | diskdrake crashes if JMIcron RAID running degraded or no longer RAID | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Mark Dawson Butterworth <mageia> |
| Component: | RPM Packages | Assignee: | Pascal Terjan <pterjan> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | pterjan |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools-backend | CVE: | |
| Status comment: | |||
|
Manuel Hiebel
2011-12-18 21:07:13 CET
CC:
(none) =>
pterjan Curiouser and curiouser. If I plug in the drive which was connected using eSATA when part of the RAID set but now as a USB drive, fdisk sees it as sdd. diskdrake then runs without crashing, but does not see sdd - only sda (as mapper/nvidia_fbabbeci), sdb (a mapper/jmicron_JRAID), and sdc (HighPoint hardware RAID). Weird.
Thierry Vignaud
2012-04-18 18:06:00 CEST
Assignee:
thierry.vignaud =>
pterjan Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |
I experience a crash (common to Mandriva 2010) under two circumstances when using the JMicron RAID controller: a) RAID1 array running degraded (eSATA drive not connected) b) RAID1 array changed to be no longer in RAID mode using BIOS a) is not particularly important, but b) means that I am currently unable to use diskdrake at all. [root@fast mark]# diskdrake ERROR: jmicron: wrong # of devices in RAID set "jmicron_JRAID" [1/2] on /dev/sdb ERROR: jmicron: wrong # of devices in RAID set "jmicron_JRAID" [1/2] on /dev/sdb INTERNAL ERROR: unknown device sdb1 MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:186 devices::entry() called from /usr/lib/libDrakX/devices.pm:201 devices::make() called from /usr/lib/libDrakX/fs/type.pm:279 fs::type::call_blkid() called from /usr/lib/libDrakX/fs/type.pm:287 fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/fsedit.pm:271 fsedit::get_hds() called from /usr/sbin/diskdrake:74 Subset of fdisk -l: Disk /dev/sdb: 400.1 GB, 400088457216 bytes 255 heads, 63 sectors/track, 48641 cylinders, total 781422768 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 identifier: 0x8313e26f Device Boot Start End Blocks Id System /dev/sdb1 * 63 42042104 21021021 7 HPFS/NTFS /dev/sdb2 42042105 488359934 223158915 5 Extended /dev/sdb5 42042168 84276989 21117411 7 HPFS/NTFS /dev/sdb6 84277053 126656459 21189703+ 83 Linux /dev/sdb7 126656523 208989584 41166531 83 Linux /dev/sdb8 208989648 368129474 79569913+ 83 Linux /dev/sdb9 368129538 488359934 60115198+ 7 HPFS/NTFS