Bug 21986

Summary:	diskdrake cannot see a USB key newly connected to the computer
Product:	Mageia	Reporter:	Christian C <bugzzzz>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien, pterjan
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakxtools	CVE:
Status comment:
Attachments:	Some commands run when the USB key was not detected

Description Christian C 2017-11-05 22:10:20 CET

Description of problem:
I connected a USB key to the computer in order to format it but drakconf did not displayed it in the device list while it was identified by different commands (see attached file) :
# dmesg
# ls /dev/sd*
# fdisk /dev/sdb
The USB key contents was the result of "dd if=~/tmp/Mageia-6-x86_64-DVD.iso of=/dev/sdX bs=1M"

Version-Release number of selected component (if applicable):
drakxtools-curses-17.88-1.mga6

How reproducible:
Don't know

Steps to Reproduce:
1. plug a USB key into the computer
2. look in drakconf->Local disks->Manage disk partitions
3.

Comment 1 Christian C 2017-11-05 22:19:46 CET

Created attachment 9776 [details]
Some commands run when the USB key was not detected

The commands where :

on the MCC :
drakconf->Local disks->Manage disk partitions->options->Display logs
then, I copied/pasted the contents

on the command line :
# dmesg
# ls /dev/sd*
# fdisk /dev/sdb

Comment 2 Marja Van Waes 2017-11-05 22:45:01 CET

Here diskdrake has only had problems with USB-keys on which isos had been dumped, not with other USB-keys.

As a workaround, you can use isodumper to format USB-keys which aren't shown by diskdrake, see: 
https://wiki.mageia.org/en/IsoDumper_Writing_ISO_images_on_USB_sticks#Formatting

Assignee: bugsquad => mageiatools
Summary: drakconf cannot see a USB key newly connected to the computer => diskdrake cannot see a USB key newly connected to the computer
CC: (none) => marja11, pterjan
Source RPM: drakconf-13.16-1.mga6 => drakxtools

Comment 3 Aurelien Oudelet 2020-08-05 16:46:59 CEST

Is it still valid in Mageia 7, Cauldron ?



This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL) within 3 weeks from 2020-08-05.

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 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was 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

CC: (none) => ouaurelien

Comment 4 Aurelien Oudelet 2020-08-29 18:42:56 CEST

Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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