Announcement

Collapse
No announcement yet.

[SOLVED] USB Drive regonised, but unable to mount (see output)

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    [SOLVED] USB Drive regonised, but unable to mount (see output)

    Sorry to open another topic on this. I've been reading many of the other topics but none could provide me with a solid answer.

    As many, this worked fine yesterday (and worked fine since I installed Kubuntu). Today Kubuntu decided (or I did something wrong) to stop providing me with 1 of my external USB disks.

    I have 2 USB disks, 1 is still working as before, meaning I boot my laptop, power on the USB disk, and the device notifier displays a USB disk. The other USB Disk: power on and many things happen in the backend (see below), but the device notifier doesn't display it. I have tried rebooting, powering on only 1 disk, doing tips provided to my by many other topic, but no luck.

    If I remember correctly I formated this disk in EXT4, and I have several VM files on that drive. (VMWare is not started).

    I have tried mounting it manually, but no luck (see bottom of output).


    Any tips I can try?


    Below is some output of my system:
    # power on USB drive:
    pdaalder@D820:~$ sudo udevadm monitor
    KERNEL[1247999324.103790] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
    UDEV [1247999324.105747] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7 (usb)
    KERNEL[1247999324.106751] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
    UDEV [1247999324.107801] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0 (usb)
    KERNEL[1247999324.108524] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3 (scsi)
    KERNEL[1247999324.108624] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/scsi_host/host3 (scsi_host)
    UDEV [1247999324.110144] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3 (scsi)
    KERNEL[1247999324.110690] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep02 (usb_endpoint)
    KERNEL[1247999324.110806] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep86 (usb_endpoint)
    KERNEL[1247999324.110918] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep81 (usb_endpoint)
    KERNEL[1247999324.111061] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/usb_endpoint/usbdev1.7_ep00 (usb_endpoint)
    UDEV [1247999324.112123] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/scsi_host/host3 (scsi_host)
    UDEV [1247999324.114512] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep02 (usb_endpoint)
    UDEV [1247999324.145039] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep86 (usb_endpoint)
    UDEV [1247999324.147245] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/usb_endpoint/usbdev1.7_ep81 (usb_endpoint)
    UDEV [1247999324.149175] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/usb_endpoint/usbdev1.7_ep00 (usb_endpoint)
    KERNEL[1247999329.116437] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0 (scsi)
    UDEV [1247999329.118652] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0 (scsi)
    KERNEL[1247999329.119622] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0 (scsi)
    KERNEL[1247999329.119740] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_disk/3:0:0:0 (scsi_disk)
    UDEV [1247999329.135800] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0 (scsi)
    KERNEL[1247999329.136388] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/block/sdb (block)
    KERNEL[1247999329.136413] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1 (block)
    KERNEL[1247999329.137086] add /devices/virtual/bdi/8:16 (bdi)
    UDEV [1247999329.138388] add /devices/virtual/bdi/8:16 (bdi)
    KERNEL[1247999329.138852] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_device/3:0:0:0 (scsi_device)
    KERNEL[1247999329.139111] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_generic/sg2 (scsi_generic)
    UDEV [1247999329.140062] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_disk/3:0:0:0 (scsi_disk)
    UDEV [1247999329.143302] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_device/3:0:0:0 (scsi_device)
    UDEV [1247999329.146503] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/scsi_generic/sg2 (scsi_generic)
    UDEV [1247999330.094278] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/block/sdb (block)
    UDEV [1247999330.169125] add /devices/pci0000:00/0000:00:1d.7/usb1/1-7/1-7:1.0/host3/target3:0:0/3:0:0:0/block/sdb/sdb1 (block)

    #dmesg:
    pdaalder@D820:~$ dmesg
    [ 2139.308194] usb 1-7: new high speed USB device using ehci_hcd and address 8
    [ 2139.442986] usb 1-7: configuration #1 chosen from 1 choice
    [ 2139.443820] scsi4 : SCSI emulation for USB Mass Storage devices
    [ 2139.453553] usb-storage: device found at 8
    [ 2139.453558] usb-storage: waiting for device to settle before scanning
    [ 2144.452520] usb-storage: device scan complete
    [ 2144.455199] scsi 4:0:0:0: Direct-Access ST325082 3A 0000 PQ: 0 ANSI: 0
    [ 2144.461376] sd 4:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    [ 2144.462238] sd 4:0:0:0: [sdb] Write Protect is off
    [ 2144.462244] sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00
    [ 2144.462249] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 2144.463768] sd 4:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    [ 2144.464744] sd 4:0:0:0: [sdb] Write Protect is off
    [ 2144.464750] sd 4:0:0:0: [sdb] Mode Sense: 27 00 00 00
    [ 2144.464755] sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 2144.464763] sdb: sdb1
    [ 2144.492844] sd 4:0:0:0: [sdb] Attached SCSI disk
    [ 2144.492982] sd 4:0:0:0: Attached scsi generic sg2 type 0

    # First device is USB drive
    pdaalder@D820:~$ lsusb
    Bus 001 Device 008: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 002: ID 099a:610c Zippy Technology Corp. EL-610 Super Mini Electron luminescent Keyboard
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 003: ID 045e:00f0 Microsoft Corp.
    Bus 003 Device 004: ID 0b97:7762 O2 Micro, Inc. Oz776 SmartCard Reader
    Bus 003 Device 002: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 002 Device 002: ID 413c:a005 Dell Computer Corp. Internal 2.0 Hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    pdaalder@D820:~$ sudo fdisk -l

    Disk /dev/sda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x41ab2316

    Device Boot Start End Blocks Id System
    /dev/sda1 1 12 96358+ de Dell Utility
    /dev/sda2 * 13 1924 15358140 7 HPFS/NTFS
    /dev/sda3 1925 9729 62693662+ f W95 Ext'd (LBA)
    /dev/sda5 3837 5748 15358140 7 HPFS/NTFS
    /dev/sda6 1925 2173 2000029+ 82 Linux swap / Solaris
    /dev/sda7 2174 3836 13358016 83 Linux
    /dev/sda8 5749 9729 31977351 83 Linux

    Partition table entries are not in disk order

    Disk /dev/sdb: 250.0 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xebf7b895

    Device Boot Start End Blocks Id System
    /dev/sdb1 1 30401 244196001 c W95 FAT32 (LBA)

    #mount
    pdaalder@D820:~$ sudo mount -t ext3 /dev/sdb1 /media/tmp/
    mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

    pdaalder@D820:~$ sudo mount -t ext4 /dev/sdb1 /media/tmp/
    mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

    pdaalder@D820:~$ sudo mount -t vfat /dev/sdb1 /media/tmp/
    mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so

    pdaalder@D820:~$ sudo mount -t usbfs /dev/sdb1 /media/tmp/
    pdaalder@D820:~$ ls /media/tmp
    001 002 003 004 005 devices
    Tags: None
    • Top
    • Bottom
    #2
    Re: USB Drive regonised, but unable to mount (see output)

    Hi, are you using both disks on the same USB port? This could be a hardware issue, do you have any other linux computer to try to hook it up?
    • Top
    • Bottom

    Comment

      #3
      Re: USB Drive regonised, but unable to mount (see output)

      Thanks for the prompt reply, but nope, they both have there own USB port. But it doesn't really mater, if I only link (physical by cable) 1 usb at a time then the one giving me this problem will still not be recognised.

      i'm worried that the disk is messed up? No idea how, but the fact that the disk is recognised by the system but not recognised as USB disk worries me a lot.
      • Top
      • Bottom

      Comment

        #4
        Re: USB Drive regonised, but unable to mount (see output)

        Have you tried to fsck it?
        Code:
        sudo fsck.ext4 /dev/sdb1
        • Top
        • Bottom

        Comment

          #5
          Re: USB Drive regonised, but unable to mount (see output)

          Well that command didn't work. I did some more research on why this didn't work, and I came accross the command e2fsck. I have no clue yet what the impact of this command is, and if it will mess up my drive. (See output at bottom).

          I will investigate a bit more

          pdaalder@D820:~$ sudo fsck ext4 /dev/sdb1
          fsck 1.41.4 (27-Jan-2009)
          Usage: fsck.ext2 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
          [-I inode_buffer_blocks] [-P process_inode_size]
          [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
          [-E extended-options] device

          Emergency help:
          -p Automatic repair (no questions)
          -n Make no changes to the filesystem
          -y Assume "yes" to all questions
          -c Check for bad blocks and add them to the badblock list
          -f Force checking even if filesystem is marked clean
          -v Be verbose
          -b superblock Use alternative superblock
          -B blocksize Force blocksize when looking for superblock
          -j external_journal Set location of the external journal
          -l bad_blocks_file Add to badblocks list
          -L bad_blocks_file Set badblocks list
          pdaalder@D820:~$ sudo e2fsck /dev/sdb1
          e2fsck 1.41.4 (27-Jan-2009)
          e2fsck: Superblock invalid, trying backup blocks...
          Superblock needs_recovery flag is clear, but journal has data.
          Recovery flag not set in backup superblock, so running journal anyway.
          vmware-usb-disk: recovering journal
          Group descriptor 0 checksum is invalid. Fix<y>?
          • Top
          • Bottom

          Comment

            #6
            Re: USB Drive regonised, but unable to mount (see output)

            Just open konqueror and type "man:e2fsck", to learn more. Basically, you can pass the "-p" option to autorepair. This is a staple in Unix systems. As far as I know, it is safe. Meaning, if things are damaged (corrupted fs, bad disk blocks, etc), it will most likely repair as long as a repair is possible. I have used it and recovered fs's many times through the years. But hey, it's your data.

            Note that this is also an option if you boot in Rescue Mode.
            • Top
            • Bottom

            Comment

              #7
              Re: USB Drive regonised, but unable to mount (see output)

              YES YES, many many many thanks. It fixed the problem. It e2fsck ended as:
              vmware-usb-disk: Group descriptor 1863 checksum is invalid. FIXED.
              vmware-usb-disk contains a file system with errors, check forced.

              vmware-usb-disk: 6373/15269888 files (0.7% non-contiguous), 27914127/61049000 blocks
              I had to power-off -> power-on and my beautiful Kubuntu recognised my drive again
              So many many thanks.
              • Top
              • Bottom

              Comment

                #8
                Re: USB Drive regonised, but unable to mount (see output)

                My pleasure Please edit the original post and add [SOLVED] to the title.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X