I believe there must be something wrong with Mageia 7-beta2 support for usb management in LipParted. Thus, I'm reporting this. Can't use a usb stick 3.0 in Mageia 7-beta2 up to date. The problem seems to be related to a specific usb 3.0 device. Another distro seems not to have problems with the same pendrive. Also this pendrive had the Mageia 7-beta2 iso which I used to install this very Mageia 7-beta2 without problems. Tried isodumper and dd to create a bootable usb with the new Mageia 7 beta 3. dd returns no error messages but do not generate a bootable device and isodumper returns IO errors. Tried simply copying the Mageia 7beta3 iso to the pendrive to be used in another distro (another computer) for dd, but the very copying failed and the pendrive gets unmounted. Tested copying in another distro and it works well. Tried gparted and partition manager for reformating the pendrive. Gparted does not allow for erasing partitions. I've tried erasing and creating a partition with partition manager and got the following messages (/dev/sdc): # LC_ALL=C partitionmanager QStandardPaths: wrong ownership on runtime directory /run/user/1001, 1001 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1001, 1001 instead of 0 QStandardPaths: wrong ownership on runtime directory /run/user/1001, 1001 instead of 0 Loaded backend plugin: "pmlibpartedbackendplugin" "Using backend plugin: pmlibpartedbackendplugin (1)" "Scanning devices..." getting smart status failed for "/dev/nvme0n1" : Operation not supported "Device found: NVMe Device" "Partition ‘/dev/nvme0n1p1’ is not properly aligned (last sector: 28131056, modulo: 1777)." "Device found: ATA ST1000LX015-1U71" "Partition ‘/dev/sda1’ is not properly aligned (last sector: 1953525134, modulo: 1423)." "Device found: ATA WDC WDS480G2G0B-" "Partition ‘/dev/sdb1’ is not properly aligned (last sector: 937721666, modulo: 1859)." "Device found: Kingston DataTraveler 3.0" getting smart status failed for "/dev/sdc" : Operation not supported "Scan finished." "Add operation: Delete partition ‘/dev/sdc1’ (7.20 GiB, fat32)" "Add operation: Create a new partition (7.20 GiB, fat32) on ‘/dev/sdc’" "Applying operations..." "LibParted Exception: Error opening /dev/sdc: No such file or directory" Backtrace has 10 calls on stack: 10: /lib64/libparted.so.2(ped_assert+0x32) [0x7fa4b9a399a2] 9: /lib64/libparted.so.2(ped_disk_destroy+0x41) [0x7fa4b9a3c7b1] 8: /usr/lib64/qt5/plugins/libpmlibpartedbackendplugin.so(+0xc0d7) [0x7fa4ba2e10d7] 7: /usr/lib64/qt5/plugins/libpmlibpartedbackendplugin.so(+0xbd4b) [0x7fa4ba2e0d4b] 6: /lib64/libkpmcore.so.7(+0xa1f8f) [0x7fa4c315bf8f] 5: /lib64/libkpmcore.so.7(_ZN9Operation7executeER6Report+0xa9) [0x7fa4c314e719] 4: /lib64/libkpmcore.so.7(_ZN15OperationRunner3runEv+0x737) [0x7fa4c313cfe7] 3: /lib64/libQt5Core.so.5(+0xbd2a3) [0x7fa4c18672a3] 2: /lib64/libpthread.so.0(+0x904c) [0x7fa4c0a8204c] 1: /lib64/libc.so.6(clone+0x3f) [0x7fa4c155ecaf] Aborted
Assuming our kernel & drivers maintainers are best equipped to debug this issue, assigning to them.
Assignee: bugsquad => kernelCC: (none) => marja11
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."
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?
What is the current state?
CC: (none) => fri
(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) => FIXEDStatus: NEW => RESOLVED