| Summary: | Cannot handle a usb 3.0 with gparted and partitionmanager + other problems | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Adelson Oliveira <adelson.oliveira> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bequimao.de, fri, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gparted + partition manager | CVE: | |
| Status comment: | |||
|
Description
Adelson Oliveira
2019-04-27 22:45:12 CEST
Assuming our kernel & drivers maintainers are best equipped to debug this issue, assigning to them. Assignee:
bugsquad =>
kernel After last updates, including kernel and partitionmanager, this is what is output if I try to manage a usb 3.0 with partitionmanager: $ LC_ALL=C partitionmanager Loaded backend plugin: "pmsfdiskbackendplugin" QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." "Device found: INTEL MEMPEK1W016GA" smartctl initialization failed for "/dev/nvme0n1" : No such file or directory error during smart output parsing for "/dev/nvme0n1" : No such file or directory "Partition ‘/dev/nvme0n1p1’ is not properly aligned (last sector: 28131056, modulo: 1777)." "Device found: ST1000LX015-1U7172" smartctl initialization failed for "/dev/sda" : No such file or directory error during smart output parsing for "/dev/sda" : No such file or directory "Partition ‘/dev/sda1’ is not properly aligned (last sector: 1953525134, modulo: 1423)." "Device found: WDC WDS480G2G0B-00EPW0" smartctl initialization failed for "/dev/sdb" : No such file or directory error during smart output parsing for "/dev/sdb" : No such file or directory "Partition ‘/dev/sdb1’ is not properly aligned (last sector: 937721666, modulo: 1859)." "Device found: DataTraveler 3.0" smartctl initialization failed for "/dev/sdc" : No such file or directory error during smart output parsing for "/dev/sdc" : No such file or directory "Scan finished." "Add operation: Delete partition ‘/dev/sdc1’ (7.20 GiB, unknown)" "Applying operations..." "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." "Device found: INTEL MEMPEK1W016GA" smartctl initialization failed for "/dev/nvme0n1" : No such file or directory error during smart output parsing for "/dev/nvme0n1" : No such file or directory "Partition ‘/dev/nvme0n1p1’ is not properly aligned (last sector: 28131056, modulo: 1777)." "Device found: ST1000LX015-1U7172" smartctl initialization failed for "/dev/sda" : No such file or directory error during smart output parsing for "/dev/sda" : No such file or directory "Partition ‘/dev/sda1’ is not properly aligned (last sector: 1953525134, modulo: 1423)." "Device found: WDC WDS480G2G0B-00EPW0" smartctl initialization failed for "/dev/sdb" : No such file or directory error during smart output parsing for "/dev/sdb" : No such file or directory "Partition ‘/dev/sdb1’ is not properly aligned (last sector: 937721666, modulo: 1859)." "Device found: DataTraveler 3.0" smartctl initialization failed for "/dev/sdc" : No such file or directory error during smart output parsing for "/dev/sdc" : No such file or directory "Scan finished."
Ulrich Beckmann
2019-05-04 10:37:29 CEST
CC:
(none) =>
bequimao.de There has been updates in kernel and other components. Can't say this has something to do with the new scenario. Today, I could use partitionmanager to format two pendrives, a 2.0 and a 3.0 usb devices. I've used dd to as, dd if=Mageia7-beta3 of=/dev/sdc (no bs choice) to do it. It is insteresting that the dd didn't generate a bootable device for the 3.0 usb when I plug it into a 2.0 usb entry. It worked fine in a 3.0 usb entry. I really don't know if this is the expected for the usb operations .... As for today, mageia 7 beta 3/ RC 1 has problems to mount pendrives 3.0/3.1 when plugged in 2.0 ports. Upon plugging a 3.0 pendrive in a 2.0 USB port, hotplug keeps on finding and missing the device. The user usually has not enough time to click on "open it ...", but even if he/she does it, the system doesn't keep it mounted for a long time... Since this answer from english forum https://forums.mageia.org/en/viewtopic.php?f=7&t=12808&p=75043&hilit=pendrive#p75046 I kind of thought this is a mageia's documented feature and did not update this bug. However, what if some one has no USB 3.0/3.1 port to work with? I think mageia's won't be able to provide support to the 3.0 pendrive. Is this a good choice? (In reply to Morgan Leijström from comment #6) > What is the current state? As far as I know, there's been no change at all. I use usb 2 for usb 2 pendrives and usb 3 for those pendrives usb 3. Today, I've noticed Pendrives 3.0 can now be plugged in USB 2.0 ports in Mageia 8. Don't know when the problem has been solved. Thanks. As for me, the bug is solved. Should I change its status or this is done by the administrator? Good. Works for me too. Resolution:
(none) =>
FIXED |