[PC-BSD Testing] PCBSD 9.0-RC1 USB Mount Problem (continued)

Paul Dufresne dufresnep at gmail.com
Tue Nov 1 08:46:41 PDT 2011


Now that I said that (too) much... maybe adding my /var/log/messages
last lines would help some figure out something:
Nov  1 11:04:54 pcbsd-3091 kernel: ada0: <ST3160815AS 3.AAD> ATA-7
SATA 1.x device
Nov  1 11:04:54 pcbsd-3091 kernel: ada0: 150.000MB/s transfers (SATA,
UDMA5, PIO 8192bytes)
Nov  1 11:04:54 pcbsd-3091 kernel: ada0: 152627MB (312581808 512 byte
sectors: 16H 63S/T 16383C)
Nov  1 11:04:54 pcbsd-3091 kernel: cd0 at ata0 bus 0 scbus0 target 0 lun 0
Nov  1 11:04:54 pcbsd-3091 kernel: cd0: <Optiarc DVD RW AD-7190A 1.05>
Removable CD-ROM SCSI-0 device
Nov  1 11:04:54 pcbsd-3091 kernel: cd0: 66.700MB/s transfers (UDMA4,
ATAPI 12bytes, PIO 65534bytes)
Nov  1 11:04:54 pcbsd-3091 kernel: cd0: Attempt to query device size
failed: NOT READY, Medium not present - tray closed
Nov  1 11:04:54 pcbsd-3091 kernel: ada0: Previously was known as ad4
Nov  1 11:04:54 pcbsd-3091 kernel: Timecounter "TSC" frequency
2666642260 Hz quality 1000
Nov  1 11:04:54 pcbsd-3091 kernel: Root mount waiting for: usbus4
Nov  1 11:04:54 pcbsd-3091 kernel: Root mount waiting for: usbus4
Nov  1 11:04:54 pcbsd-3091 kernel: uhub4: 8 ports with 8 removable, self powered
Nov  1 11:04:54 pcbsd-3091 kernel: Root mount waiting for: usbus4
Nov  1 11:04:54 pcbsd-3091 kernel: Trying to mount root from
ufs:/dev/label/rootfs0 [rw,noatime]...
Nov  1 11:04:54 pcbsd-3091 kernel: ugen1.2: <Logitech> at usbus1
Nov  1 11:04:54 pcbsd-3091 kernel: ums0: <Logitech USB-PS2 Optical
Mouse, class 0/0, rev 2.00/13.00, addr 2> on usbus1
Nov  1 11:04:54 pcbsd-3091 kernel: ums0: 4 buttons and [XYZ] coordinates ID=0
Nov  1 11:04:54 pcbsd-3091 kernel: Cuse4BSD v0.1.21 @ /dev/cuse
Nov  1 11:04:54 pcbsd-3091 kernel: WARNING: attempt to
domain_add(bluetooth) after domainfinalize()
Nov  1 11:04:55 pcbsd-3091 kernel: .
Nov  1 11:04:56 pcbsd-3091 avahi-daemon[1757]: WARNING: No NSS support
for mDNS detected, consider installing nss-mdns!
Nov  1 11:04:59 pcbsd-3091 dbus[1714]: [system] Activating service
name='org.freedesktop.ConsoleKit' (using servicehelper)
Nov  1 11:04:59 pcbsd-3091 dbus[1714]: [system] Activating service
name='org.freedesktop.PolicyKit1' (using servicehelper)
Nov  1 11:05:00 pcbsd-3091 dbus[1714]: [system] Successfully activated
service 'org.freedesktop.PolicyKit1'
Nov  1 11:05:00 pcbsd-3091 dbus[1714]: [system] Successfully activated
service 'org.freedesktop.ConsoleKit'
Nov  1 11:05:11 pcbsd-3091 sudo:     root : TTY=unknown ; PWD=/root ;
USER=root ; COMMAND=/usr/local/bin/pc-fbsdupdatecheck
Nov  1 11:06:00 pcbsd-3091 sudo:     root : TTY=unknown ; PWD=/root ;
USER=root ; COMMAND=/usr/local/bin/pc-fbsdupdatecheck
Nov  1 11:06:19 pcbsd-3091 kernel: drm1: <ATI Radeon QD R100> on vgapci1
Nov  1 11:06:19 pcbsd-3091 kernel: info: [drm] Initialized radeon
1.31.0 20080613
Nov  1 11:06:22 pcbsd-3091 sudo:     root : TTY=unknown ; PWD=/root ;
USER=root ; COMMAND=/usr/local/bin/pc-fbsdupdatecheck
Nov  1 11:06:31 pcbsd-3091 dbus[1714]: [system] Activating service
name='org.freedesktop.UPower' (using servicehelper)
Nov  1 11:06:31 pcbsd-3091 dbus[1714]: [system] Successfully activated
service 'org.freedesktop.UPower'
Nov  1 11:06:32 pcbsd-3091 gdm-simple-greeter[6203]: Gtk-WARNING:
gtkwidget.c:5683: widget not within a GtkWindow
Nov  1 11:06:43 pcbsd-3091 gnome-keyring-daemon[6226]: couldn't
allocate secure memory to keep passwords and or keys from being
written to the disk
Nov  1 11:06:45 pcbsd-3091 gnome-keyring-daemon[6228]: couldn't set
environment variable in session: The name org.gnome.SessionManager was
not provided by any .service files
Nov  1 11:06:45 pcbsd-3091 gnome-keyring-daemon[6228]: couldn't set
environment variable in session: The name org.gnome.SessionManager was
not provided by any .service files
Nov  1 11:06:45 pcbsd-3091 gnome-keyring-daemon[6228]: couldn't set
environment variable in session: The name org.gnome.SessionManager was
not provided by any .service files
Nov  1 11:06:46 pcbsd-3091 pulseaudio[6332]: module.c: module-detect
is deprecated: Please use module-udev-detect instead of module-detect!
Nov  1 11:06:46 pcbsd-3091 sudo:     paul : TTY=unknown ;
PWD=/usr/home/paul ; USER=root ;
COMMAND=/usr/local/bin/pc-fbsdupdatecheck
Nov  1 11:06:46 pcbsd-3091 pulseaudio[6332]: oss-util.c: '/dev/dsp2'
doesn't support full duplex
Nov  1 11:06:54 pcbsd-3091 sudo:     paul : TTY=unknown ;
PWD=/usr/home/paul ; USER=root ; COMMAND=/usr/local/bin/life-preserver
-tray
Nov  1 11:07:53 pcbsd-3091 sudo:     paul : 1 incorrect password
attempt ; TTY=pts/0 ; PWD=/usr/home/paul ; USER=root ;
COMMAND=/usr/local/bin/taxipilot
Nov  1 11:08:59 pcbsd-3091 kernel: pid 6289 (pcmanfm), uid 1001:
exited on signal 11
Nov  1 11:14:42 pcbsd-3091 sudo:     paul : TTY=pts/2 ;
PWD=/usr/home/paul ; USER=root ; COMMAND=/bin/csh
Nov  1 11:14:47 pcbsd-3091 kernel: tun0: link state changed to UP
Nov  1 11:15:07 pcbsd-3091 ppp[8025]: tun0: Warning: 0.0.0.0/0: Change
route failed: errno: No such process
Nov  1 11:21:06 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4
Nov  1 11:21:06 pcbsd-3091 kernel: umass0: <FLASH Drive SKUSB20, class
0/0, rev 2.00/0.00, addr 2> on usbus4
Nov  1 11:21:06 pcbsd-3091 kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0000
Nov  1 11:21:06 pcbsd-3091 kernel: umass0:3:0:-1: Attached to scbus3
Nov  1 11:21:06 pcbsd-3091 kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Nov  1 11:21:06 pcbsd-3091 kernel: da0: <FLASH Drive SK_USB20 1.00>
Removable Direct Access SCSI-2 device
Nov  1 11:21:06 pcbsd-3091 kernel: da0: 40.000MB/s transfers
Nov  1 11:21:06 pcbsd-3091 kernel: da0: 7830MB (16035840 512 byte
sectors: 255H 63S/T 998C)
Nov  1 11:21:07 pcbsd-3091 amountd: CREATE da0
Nov  1 11:21:08 pcbsd-3091 amountd: CREATE da0s1
Nov  1 11:21:44 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4 (disconnected)
Nov  1 11:21:44 pcbsd-3091 kernel: umass0: at uhub4, port 2, addr 2
(disconnected)
Nov  1 11:21:44 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): lost device
- 0 outstanding
Nov  1 11:21:44 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): removing device entry
Nov  1 11:21:44 pcbsd-3091 amountd: DESTROY da0
Nov  1 11:21:44 pcbsd-3091 amountd: DESTROY da0s1
Nov  1 11:21:52 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4
Nov  1 11:21:52 pcbsd-3091 kernel: umass0: <FLASH Drive SKUSB20, class
0/0, rev 2.00/0.00, addr 2> on usbus4
Nov  1 11:21:52 pcbsd-3091 kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0000
Nov  1 11:21:52 pcbsd-3091 kernel: umass0:3:0:-1: Attached to scbus3
Nov  1 11:21:52 pcbsd-3091 kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Nov  1 11:21:52 pcbsd-3091 kernel: da0: <FLASH Drive SK_USB20 1.00>
Removable Direct Access SCSI-2 device
Nov  1 11:21:52 pcbsd-3091 kernel: da0: 40.000MB/s transfers
Nov  1 11:21:52 pcbsd-3091 kernel: da0: 7830MB (16035840 512 byte
sectors: 255H 63S/T 998C)
Nov  1 11:21:53 pcbsd-3091 amountd: CREATE da0
Nov  1 11:21:53 pcbsd-3091 amountd: CREATE da0s1
Nov  1 11:22:09 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4 (disconnected)
Nov  1 11:22:09 pcbsd-3091 kernel: umass0: at uhub4, port 2, addr 2
(disconnected)
Nov  1 11:22:09 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): lost device
- 0 outstanding
Nov  1 11:22:09 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): removing device entry
Nov  1 11:22:09 pcbsd-3091 amountd: DESTROY da0
Nov  1 11:22:09 pcbsd-3091 amountd: DESTROY da0s1
Nov  1 11:22:22 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4
Nov  1 11:22:22 pcbsd-3091 kernel: umass0: <FLASH Drive SKUSB20, class
0/0, rev 2.00/0.00, addr 2> on usbus4
Nov  1 11:22:22 pcbsd-3091 kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0000
Nov  1 11:22:22 pcbsd-3091 kernel: umass0:3:0:-1: Attached to scbus3
Nov  1 11:22:22 pcbsd-3091 kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Nov  1 11:22:22 pcbsd-3091 kernel: da0: <FLASH Drive SK_USB20 1.00>
Removable Direct Access SCSI-2 device
Nov  1 11:22:22 pcbsd-3091 kernel: da0: 40.000MB/s transfers
Nov  1 11:22:22 pcbsd-3091 kernel: da0: 7830MB (16035840 512 byte
sectors: 255H 63S/T 998C)
Nov  1 11:22:23 pcbsd-3091 amountd: CREATE da0
Nov  1 11:22:24 pcbsd-3091 amountd: CREATE da0s1
Nov  1 11:22:28 pcbsd-3091 kernel: pid 6401 (gvfs-hal-volume-mon), uid
1001: exited on signal 11
Nov  1 11:32:38 pcbsd-3091 kernel: ugen4.2: <FLASH> at usbus4 (disconnected)
Nov  1 11:32:38 pcbsd-3091 kernel: umass0: at uhub4, port 2, addr 2
(disconnected)
Nov  1 11:32:38 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): lost device
- 0 outstanding
Nov  1 11:32:38 pcbsd-3091 kernel: (da0:umass-sim0:0:0:0): removing device entry
Nov  1 11:32:38 pcbsd-3091 amountd: DESTROY da0
Nov  1 11:32:38 pcbsd-3091 amountd: DESTROY da0s1
Nov  1 11:32:38 pcbsd-3091 kernel: deget(): pcbmap returned 6
Nov  1 11:32:38 pcbsd-3091 last message repeated 2 times
Nov  1 11:33:00 pcbsd-3091 kernel: ugen4.2: <USB MF> at usbus4
Nov  1 11:33:00 pcbsd-3091 kernel: umass0: <Internal Device> on usbus4
Nov  1 11:33:00 pcbsd-3091 kernel: umass0:  SCSI over Bulk-Only; quirks = 0x4000
Nov  1 11:33:00 pcbsd-3091 kernel: umass0:3:0:-1: Attached to scbus3
Nov  1 11:33:00 pcbsd-3091 kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
Nov  1 11:33:00 pcbsd-3091 kernel: da0: <SigmaTel MSCN 0100> Removable
Direct Access SCSI-4 device
Nov  1 11:33:00 pcbsd-3091 kernel: da0: 40.000MB/s transfers
Nov  1 11:33:00 pcbsd-3091 kernel: da0: 1928MB (493568 4096 byte
sectors: 255H 63S/T 30C)
Nov  1 11:33:00 pcbsd-3091 amountd: CREATE da0
Nov  1 11:33:55 pcbsd-3091 kernel: deget(): pcbmap returned 6
Nov  1 11:33:56 pcbsd-3091 last message repeated 5 times
[root at pcbsd-3091] ~#


