| Summary: | udisksd doesn't mount 4TB USB hard drive | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | DariuszSki <linuxstuff> |
| Component: | RPM Packages | Assignee: | Base system maintainers <basesystem> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, marja11 |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | udisks | CVE: | |
| Status comment: | |||
|
Description
DariuszSki
2016-11-28 11:06:29 CET
Updating to say it affects x86_64, don't know about x86. Hardware:
All =>
x86_64 (In reply to DariuszSki from comment #0) > Description of problem: > > Having bought a HDD to dump camcorder footage to, I re-formatted it from > NTFS to ext4 without problem using gparted. However, I can't mount the 4TB > portable HDD, the drive constantly being accessed as if it's a spinning > device (BluRay), rather than a Hard Drive (as indicated by syslog). > * Where do you see it's accessed as BluRay device? > > > > Information from /var/log/syslog > > Nov 28 07:37:36 local kernel: [70536.432609] scsi 22:0:0:0: Direct-Access > WD Elements 25A3 1013 PQ: 0 ANSI: 6 > Nov 28 07:37:36 local kernel: [70536.434856] sd 22:0:0:0: [sdg] Spinning up > disk... The above line is normal, I see it, too, when attaching a, smaller, 2TB WD elements external HD, which is correctly detected and mounted. However, I don't see anything like > Nov 28 07:37:48 local kernel: [70548.461242] sd 22:0:0:0: [sdg] Very big > device. Trying to use READ CAPACITY(16). or like > local org.gtk.Private.UDisks2VolumeMonitor[4784]: index_parse.c:190: > indx_parse(): error opening /run/media/someuser/XXX/BDMV/index.bdmv * How exactly did you (try to) mount it? * Please run, as root, journalctl -af > journal.txt ** and attach the disk. ** While it's attached, run, in a different konsole/terminal, as user: lspicdrake -v > lspci.txt and lsusb > lsusb.txt ** try to mount and access that 4TB disk. ** After that fails, please attach: lspci.txt lsusb.txt and journal.txt to this bug report Keywords:
(none) =>
NEEDINFO (now assigning to a better maintainer group) Assignee:
pkg-bugs =>
basesystem This sounds like it's similar to the very annoying bluebirds firmware on some dvd drives. http://www.tim.id.au/blog/2009/09/03/solved-bluebirds-installer-on-lg-gh22ns50-dvd-rw/ It's intended to allow easy installation of the needed drivers in windows systems. I don't have any blueray devices, so don't know what software would normally be used to access one. I'd start by running harddrake2 with the drive connected, to see if it can id needed packages. To stop the drive being seen as a blueray drive on connection, the firmware will likely have to be updated. The info requested by Marja should help id the drive, which may make finding a way to update the firmware or some other workaround easier. CC:
(none) =>
davidwhodgins Just remembered. The workaround for the lg bluebird dvd fiasco is handled by installing usb_modeswitch and usb_modeswitch-data. DariuszSki, try installing those packages to see if there is a workaround already available for that drive. Marja, DariuszSki is correct that the drive is being seen as a blueray drive, as indicated by the system looking for the index.bdmv file. https://duckduckgo.com/l/?kh=-1&uddg=https%3A%2F%2Ffileinfo.com%2Fextension%2Fbdmv @ DariuszSki Closing as OLD, because you never replied to the comments above. Please reopen with more information if this bug is still valid for Mageia 6 or later. Status:
NEW =>
RESOLVED |