Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7568 - udev / hal - fail to mount camera

Attached to Project: Arch Linux
Opened by Radu Potop (wooptoo) - Thursday, 05 July 2007, 22:58 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 06 March 2008, 23:05 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

After the upgrade to udev-113-1 and hal-0.5.9-1, I can't mount my camera anymore and get this error:
mount /dev/sdb1 /mnt/cam -t vfat
mount: /dev/sdb1: can't read superblock

udev-113-2 didn't solve this either.

dmesg|tail:
ASC=0x4 ASCQ=0x3
end_request: I/O error, dev sdb, sector 39
sd 8:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x3
end_request: I/O error, dev sdb, sector 39
FAT: unable to read boot sector
sd 8:0:0:0: Device not ready: <6>: Current: sense key=0x2
ASC=0x4 ASCQ=0x3
end_request: I/O error, dev sdb, sector 39
FAT: unable to read boot sector

I can mount it only if i remove the SD memory card from it.
I'm also using thunar-volman to automount devices, i think it's a udev issue since it won't mount even from the command line with hal stopped.

thunar-volman throws out this error:
Failed to mount "/org/freedesktop/Hal/devices/volume_part1_size_2059382272".
Given device "/org/freedesktop/Hal/devices/volume_part1_size_2059382272" is not a volume or drive.

Other devices like usb memory sticks, cds, etc work fine.
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Thursday, 06 March 2008, 23:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in kernel 2.6.24
Comment by Radu Potop (wooptoo) - Thursday, 05 July 2007, 23:01 GMT
edit:

More people had this problem: http://bbs.archlinux.org/viewtopic.php?id=34678

Also, after i unplug the camera a error appears on it's lcd saying that the SD card can't be read and it needs formatting. No luck after formatting either.
Comment by Roman Kyrylych (Romashka) - Wednesday, 11 July 2007, 16:08 GMT
Reopened on this request:
Same problem/same errors.
Comment by Radu Potop (wooptoo) - Sunday, 22 July 2007, 16:34 GMT
Can someone at least provide a PKGBUILD for udev-112 ? Didn't expect this issue to take so long to fix :(
Comment by Lone_Wolf (Lone_Wolf) - Tuesday, 24 July 2007, 17:40 GMT
Goto http://www.archlinux.org/packages/4083/ , choose cvs view, pkgbuild

version 1.139 was for udev 112 version.
select a diff between 1.142 (udev 113-2) and 1.139 and you can see the changes.
That should help you to revert the pkgbuild to 112.
Comment by Tobias Powalowski (tpowa) - Thursday, 16 August 2007, 20:16 GMT
status on this?
Comment by Radu Potop (wooptoo) - Thursday, 06 March 2008, 22:00 GMT
Bug not fixed.
Comment by Roman Kyrylych (Romashka) - Thursday, 06 March 2008, 22:02 GMT
@wooptoo: it has been more than half year since then - we close such old bugs if authors don't respont to "status?" comments ;)
what is your current version of udev?
Comment by Radu Potop (wooptoo) - Thursday, 06 March 2008, 22:37 GMT
Um... sorry.
I'm currently using udev 111. Udev 112 also works (although it's a bit slower), but any newer version has this bug. I simply can't mount the volume, i tried manually and also with HAL through thunar or nautilus. Same results. You can find the output errors in my initial post.
I will submit a detailed bug report to linux-hotplug mailing list, because i don't think this is related to Arch Linux.
Comment by Roman Kyrylych (Romashka) - Thursday, 06 March 2008, 22:40 GMT
just FYI - initscripts after 2008.03 will broke your system if you'll still use such old version of udev.
Comment by Radu Potop (wooptoo) - Thursday, 06 March 2008, 22:57 GMT
Fixed in kernel 2.6.24.
I kept using udev 111, because i thought it was something with the newer udev. It turns out it was a kernel bug. They only fixed it in 2.6.24.
This can be finally closed.

Loading...