2011/11/1, Paul Dufresne <dufresnep at gmail.com>:
> I too would have some problems with my other 8 GB usb keys.
> Same mark same model. One would work fine, the other not.
>
> One would say DBUS error org.freedesktop.DBUS.Error.NoReply: Message
> did not receive a reply.
>
> dmesg last lines would show:
> ugen4.2: <FLASH> at usbus4
> umass0: <FLASH Drive SKUSB20, class 0/0, rev 2.00/0.00, addr 2> on usbus4
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:3:0:-1: Attached to scbus3
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: <FLASH Drive SK_USB20 1.00> Removable Direct Access SCSI-2 device
> da0: 40.000MB/s transfers
> da0: 7830MB (16035840 512 byte sectors: 255H 63S/T 998C)
> ugen4.2: <FLASH> at usbus4 (disconnected)
> umass0: at uhub4, port 2, addr 2 (disconnected)
> (da0:umass-sim0:0:0:0): lost device - 0 outstanding
> (da0:umass-sim0:0:0:0): removing device entry
> ugen4.2: <FLASH> at usbus4
> umass0: <FLASH Drive SKUSB20, class 0/0, rev 2.00/0.00, addr 2> on usbus4
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:3:0:-1: Attached to scbus3
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: <FLASH Drive SK_USB20 1.00> Removable Direct Access SCSI-2 device
> da0: 40.000MB/s transfers
> da0: 7830MB (16035840 512 byte sectors: 255H 63S/T 998C)
> pid 6401 (gvfs-hal-volume-mon), uid 1001: exited on signal 11
> [root at pcbsd-3091] ~#
>
> Well, I wanted to say something too about msdos filesystem support.
> When trying to 'mkfs.msdos' on a usb key of 2GB, I would have two
> errors... something like not enough sectors.
>
> Was thinking about finding where mkfs.msdos was coming from, and see
> if it is not an old version that would not know how to handle 2048
> bytes sectors (that what fdisk reported for this usb key).
>
> But I did not figure out from which port, mkfs.msdos is coming from yet.
>
> Let me retry to give some meat to this message:
> hum... cannot redo... last time I saved the partition table empty in
> the hope that XP would
> be able to format it... it did not.
>
> Now, I seems to not be able to see the disk anymore:
> dmesg | tail:
> umass0: <FLASH Drive SKUSB20, class 0/0, rev 2.00/0.00, addr 2> on usbus4
> umass0:  SCSI over Bulk-Only; quirks = 0x0000
> umass0:3:0:-1: Attached to scbus3
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: <FLASH Drive SK_USB20 1.00> Removable Direct Access SCSI-2 device
> da0: 40.000MB/s transfers
> da0: 7830MB (16035840 512 byte sectors: 255H 63S/T 998C)
> pid 6401 (gvfs-hal-volume-mon), uid 1001: exited on signal 11
> ugen4.2: <FLASH> at usbus4 (disconnected)
> umass0: at uhub4, port 2, addr 2 (disconnected)
> (da0:umass-sim0:0:0:0): lost device - 0 outstanding
> (da0:umass-sim0:0:0:0): removing device entry
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> ugen4.2: <USB MF> at usbus4
> umass0: <Internal Device> on usbus4
> umass0:  SCSI over Bulk-Only; quirks = 0x4000
> umass0:3:0:-1: Attached to scbus3
> da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
> da0: <SigmaTel MSCN 0100> Removable Direct Access SCSI-4 device
> da0: 40.000MB/s transfers
> da0: 1928MB (493568 4096 byte sectors: 255H 63S/T 30C)
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> deget(): pcbmap returned 6
> [root at pcbsd-3091] ~#
> [root at pcbsd-3091] ~# ls -lh /dev/da*
> crw-rw-rw-  1 root  operator    0, 126 Nov  1 11:33 /dev/da0
> [root at pcbsd-3091] ~# fdisk /dev/da0
> fdisk: could not detect sector size
> [root at pcbsd-3091] ~#
>
> 2011/11/1, Kris Moore <kris at pcbsd.org>:
>> On 10/26/2011 15:18, Ian Robinson wrote:
>>> Ian Robinson previous said:
>>>
>>> Re:  USB mounting -- Although the system recognizes that a USB thumb
>>> drive or USB hard disk has been connected (and little graphic window
>>> pops up near the clock), the system generates an error and will not
>>> mount USB stick or USB [hard] drive.
>>>
>>> Following up on this, the USB stick was formated FAT32; the USB Hard
>>> Disk was formatted NTFS.  The specific error message for the FAT32
>>> memory stick was:
>>>
>>> "An error occurred while accessing '244.7 MB Removable Media', the
>>> system responded: org.freebsd.HAL.Device.Volume.UnknownFailure:
>>> mount_msdosfs:  C: no such file or directory"
>>>
>>> I can mount the drives from the command line.
>>>
>>> Since one must be root to execute a mount, I thus wonder whether this
>>> is a rights issue where the mounting routine requires some switch to
>>> root to complete the mount.   I do not remember having this problem
>>> with the BETA versions.
>>>
>>> --
>>> Ian Robinson
>>> Salem, Ohio
>>>
>>>
>>>
>>> _______________________________________________
>>> Testing mailing list
>>> Testing at lists.pcbsd.org
>>> http://lists.pcbsd.org/mailman/listinfo/testing
>>
>> Fixed this for RC2. In the meantime you can fix by editing /etc/profile
>> and /etc/csh.cshrc. Make sure to un-comment the LANG=en_US.UTF-8 in both.
>>
>> --
>> Kris Moore
>> PC-BSD Software
>> iXsystems
>>
>>
>


More information about the Testing mailing list