Mount foreign usb storage

The aim is to mount any usb storage (say, not mine one) with write rights for normal user. So, use cases with fstab and udev automounting are not acceptable.
OK, I have found this https://wiki.archlinux.org/index.php/US … ge_Devices wiki page and have tried to follow. In particular, I have:
~ $ sudo blkid -o list -c /dev/null | grep sdc1
/dev/sdc1 ext4 (not mounted) 15bfa2da-6214-4228-851e-c1207b74fc34
~ $ sudo mount -o gid=users,fmask=113,dmask=002 /dev/sdc1 /media
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg shows "Unrecognized mount option" for all these three options (I have tried to remove them one by one). Apparently, ext4 just hasn't these options. But - how to mount?

Congratulations on your choice of Os ;-)
To solve this problem you can try and create a directory called /rmdisk , then start vold running:
/etc/init.d/volmgt stop
/etc/init.d/volmgt start
if you are lucky your USB flash will show up under /rmdisk/<name> after a few seconds.
If not you should be able to see the flash with cfgadm, which list the status of USB ports (among other things).
Solaris should automatically create a /dev/dsk/ and /dev/rdsk/ entries for your flash memory, if its not automatically mounted by vold, try and stop vold using
/etc/init.d/volmgt stop
Then do a cd /dev/dsk and run an ls -lart, the USB devices should be among the last devices in that list, then mount it using:
mount -F pcfs /dev/dsk/<device> /some/directory
the device should end with s2 or p2, some flash devices might also need :c, aka /dev/dsk/<device>:c, it depends how its configured.
See man mount_pcfs for more information...
Hope this helps a bit (:
//Magnus

Similar Messages

  • Auto-mounting USB storage devices doesn't work

    Hi all,
    I have some problems with the auto-mounting of USB storage devices. I already installed udisks and ntfs-3g.
    When I connect the external device (it's an external hard disk WD My Passport 500GB, but I have the same problem with a SanDisk USB stick 8GB) the auto-mount doesn't work. I see a shorcut in the left panel of Thunar but if I try to use it Thunar crash without any message error.
    I try with the manual mount and it works, but the left panel of Thunar continue to have the same problem.
    In the italian Arch forum a friend suggest me to open Thunar from bash and close it. If I do it I receive this error log:
    $ thunar
    thunar: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt14error_categoryD2Ev, version GLIBCXX_3.4.15
    and this is the reply of dmesg command:
    [ 340.826768] usb 1-1: new high speed USB device number 2 using ehci_hcd
    [ 341.591397] Initializing USB Mass Storage driver...
    [ 341.592166] scsi6 : usb-storage 1-1:1.0
    [ 341.592345] usbcore: registered new interface driver usb-storage
    [ 341.592349] USB Mass Storage support registered.
    [ 341.599805] usbcore: registered new interface driver uas
    [ 342.591094] scsi 6:0:0:0: Direct-Access WD My Passport 070A 1032 PQ: 0 ANSI: 4
    [ 342.591474] sd 6:0:0:0: Attached scsi generic sg1 type 0
    [ 342.592845] scsi 6:0:0:1: CD-ROM WD Virtual CD 070A 1032 PQ: 0 ANSI: 4
    [ 342.593048] scsi 6:0:0:1: Attached scsi generic sg2 type 5
    [ 342.594050] sd 6:0:0:0: [sdb] 975400960 512-byte logical blocks: (499 GB/465 GiB)
    [ 342.594814] scsi 6:0:0:2: Enclosure WD SES Device 1032 PQ: 0 ANSI: 4
    [ 342.595141] scsi 6:0:0:2: Attached scsi generic sg3 type 13
    [ 342.596546] sd 6:0:0:0: [sdb] Write Protect is off
    [ 342.596553] sd 6:0:0:0: [sdb] Mode Sense: 23 00 10 00
    [ 342.596557] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [ 342.599163] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [ 342.618228] sdb: sdb1
    [ 342.621039] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    [ 342.621046] sd 6:0:0:0: [sdb] Attached SCSI disk
    [ 342.665174] sr0: scsi3-mmc drive: 51x/51x caddy
    [ 342.665180] cdrom: Uniform CD-ROM driver Revision: 3.20
    [ 342.665447] sr 6:0:0:1: Attached scsi CD-ROM sr0
    [ 342.665654] ses 6:0:0:2: Attached Enclosure device
    [ 349.105348] [b]Thunar[996]: segfault at 0 ip b6de1660 sp bfe586f4 error 4 in libglib-2.0.so.0.2800.8[b6d6f000+ed000][/b]
    Do you have any suggestion?
    Thank you very much,
    Gianluca

    Are you using [testing]? Partially updated system?
    The error looks like you have a different version of gcc-libs / glibc than the app was built against.
    Last edited by Mr.Elendig (2011-06-20 19:16:33)

  • No USB storage automounting in LXDE

    I'm running LXDE on top of Arch. I have followed the wiki, but it still does not seem to automatically mount my USB storage devices.
    I can use dmesg to see that the device is inserted and recognized. I can manually mount the device and copy files.
    I have done the following:
    * Check the checkbox to automatically mount inserted storage devices in PCManFM
    * Ensure that udisks2 is installed
    * Add the policykit file described in the troubleshooting section of the PCManFM wiki (even though the problem it describes isn't exactly my problem)
    This thread appears to be completely obsolete, so though I read it I didn't glean anything actionable
    It isn't clear to me whether this thread is relevant to my interests; the resolution certainly isn't.
    I can use udiskie to automount the USB media. Maybe I'm dumb for thinking that LXDE (or PCManFM) should do it for me without having to run udiskie first, but I figured I'd ask in case there's an easier way I'm not aware of.

    jasonwryan wrote:If you are running systemd, and have an active session, then the polkit rule is unnecessary, unhelpful even.
    OK, good to know. I'll remove the rule.
    Thanks for the replies. Lucke, your guess makes sense...that would explain why all the LXDE info for automounting assumes it will just automagically work, even though it clearly doesn't.

  • Solaris 8 USB storage (2 tb)...can't mount

    Hello all,
    I have been trying for the past week to mount a 2 TB usb storage device that I built. It shows up when I type
    cd /dev/rdsk
    ls -l c*0 | grep usb
    I then tried to mount it with this command (vold turned off)
    mount -F pcfs /dev/dsk/c4t0d0s0:c /mnt
    it says no device or address.....
    so I typed iostat -En
    got this
    usb_sd1 Soft Errors: 3 Hard Errors: 0 Transport Errors: 0
    Vendor: Product: Combine 4HDD0702 Revision: 1278 Serial No:
    Size: 2000.43GB <2000431448064 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
    Illegal Request: 3 Predictive Failure Analysis: 0
    I need HELP!!!
    Thanks
    Kluesy

    Hello! First try using the motherboard ports to rule out a bad pci card. Then attache the drive and turn it on and open disk utility to see if it can repair it. If that doesn't work boot from the install cd and run disk utility from there to try and repair the drive. It has been formatted hasn't it? Tom

  • MOUNT USB STORAGE FOR VM BACKUP

    Hi, I just tried to mount USB Storage to my host with linux version.
    I detect it with fdisk -l and esxcli storage core device list | grep -i usb, after stopping usbarbitrator
    Result:
    /dev/disks #dmesg
    ScsiDevice: 3385: Successfully registered device "mpx.vmhba50:C0:T0:L0" from plugin "NMP" of type 0
    /dev/disks # esxcli storage core device list | grep -i usb
       Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
       Display Name: Local USB Direct-Access (mpx.vmhba50:C0:T0:L0)
    How can I get disk usable for perform a VM backup?

    hooya wrote:
    It's in debugging mode now, which is why I can adb push to the phone. The phone should (and has in the past) mounted USB storage even in debugging mode.
    That wouldn't change the fact that no other USB mass storage will mount either. I'm just using my phone as an example. USB Hard drives and my SD card reader don't show up either, but I can't do a "push" command to those like I can my phone...
    If you are wondering where your post went, I think you meant to hit the 'reply' link rather than the 'report' link.  It happens more often than you would think
    Edit: Oh, I see you already figured that out.
    Last edited by ewaller (2012-07-06 02:30:26)

  • V-cast setup issue; turning USB storage off

    .I am trying to use V-cast. Media Manager. 
    I've installed the app on my Droid X and on my desktop. I have the USB cable connected and  I have V-Case MM open on my desktop. Everything seems to be set to "Go" until I launch V-cast on the phone.
    When I do that I get the following error: "Memory card error, card mounted or not present.  Please make sure memory card is inserted and USB storage is turned off."
    I know the card is present, and mounted because the Droid X comes with the card already installed. 
    But I went to "Settings/SD card & phone storage settings" just to be sure.  It shows "Total space 14.87GB" and "Available space 14.80GB", and an "Mount SD Card" option.  "Internal phone storage" shows 6.22GB of available space.
    Now here's the rub. 
    When I plug in the USB cable in the SD card data information changes to "unavailable" and the "Unmount..." option changes to "Mount SD card".
    I'm guessing the issue is with the last part of the error message: "USB storage is turned off" but I don't know how to turn it on.
    What is USB storage?  Is it to off site storage option Verizon offers?  Am I required to "Subscribe" in order for this app to work?

    I believe you have to be in PC Mode not Mass Storage...  Try changing that under mount options.

  • Cypress - Other hardware - Cypress At2 USB Storage Adapter

    I have a USB Disk Enclosure that was working with Windows 8.1.  I recently installed a Windows Update optional update titled "Cypress -
    Other hardware - Cypress
    At2 USB Storage Adapter" and the next time I attempted to use the disk enclosure, it did not work.  When I connect the device the system makes a sound like it recognizes a device and the
    Device Manager display gets redrawn (refreshes), but no device shows up in Device Manager, Disk Manager or Safely Remove
    Hardware and Eject Media.  I have booted, also without helping the situation.  I am thinking that I should remove the update, but the "Uninstall and update" panel does not list and update title that matches the above.
    Update #1:  I found the same issue from two others on another MS forum that was posted yesterday: answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/crypress-a2b-usb-driver-update/96765e04-7f4a-42fb-bf37-ca98fa8fc0cc?rtAction=1395927639282
    I have had MS Support remoted into my system all morning and am being told they want $99 to run their tools to fix the problem.
    Update #2:  After hours chatting w/MS Support, no progress.  They ran lots of virus scans and repair procedures.  I did make the following observation.  When the USB Drive is connected, the system recognized something and chimes as described
    above.  What actually changes is that a "Cypress AT2 USB Storage Adapter" devices appears in the "Universal Serial Bus controllers" tree of Device Manager.  When the drive is unplugged, this device disappears.  Before the
    Win Update that I suspect caused the problem, the drive would appear as a drive also.  Note that the original behavior had the device appear as a disk, not as a removable device like a flash drive.  So Windows is recognizing the storage controller,
    but not presenting the attached disk as a drive in windows.  Oh well, back to the MS Support Chat......
    Update #3: I contacted MS Support a second time and pointed them at the “Cypress AT2 USB Storage Adapter”
    that appeared when the USB Enclosure was plugged in.  They poked around for a while and finally “Uninstalled” the device driver and had me unplg/plug the drive and BANG, the drive appeared. 
    I don’t know if it was the 5+ hours of work the first support person did or if that was the solution all along, but the drive works now. 
    Oh and one more thing, as I was completing the survey for the support, with not good ratings I might say, the remote control connected support person booted my computer right out from under me without a word of warning. 
    I guess there is more than one way to keep survey ratings high.

    Same problem. To solve you have to uninstall "Cypress At2 USB Storage Adapter"
    removing driver files with the option suggested by the dialog box of device manager. (I'm sorry i can't use the correct words because I own the italian version)
    After that, when you connect the drive, il will correctly mount the volume and do not appear Cypress device anymore.

  • [solved] USB storage devices problem

    Hello everyone. I have MSI Wind U270 and recently I've moved from Ubuntu 11.04 to Arch. I really like Arch so far but I have one quite big problem and I can't find any solution, so I hope someone here could help me.
    After I'd installed Arch, I tried to copy some file from/to USB flash drive. After just few seconds, transfer failed with information about I/O errors and USB flash drive disappeared along with any other USB drives connected at the same time but logitech usb mouse and keyboard continue to work.
    My first thought was that it's simply broken USB drive, but same thing was happening also when I tried to move some files from/to any other USB storage device that I have.
    Here is sample dmesg output after I connect device:
    [ 4799.189720] usb 1-2: new high-speed USB device number 4 using ehci_hcd
    [ 4799.369911] xhci_hcd 0000:06:00.0: PME# disabled
    [ 4799.369935] xhci_hcd 0000:06:00.0: setting latency timer to 64
    [ 4799.399707] ehci_hcd 0000:00:13.2: BAR 0: set to [mem 0xfeb48000-0xfeb480ff] (PCI address [0xfeb48000-0xfeb480ff])
    [ 4799.399754] ehci_hcd 0000:00:13.2: restoring config space at offset 0x1 (was 0x2b00000, writing 0x2b00013)
    [ 4799.399800] ehci_hcd 0000:00:13.2: PME# disabled
    [ 4799.399819] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    [ 4799.426731] ohci_hcd 0000:00:12.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    [ 4799.520213] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    [ 4799.690262] usbcore: registered new interface driver uas
    [ 4799.704107] Initializing USB Mass Storage driver...
    [ 4799.704420] scsi7 : usb-storage 1-2:1.0
    [ 4799.704959] usbcore: registered new interface driver usb-storage
    [ 4799.704966] USB Mass Storage support registered.
    [ 4801.166512] scsi 7:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 0 CCS
    [ 4801.168550] sd 7:0:0:0: [sdc] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
    [ 4801.169401] sd 7:0:0:0: [sdc] Write Protect is off
    [ 4801.169411] sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
    [ 4801.170332] sd 7:0:0:0: [sdc] No Caching mode page present
    [ 4801.170340] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [ 4801.175736] sd 7:0:0:0: [sdc] No Caching mode page present
    [ 4801.175747] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [ 4801.176962] sdc: sdc1
    [ 4801.181454] sd 7:0:0:0: [sdc] No Caching mode page present
    [ 4801.181465] sd 7:0:0:0: [sdc] Assuming drive cache: write through
    [ 4801.181471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
    [ 4801.388155] xhci_hcd 0000:06:00.0: PME# enabled
    [ 4801.439601] ehci_hcd 0000:00:13.2: PCI INT B disabled
    [ 4801.439657] ehci_hcd 0000:00:13.2: PME# enabled
    [ 4801.519628] ohci_hcd 0000:00:12.0: PCI INT A disabled
    [ 4802.346484] ohci_hcd 0000:00:13.0: PCI INT A disabled
    and when I start to copy some things to/from USB device this is what's happening:
    [ 4981.389262] ehci_hcd 0000:00:12.2: force halt; handshake ffffc90000c1e024 00004000 00000000 -> -110
    [ 4981.389271] ehci_hcd 0000:00:12.2: HC died; cleaning up
    [ 4981.389377] usb 1-2: USB disconnect, device number 4
    [ 4981.399810] sd 7:0:0:0: [sdc] Unhandled error code
    [ 4981.399820] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
    [ 4981.399826] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1f b4 7e 00 00 08 00
    [ 4981.399840] end_request: I/O error, dev sdc, sector 2077822
    [ 4981.399850] Buffer I/O error on device sdc1, logical block 259720
    [ 4981.399854] lost page write due to I/O error on sdc1
    [ 4981.404451] sd 7:0:0:0: [sdc] Unhandled error code
    [ 4981.404461] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
    [ 4981.404467] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 20 34 7e 00 00 f0 00
    [ 4981.404481] end_request: I/O error, dev sdc, sector 2110590
    [ 4981.404489] Buffer I/O error on device sdc1, logical block 263816
    [ 4981.404493] lost page write due to I/O error on sdc1
    [ 4981.404500] Buffer I/O error on device sdc1, logical block 263817
    [ 4981.404504] lost page write due to I/O error on sdc1
    [ 4981.404509] Buffer I/O error on device sdc1, logical block 263818
    [ 4981.404512] lost page write due to I/O error on sdc1
    [ 4981.404517] Buffer I/O error on device sdc1, logical block 263819
    [ 4981.404521] lost page write due to I/O error on sdc1
    [ 4981.404525] Buffer I/O error on device sdc1, logical block 263820
    [ 4981.404529] lost page write due to I/O error on sdc1
    [ 4981.404534] Buffer I/O error on device sdc1, logical block 263821
    [ 4981.404537] lost page write due to I/O error on sdc1
    [ 4981.404543] Buffer I/O error on device sdc1, logical block 263822
    [ 4981.404546] lost page write due to I/O error on sdc1
    [ 4981.404550] Buffer I/O error on device sdc1, logical block 263823
    [ 4981.404554] lost page write due to I/O error on sdc1
    [ 4981.444899] usb 1-4: USB disconnect, device number 3
    Next I thought – computer is broken. But it simply couldn't be true because in Ubuntu it's working.
    I wanted to test if USB transfer is working in other distros, so I downloaded few and tried:
    Ubuntu 11.04 – everything is working
    Ubuntu 11.10 – it's not working, exactly same errors as in Arch
    Ubuntu 12.04 Alpha 2 – it's not working
    Mint 11 – it's working
    Mint 12 – it's not working
    So one thing in common that I can think of is fact that USB transfer is working in distros using kernel <3.0 and is broken in those using kernel >=3.0.
    In dmesg output I can see ehci_hcd errors. When I remove this module before moving files, than everything is working fine apart from very slow transfer but it's obvious.
    I really hope that someone will be able to help with my problem.  I don't know if it's some bug or it's just some configuration error.
    EDIT: problems were caused by rts5139 module (card reader). Blacklisting that module solved all the problems.
    Last edited by wpb (2012-07-01 08:37:02)

    Ok,  so here is part of /var/log/messages.log with failed USB transfer:
    Feb 28 20:21:40 localhost kernel: [ 117.263584] usb 3-2: new high-speed USB device number 4 using ehci_hcd
    Feb 28 20:21:40 localhost mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:12.2/usb3/3-2"
    Feb 28 20:21:40 localhost kernel: [ 117.470130] ehci_hcd 0000:00:13.2: BAR 0: set to [mem 0xfeb48000-0xfeb480ff] (PCI address [0xfeb48000-0xfeb480ff])
    Feb 28 20:21:40 localhost kernel: [ 117.470251] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Feb 28 20:21:40 localhost kernel: [ 117.546266] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    Feb 28 20:21:40 localhost mtp-probe: bus: 3, device: 4 was not an MTP device
    Feb 28 20:21:42 localhost kernel: [ 119.687034] usbcore: registered new interface driver uas
    Feb 28 20:21:42 localhost kernel: [ 119.692675] Initializing USB Mass Storage driver...
    Feb 28 20:21:42 localhost kernel: [ 119.693029] scsi7 : usb-storage 3-2:1.0
    Feb 28 20:21:42 localhost kernel: [ 119.694285] usbcore: registered new interface driver usb-storage
    Feb 28 20:21:42 localhost kernel: [ 119.694294] USB Mass Storage support registered.
    Feb 28 20:21:43 localhost kernel: [ 120.353657] ohci_hcd 0000:00:13.0: PCI INT A disabled
    Feb 28 20:21:43 localhost kernel: [ 121.110815] scsi 7:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 0 CCS
    Feb 28 20:21:43 localhost kernel: [ 121.115125] sd 7:0:0:0: [sdc] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
    Feb 28 20:21:43 localhost kernel: [ 121.117132] sd 7:0:0:0: [sdc] Write Protect is off
    Feb 28 20:21:43 localhost kernel: [ 121.125243] sdc: sdc1
    Feb 28 20:21:43 localhost kernel: [ 121.130244] sd 7:0:0:0: [sdc] Attached SCSI removable disk
    Feb 28 20:21:44 localhost kernel: [ 121.570240] ehci_hcd 0000:00:13.2: PCI INT B disabled
    Feb 28 20:21:44 localhost ntfs-3g[1936]: Version 2012.1.15 external FUSE 28
    Feb 28 20:21:44 localhost ntfs-3g[1936]: Mounted /dev/sdc1 (Read-Write, label "", NTFS 3.1)
    Feb 28 20:21:44 localhost ntfs-3g[1936]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077,fmask=0177
    Feb 28 20:21:44 localhost ntfs-3g[1936]: Mount options: rw,nosuid,nodev,uhelper=udisks,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096,default_permissions
    Feb 28 20:21:44 localhost ntfs-3g[1936]: Global ownership and permissions enforced, configuration type 1
    Feb 28 20:22:11 localhost kernel: [ 148.692914] usb 3-2: USB disconnect, device number 4
    Feb 28 20:22:11 localhost kernel: [ 148.756937] sd 7:0:0:0: [sdc] Unhandled error code
    Feb 28 20:22:11 localhost kernel: [ 148.756947] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
    Feb 28 20:22:11 localhost kernel: [ 148.756954] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1e 2f f6 00 00 18 00
    Feb 28 20:22:11 localhost kernel: [ 148.756983] lost page write due to I/O error on sdc1
    Feb 28 20:22:11 localhost kernel: [ 148.757000] lost page write due to I/O error on sdc1
    Feb 28 20:22:11 localhost kernel: [ 148.757016] lost page write due to I/O error on sdc1
    Feb 28 20:22:11 localhost kernel: [ 148.761894] sd 7:0:0:0: [sdc] Unhandled error code
    Feb 28 20:22:11 localhost kernel: [ 148.761905] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
    Feb 28 20:22:11 localhost kernel: [ 148.761911] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1e 2f ae 00 00 08 00
    Feb 28 20:22:11 localhost kernel: [ 148.761939] lost page write due to I/O error on sdc1
    Feb 28 20:22:11 localhost kernel: [ 148.914173] usb 3-4: USB disconnect, device number 3
    Feb 28 20:22:24 localhost ntfs-3g[1936]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
    Feb 28 20:22:24 localhost ntfs-3g[1936]: Reading $BITMAP failed: Input/output error
    Feb 28 20:22:24 localhost ntfs-3g[1936]: Failed to allocate clusters: Input/output error
    Feb 28 20:22:24 localhost kernel: [ 161.862408] quiet_error: 2 callbacks suppressed
    Feb 28 20:22:24 localhost kernel: [ 161.862424] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862436] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862446] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862457] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862466] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862476] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862485] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862495] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862505] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost kernel: [ 161.862514] lost page write due to I/O error on sdc1
    Feb 28 20:22:24 localhost ntfs-3g[1936]: Unmounting /dev/sdc1 ()
    and here is complete /var/log/messages.log - I just started system and then tried to copy some files to USB drive:

  • What USB storage devices have a block size of 512 bytes?

    After pulling my hair out for weeks trying to get a usb hard drive to work with my new AirPort Extreme (802.11n), I ran across this
    http://docs.info.apple.com/article.html?artnum=305038
    AirPort Extreme (802.11n): USB storage device supported formats and protocols
    You can connect USB-based storage devices to an AirPort Extreme (802.11n). Learn which formats and protocols are supported.
    The AirPort Extreme (802.11n) supports USB storage devices that have a block size of 512 bytes, and are formatted as Mac OS Extended (HFS-plus), FAT16, or FAT32. Not all USB storage devices use a block size of 512 bytes.
    The AirPort Extreme (802.11n) shares storage devices based on the format used to initialize the storage device. For example, if HFS-plus formatting was used, AFP and SMB/CIFS protocols are used to share the device on the network. If FAT16 or FAT32 was used, SMB/CIFS protocols are used.
    The AirPort Extreme (802.11n) works with disks that have a single partition and are not software RAID volumes (no more than one volume per physical disk). If the disk is a self-contained RAID that presents itself to a computer as a single volume requiring no software support, then it is supported.
    Note: Use AirPort Disk Utility to discover and mount AirPort Extreme-based volumes over the network.
    Now, this information is not easily obtainable while
    shopping for a new usb hard drive. How do I find out which
    ones support this 512 byte block size????
    Would have bee nice to know that not all usb hard drives
    are supported by the AirPort Extreme (802.11n) before I
    purchased it.
    Thanks
    J Riley

    Duane posted a link to an unofficial 802.11n Airport Extreme Hard Drive Compatibility List.
    http://www.ifelix.co.uk/tech/8014.html
    Still not enough information to make an informed purchase that
    will work.

  • Latest Initrd not recognising USB storage devices?

    Just installed 2.6.30 with all the necessary files. Everything seemed fine, except for one thing: my external USB hard drive is no longer recognised on boot. Here is my fstab and my mkinitcpio.conf.
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs rw,noexec,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    UUID=139cf76d-425a-4c40-a5b1-bbbf22533d9a /boot ext4 defaults 0 1
    UUID=4eddd177-23f6-49ab-a8ad-d3e1303133e0 / ext4 defaults 0 1
    UUID=ED83-B8D4 /media/flash vfat rw,user,noauto 0 0
    #UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /iomega ext4 rw,noexec,nosuid 0 1
    UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /media/iomega ext4 rw,user,noauto 0 0
    UUID=da9e741f-3525-47c6-8c7f-edf1ded00e7a swap swap defaults 0 0
    As you can see from this, I originally had my external usb drive mounted on /iomega @ boot. However, since that no longer works, I have changed it to /media/iomega and let HAL mount it automatically when I fire up GNOME (the same way I have my flash drive set up). I used the original line with 2.6.29 with no problems.
    The strange thing is, the device is there, because, when it fails, I go into single user mode, remount / read-write and then run mount -a and the device appears with no errors. If I change the line so it doesn't do an fsck on boot, it doesn't mount the device, but I do get an error saying the device is not there. I can then mount it manually at the command prompt.
    The device is shown in /etc/blkid.tab and in /dev/disk/by-uuid.
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes, into the CPIO image, and additional
    # binaries a given user may wish. This is run first, so may
    # be used to override the actual binaries used in a given hook.
    # (Existing files are NOT overwritten is already added)
    # BINARIES are dependancy parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in anyway. This is useful for config files.
    # Some users may wish to include modprobe.conf for custom module options,
    # like so:
    # FILES="/etc/modprobe.conf"
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'modload' may be used in place of 'udev', but is not recommended
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    # This setup specifies all modules in the MODULES setting above.
    # No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    # This setup will autodetect all modules for your system and should
    # work as a sane default
    # HOOKS="base udev autodetect pata scsi sata filesystems"
    # This is identical to the above, except the old ide subsystem is
    # used for IDE devices instead of the new pata subsystem.
    # HOOKS="base udev autodetect ide scsi sata filesystems"
    # This setup will generate a 'full' image which supports most systems.
    # No autodetection is done.
    # HOOKS="base udev pata scsi sata usb filesystems"
    # This setup assembles an pata raid array with an encrypted root FS.
    # Note: See 'mkinitcpio -H raid' for more information on raid devices.
    # HOOKS="base udev pata raid encrypt filesystems"
    # This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev usb lvm2 filesystems"
    HOOKS="base udev autodetect pata scsi sata usb keymap filesystems"
    # COMPRESSION
    # Use this to compress the initramfs image. With kernels earlier than
    # 2.6.30, only gzip is supported, which is also the default. Newer kernels
    # support gzip, bzip2 and lzma.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    This is essentially the same as I had it in 2.6.29. I did initially use LZMA, since that gives slightly faster compression & decompression, but changed it back in case it was a timing issue (and rebuilt initrd). No joy. I also tried usbdelay=10 on boot, but again no difference.
    This isn't exactly a "show-stopper", since the device functions normally otherwise and everything else is fine, but it is annoying. I would much rather have this device available automatically on boot, so that it gets checked when the max mount count comes up.

    This was the bug update I received today:
    FS#15282 - [mkinitcpio] Latest initrd not recognising usb storage devices?
    User who did this - Thomas Bächler (brain0)
    You can never rely on external hard drives to show up "in time".
    The difference was that adding the "usb" hook to mkinitcpio used to add a 6 second delay on boot by default, this doesn't happen anymore. I think external drives simply don't belong in fstab, because there's too many possible race conditions. If you insist, you can try to force the usb storage driver to scan for devices sooner after detection, see the delay_use parameter to the usb-storage module.
    You're going to have to modify the delay_use parameter to get it to work. Be prepared for race conditions, though. I didn't bother myself as it wasn't a show stopper for me, so I've advised that it can be closed as a non-bug.
    ETA: usbdelay=10 doesn't work as that flag is apparently no longer recognised for some reason.
    ETTA: I've always used UUID in the fstab because udev can remap devices on boot (I've had fstab not recognising devices because of this).
    In case some people don't know, to see what the uuid for a device is, use the following:
    sudo tune2fs -l <device-name>
    Last edited by jamesbannon (2009-06-28 18:30:23)

  • USB Storage devices not working with kernel in repositories [Solved]

    I am experiencing a quite vexing problem with my USB Mass Storage devices, when I plug one in I get the following error in my dmesg:
    [ 1811.976758] usb 2-2: new high speed USB device number 5 using ehci_hcd
    [ 1812.101854] scsi7 : usb-storage 2-2:1.0
    [ 1813.102576] scsi 7:0:0:0: Direct-Access     Verbatim STORE N GO       2.68 PQ: 0 ANSI: 2
    [ 1813.103818] sd 7:0:0:0: [sdb] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
    [ 1813.104327] sd 7:0:0:0: [sdb] Write Protect is off
    [ 1813.104331] sd 7:0:0:0: [sdb] Mode Sense: 0b 00 00 08
    [ 1813.105567] sd 7:0:0:0: [sdb] No Caching mode page present
    [ 1813.105572] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 1813.107560] sd 7:0:0:0: [sdb] No Caching mode page present
    [ 1813.107565] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 1813.108340]  sdb: sdb1
    [ 1813.112180] sd 7:0:0:0: [sdb] No Caching mode page present
    [ 1813.112186] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [ 1813.112190] sd 7:0:0:0: [sdb] Attached SCSI removable disk
    [ 1813.196828] sdb: detected capacity change from 2003828736 to 0
    In the /dev/ folder on the device shows up, not the partitions. When I try to open it with cfdisk I get "FATAL ERROR: Cannot open disk drive". I am pretty sure it iss neither a hardware problem with my laptop or my usb devices, as they both work on my dual-booted Ubuntu. My usb ports in general seem to be functioning, I can still charge a phone through them and use my built in USB webcam.
    I am not sure where exactly this issue lies, it started after I upgraded to 3.0.7 (among other updates) from the normal repositories, but still persisted after I downgraded to 3.0.6.
    My attempts at Googling have so far revealed mainly hardware errors, which don't seem to fit with the devices working on another OS on the same pc.
    Thanks.
    Last edited by MartianW (2011-11-09 16:30:15)

    Same problem. I try to mount different devices. For each device same result.
    The file /var/log/error.log is full of this kind of messages:
    Nov  4 21:34:18 moria kernel: [  113.455195] sd 6:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:34:18 moria kernel: [  113.455200] sd 6:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:35:29 moria kernel: [  184.077728] sd 7:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:35:29 moria kernel: [  184.077736] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:35:29 moria kernel: [  184.080720] sd 7:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:35:29 moria kernel: [  184.080730] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:35:30 moria kernel: [  184.808109] sd 7:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:35:30 moria kernel: [  184.808116] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:41:10 moria kernel: [  525.107109] sd 8:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:41:10 moria kernel: [  525.107114] sd 8:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:41:10 moria kernel: [  525.110615] sd 8:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:41:10 moria kernel: [  525.110619] sd 8:0:0:0: [sdb] Assuming drive cache: write through
    Nov  4 21:41:11 moria kernel: [  525.841487] sd 8:0:0:0: [sdb] No Caching mode page present
    Nov  4 21:41:11 moria kernel: [  525.841491] sd 8:0:0:0: [sdb] Assuming drive cache: write through

  • USB Storage devices not being detected - device nodes not created?

    Hi,
    I've installed Arch Linux 64-bit on my Dell workstation, and it doesn't seem to be picking up my USB storage drives. Kernel version is 3.6.3-1.
    When I plug in a drive, I see in dmesg:
    [391147.657574] usb 1-8: new high-speed USB device number 6 using ehci_hcd
    However, I don't see anything else. There's nothing about creating device nodes, or anything like that.
    My output from `fstab -l` doesn't seem to mention anything about USB drives either, just my two system drives.
    [victorhooi@arch-precision ~]$ sudo fdisk -l
    [sudo] password for victorhooi:
    WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sda: 80.0 GB, 80000000000 bytes, 156250000 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0f2d18e3
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 718847 358400 7 HPFS/NTFS/exFAT
    /dev/sda2 718848 156246015 77763584 7 HPFS/NTFS/exFAT
    WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
    Disk /dev/sdb: 80.0 GB, 80000000000 bytes, 156250000 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x3a9c7de5
    Device Boot Start End Blocks Id System
    /dev/sdb1 1 156249999 78124999+ ee GPT
    My output from lsusb:
    [victorhooi@arch-precision ~]$ lsusb
    Bus 001 Device 006: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
    Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
    Bus 002 Device 003: ID 04b3:310d IBM Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Output from blkid - both before and after inserting the drive is identical:
    [victorhooi@arch-precision ~]$ blkid -o list -c /dev/null
    device fs_type label mount point UUID
    /dev/sda1 (not mounted)
    /dev/sda2 (not mounted)
    /dev/sdb1 /boot
    /dev/sdb2 (not mounted)
    /dev/sdb3 (not mounted)
    When I installed my kernel, I saw warnings about fsck.btrfs - not sure if that's related though:
    >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    ==> Building image from preset: 'default'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 3.6.5-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [autodetect]
    -> Running build hook: [pata]
    -> Running build hook: [scsi]
    -> Running build hook: [sata]
    -> Running build hook: [filesystems]
    -> Running build hook: [usbinput]
    -> Running build hook: [fsck]
    ==> ERROR: file not found: `fsck.btrfs'
    ==> WARNING: No fsck helpers found. fsck will not be run on boot.
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    ==> WARNING: errors were encountered during the build. The image may not be complete.
    ==> Building image from preset: 'fallback'
    -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 3.6.5-1-ARCH
    -> Running build hook: [base]
    -> Running build hook: [udev]
    -> Running build hook: [pata]
    -> Running build hook: [scsi]
    -> Running build hook: [sata]
    -> Running build hook: [filesystems]
    -> Running build hook: [usbinput]
    -> Running build hook: [fsck]
    ==> Generating module dependencies
    ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    ==> Image generation successful
    error: command failed to execute correctly
    I checked the output from lsmod, I dont' see usb-storage, but I do see sd_mod.
    Any thoughts?
    Cheers,
    Victor

    WonderWoofy wrote:At least that is one of the very few times you have to reboot.  MS just never actually ships you a new kernel.  I have never been able to understand why I need to reboot my machine in windows when I install something like a word processor.  What is it actually doing?
    I have no idea, too. I usually don't reboot even after kernel update, because I always think "Oh, what the heck, I'll reboot it eventually anyway". As we can see, it's not always a good idea .
    WonderWoofy wrote:Edit: Don't forget to mark as solved!
    We have to wait for @victorhooi to confirm it .

  • Can't mount 4Tb USB 3.0 drive on a Sparc T5-8 control domain

    Hello,
    I'm trying to mount a 4Tb USB 3.0 disk drive on a Sun Sparc T5-8 running Solaris 11.  It is also the LDOM primary and control domain.
    I've verified that hal, dbus and rmvolmgr are running:
    # svcs hal dbus rmvolmgr
    STATE          STIME    FMRI
    online         Jan_29   svc:/system/dbus:default
    online         16:21:51 svc:/system/hal:default
    online         16:21:51 svc:/system/filesystem/rmvolmgr:default
    but the server can't detect the drive:
    # rmformat -l
    Looking for devices...
    No removables found.
    # echo | format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
           0. c0t5000CCA022659884d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022659884
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD0/disk
           1. c0t5000CCA022666330d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022666330
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD1/disk
           2. c0t5000CCA0166F4D08d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca0166f4d08
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD2/disk
           3. c0t5000CCA022665404d0 <HITACHI-H109090SESUN900G-A600 cyl 38553 alt 2 hd 24 sec 1900>  solaris
              /scsi_vhci/disk@g5000cca022665404
              /dev/chassis/SPARC_T5-8.AK00164945//SYS/SASBP0/HDD3/disk
          4. c1t0d0 <drive not available>
              /pci@300/pci@1/pci@0/pci@4/pci@0/pci@6/usb@0/storage@3/disk@0,0
    Specify disk (enter its number): Specify disk (enter its number): ^C
    I verified the drive is good because I can mount it on a Sun T4 server running Solaris10 and was able to mount and see the data.
    Any ideas why the Sparc T5 can't access the drive?  I've also tried restarting hal and rmvolmgr, but issue still persist.
    Any assistance is appreciated as we need to access customer's data on the drive as soon as possible.
    Thanks,

    Hi,
    since your posting is a couple of weeks old I don't know if you already managed to get the disk working.
    You might want to consider one of the following options to get it working as the problem is seen when the disk drive draws more power as the USB port can deliver.  
    1)  use USB EXTENSION Y CABLE   
    2)  use external USB hub with power supply  
    3)  use USB disk with external power supply
    For more details you might want to review
    (Doc ID 1572327.1)  Solaris might be Unable to Mount certain USB Disks because of Overcurrent on USB Port
    regards
    Walter

  • Udisks2: mount only usb flash

    Hello, Arch users!
    How can I configure udisks2 to permit mounting only usb flash drives and similiar for users in "storage" group, not internal drives?
    Here are the contents of my /etc/polkit-1/localauthority/50-local.d/10-storage-group-mount-override.pkla:
    [storage group mount override]
    Identity=unix-group:storage
    Action=org.freedesktop.udisks2.filesystem-mount-system
    ResultAny=no
    ResultInactive=yes
    ResultActive=yes
    Or I must create another group "storage-flashonly" for this and configure something for it?
    My use-case: I want to protect guest users from mounting my windows partitions, but allow them automounting of their usb flash drives.
    Any thoughts aprreciated.
    Last edited by dontbugme (2012-05-26 02:28:00)

    Change Action line from
    Action=org.freedesktop.udisks2.filesystem-mount-system
    to
    Action=org.freedesktop.udisks2.filesystem-mount
    and it will be mount only removable devices, internal drives won't be mounted

  • Mount a USB flash drive from a shell

    I am about six months new to Linux; I have installed my first arch system but not yet installed a desktop environment.  I am trying to mount a USB flash drive from the shell but I am not having much luck.  I have tried following the instructions in the archwiki, http://wiki.archlinux.org/index.php/USB_Storage_Devices. I am having a problem with the following command:
    mount -t vfat /dev/sda1 /mnt/usbstick
    I get an error message saying that the mount point does not exist.  I have in the /mnt directory the following:
    cd cdrom dvd fd0 f1
    (I am not sure what fd0 and fl are, if somebody could please tell me I would appreciate it.  Also I do not have a DVD-ROM on my computer is the dvd listed by default or do I have a package installed I do not need?)  I did some searching online and came across the following site, http://linuxcommando.blogspot.com/2007/ … -from.html. I followed the instructions to identify the correct partition name corresponding to the USB drive by running the following command:
    grep SCSI /var/log/messages.log
    and I get the following results:
    Dec 30 22:16:17 morgan-desktop scsi2 : SCSI emulation for USB Mass Storage divices
    Dec 30 22:16:22 morgan-desktop sd 2:0:0:0: [sdb] Attached SCSI removable disk
    The next steps in the instructions are to mount the partition to the existing mount point (directory) by using the following command.
    mkdir -p /mnt/myusb
    mount -t vfat -o rw,users /dev/sda1 /mnt/myusb
    This is where I am having a problem, I do not understand the results and how to proceed to the next step, please help me.
    One other small question what is the best command to shut down the computer as a normal user?
    Thank you
    Morgan Smith

    Ok, Lots of different advice here, let's see if I can explain it all together, and clear up a few bits...
    I'll try to explain why I'm saying what I am, it doesn't matter if you don't follow it all, commands are below.
    You are on the right lines here, but a few things missing.  Firstly, to mount the USB stick you are using the correct command, but the locations are a problem.  The command is "mount -t type what/to/mount where/to/mount".   You can find out more about the mount command with "mount --help" or "man mount"
    You have correctly identified type as vfat - this means the pen is formated as FAT.
    To find out what to mount, you can check /var/log/messages.log, the second command you posted searches trough that file and prints out lines including the phrase SCSI, and the result tells you that a usb storage device had been attached as sdb, so the correct device is /dev/sdb1.  Storage devices are named sda sdb sdc etc in the order they are attached, and the numbers refer to the partitions on the disk.
    You can mount it anywhere you want, as any existing directory, but the one you tried to use /mnt/usbstick doesn't exist, so create it, using mkdir.
    The commands you need therefore are:
    mkdir /mnt/usbstick
    mount -t vfat /dev/sdb1 /mnt/usbstick
    This will work as root.  There is also, as byte said, a program called pmount (which you can get with pacman -S pmount) which works the same way for a standard user.
    Finally, there are also a number of tools like HAL which can be used to automate the process.
    As for shutting down, as has been said you must be root or in the power group, then you can use 'halt' 'poweroff' 'reboot' or 'shutdown'. All have slightly different effects, and poweroff is probably the easiest.
    Hope this helps
    Jack

Maybe you are looking for