Bug 5801 - installer stuck after "current_hd called but $current_hd is not an hd (raid) at ...diskdrake/hd_gtk.pm line 406"
Summary: installer stuck after "current_hd called but $current_hd is not an hd (raid) ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: NEEDINFO
: 16136 16920 17508 18089 18383 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-05-09 12:10 CEST by Thierry Vignaud
Modified: 2021-05-26 12:12 CEST (History)
8 users (show)

See Also:
Source RPM: drakxtools-17.15-1.mga6.src.rpm
CVE:
Status comment:


Attachments
installer stuck after the "currend_kind" error (16.58 KB, image/png)
2012-05-09 12:10 CEST, Thierry Vignaud
Details
initial error after clicking on "xfs" orange button (after selecting the raid) (19.62 KB, image/png)
2012-05-09 12:13 CEST, Thierry Vignaud
Details
only show filesystem buttons if type is hd/lvm (440 bytes, patch)
2013-02-03 05:02 CET, Andrew Hill
Details | Diff

Description Thierry Vignaud 2012-05-09 12:10:08 CEST
Here's an old error (we got a lot of reports back @mdv).
If one select a RAID tab, then click one of the fs button (eg: "xfs"),
the installer complains that:
"current_hd called but $current_hd is not an hd (raid) at ...diskdrake/hd_gtk.pm line 376"

And then the installer is stuck (see screenshot)
Comment 1 Thierry Vignaud 2012-05-09 12:10:41 CEST
Created attachment 2226 [details]
installer stuck after the "currend_kind" error
Comment 2 Thierry Vignaud 2012-05-09 12:13:18 CEST
Created attachment 2227 [details]
initial error after clicking on "xfs" orange button (after selecting the raid)
Comment 3 Pascal Terjan 2012-05-09 16:10:11 CEST
Indeed it is quite old, I remember improving them message to show the type between parenthesis.
I thought it had been fixed long ago but it seems I never finished https://qa.mandriva.com/show_bug.cgi?id=52433
Comment 4 Marja Van Waes 2012-05-26 13:04:51 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Marja Van Waes 2012-08-11 07:44:20 CEST
@ pterjan
@ tv

Did this get fixed before release or is it still valid?

CC: (none) => marja11

Comment 6 Thierry Vignaud 2012-08-13 10:21:56 CEST
It hasn't else we would have commented here...
Marja Van Waes 2012-08-18 14:59:41 CEST

Keywords: NEEDINFO => (none)
Whiteboard: (none) => (MGA2)

Comment 7 Fabian Wannenmacher 2012-12-21 02:12:36 CET
Stil valid for MGA3 Beta1. If you use the type-button in Expert-Mode the Problem dosn't apear. If it's not so easy to fix may just removing the colorful buttons is a simple solution for the problem.

CC: (none) => f.wanne

Marja Van Waes 2012-12-26 20:48:03 CET

Whiteboard: (MGA2) => 3beta1

Comment 8 Andrew Hill 2013-02-03 05:02:02 CET
Created attachment 3486 [details]
only show filesystem buttons if type is hd/lvm
Glen Ogilvie 2013-02-04 22:29:27 CET

CC: (none) => nelg

Comment 9 Dick Gevers 2014-11-19 20:50:30 CET
@anyone

Since pre-5 installers will not be fixed, please review against current (5beta1) or later installer and set header fields accordingly.

Alternatively, please close a.s.a.p. as resolved -> old.

Thanks.
Comment 10 Thierry Vignaud 2014-11-20 10:28:41 CET
I'm well placed to know that nothing has changed.
Comment 11 Dick Gevers 2014-11-20 10:45:12 CET
@tv: I'm aware that you are :)

Whiteboard: 3beta1 => 5beta1

Thierry Vignaud 2015-06-17 12:51:50 CEST

Source RPM: (none) => drakxtools

Comment 12 Thierry Vignaud 2015-06-17 12:52:05 CEST
*** Bug 16136 has been marked as a duplicate of this bug. ***

CC: (none) => gabcorreo

Comment 13 Thierry Vignaud 2015-06-17 12:57:03 CEST
Also reported by Gabriel Gazzan on mga4 ("Creating a RAID 0 device from 2 hard drives.")

BTW, Gabriel: could you provide journalctl logs?
Just attach the /tmp/logs.txt file resulting from running the following command (as root):
journalctl --since=2015-06-16 --until=2015-06-16 > /tmp/logs.txt

(you may want to remove useless info)

Keywords: (none) => NEEDINFO
Source RPM: drakxtools => drakxtools-16.26.12-1.mga4

Thierry Vignaud 2015-06-17 12:57:35 CEST

Summary: installer stuck after "current_hd called but $current_hd is not an hd (raid) at ...diskdrake/hd_gtk.pm line 376" => installer stuck after "current_hd called but $current_hd is not an hd (raid) at ...diskdrake/hd_gtk.pm line 406"

Comment 14 Gabriel Gazzan 2015-06-17 22:25:47 CEST
The command outputs an almost empty file (it only has a header stating the start and end dates of the log).

What can I do to give you further info?
Comment 15 Thierry Vignaud 2015-06-18 06:28:48 CEST
Use this one instead:
journalctl --since=2015-06-15 --until=2015-06-17 > /tmp/logs.txt
Comment 16 Thierry Vignaud 2015-10-08 15:42:20 CEST
*** Bug 16920 has been marked as a duplicate of this bug. ***

CC: (none) => claurence57

Comment 17 Thierry Vignaud 2015-10-08 15:43:43 CEST
From latest report:
"In a Virtualbox environment. I added 2 virtual hd and created a new RAID 0 device. the partitioning software crashed while configuring that raid 0 device
(...)
It crashes when I try to format the md0 device with another FS (and click other : the grey button)."

Whiteboard: 5beta1 => 5beta1 MGA5TOO

Comment 18 Thierry Vignaud 2016-01-17 11:09:48 CET
*** Bug 17508 has been marked as a duplicate of this bug. ***

CC: (none) => bittwister2

Thierry Vignaud 2016-01-17 11:11:04 CET

Source RPM: drakxtools-16.26.12-1.mga4 => drakxtools-17.15-1.mga6.src.rpm
Whiteboard: 5beta1 MGA5TOO => MGA5TOO

Comment 19 Thierry Vignaud 2016-03-31 12:38:25 CEST
*** Bug 18089 has been marked as a duplicate of this bug. ***

CC: (none) => l.lacher

Comment 20 Thierry Vignaud 2016-07-28 08:49:15 CEST
*** Bug 18383 has been marked as a duplicate of this bug. ***

CC: (none) => spam.1

Comment 21 Marja Van Waes 2021-05-26 12:12:58 CEST
AFAICS last time this issue was reported was in a duplicate bug report, before Mageia 6 release.

Assuming this has been fixed since then.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.