flash drive not recognized after attempted install of a .iso file

remn · 2016-01-31 06:52:20

I installed an .iso file of a linux distro on a usb flash drive that had been working fine. I didn't end up using the drive to run the OS, so now I want to re-format it for use as a regular flash drive. But when I plug it in it's not recognized. I've tried lsblk, fdisk -l, and lsusb. None of these commands recognize this drive. They all work fine with my other flash drives. Anything else I can try to recognize and re-format this drive, or is it a lost cause?

jasonwryan · 2016-01-31 06:59:33

dmesg

remn · 2016-01-31 07:37:43

Wow that produced a lot of info. What am I looking for? Not sure if it's safe to post all of that, but the following output seems to be about the flash drive:

[ 1588.940956] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1589.030678] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1589.030974] scsi host4: usb-storage 2-1:1.0
[ 1589.031271] usbcore: registered new interface driver usb-storage
[ 1589.032531] usbcore: registered new interface driver uas
[ 1590.031438] scsi 4:0:0:0: Direct-Access     SanDisk  SanDisk Ultra    PMAP PQ: 0 ANSI: 6
[ 1590.033729] sd 4:0:0:0: [sdb] 61767680 512-byte logical blocks: (31.6 GB/29.4 GiB)
[ 1590.034607] sd 4:0:0:0: [sdb] Write Protect is off
[ 1590.034617] sd 4:0:0:0: [sdb] Mode Sense: 2b 00 00 08
[ 1590.035482] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1590.158947]  sdb: sdb1
[ 1590.161573] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 1601.347080] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 1935.157800] JFS: nTxBlock = 8192, nTxLock = 65536
[ 1935.221201] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 2013.302698]  sdb: sdb1
[ 2013.659399]  sdb: sdb1
[ 2564.078608]  sdb: sdb1
[ 2564.684424]  sdb: sdb1
[ 2598.056457] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 2598.066902] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 2623.197655] sdb: detected capacity change from 31625052160 to 0
[ 2674.079944] usb 2-1: USB disconnect, device number 2
[ 2678.189038] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 2678.204761] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2678.204889] scsi host5: usb-storage 2-1:1.0
[ 2679.202088] scsi 5:0:0:0: Direct-Access     SanDisk  SanDisk Ultra    PMAP PQ: 0 ANSI: 6
[ 2679.202756] sd 5:0:0:0: [sdb] 61767680 512-byte logical blocks: (31.6 GB/29.4 GiB)
[ 2679.203558] sd 5:0:0:0: [sdb] Write Protect is off
[ 2679.203564] sd 5:0:0:0: [sdb] Mode Sense: 2b 00 00 08
[ 2679.204361] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 2679.427611]  sdb: sdb1
[ 2679.430400] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 2682.955849] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 2682.965996] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 3392.125362] sdb: detected capacity change from 31625052160 to 0
[ 3394.030764] usb 2-1: USB disconnect, device number 4
[ 3397.141513] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
[ 3397.156855] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3397.156967] scsi host6: usb-storage 2-1:1.0
[ 3398.150184] scsi 6:0:0:0: Direct-Access     SanDisk  SanDisk Ultra    PMAP PQ: 0 ANSI: 6
[ 3398.150929] sd 6:0:0:0: [sdb] 61767680 512-byte logical blocks: (31.6 GB/29.4 GiB)
[ 3398.151731] sd 6:0:0:0: [sdb] Write Protect is off
[ 3398.151735] sd 6:0:0:0: [sdb] Mode Sense: 2b 00 00 08
[ 3398.152535] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3398.331573]  sdb: sdb1
[ 3398.334098] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 3405.290351] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 3405.300440] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 3661.286984] usb 2-1: USB disconnect, device number 5
[ 3661.293541] sd 6:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 3661.293551] sd 6:0:0:0: [sdb] CDB: opcode=0x2a 2a 00 00 15 15 a0 00 00 f0 00
[ 3661.293557] blk_update_request: I/O error, dev sdb, sector 1381792
[ 3661.293635] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 173056)
[ 3661.293641] Buffer I/O error on device sdb1, logical block 172544
[ 3661.293648] Buffer I/O error on device sdb1, logical block 172545
[ 3661.293652] Buffer I/O error on device sdb1, logical block 172546
[ 3661.293656] Buffer I/O error on device sdb1, logical block 172547
[ 3661.293659] Buffer I/O error on device sdb1, logical block 172548
[ 3661.293663] Buffer I/O error on device sdb1, logical block 172549
[ 3661.293666] Buffer I/O error on device sdb1, logical block 172550
[ 3661.293670] Buffer I/O error on device sdb1, logical block 172551
[ 3661.293673] Buffer I/O error on device sdb1, logical block 172552
[ 3661.293677] Buffer I/O error on device sdb1, logical block 172553
[ 3661.293895] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 173312)
[ 3661.294111] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 173568)
[ 3661.294332] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 173824)
[ 3661.294549] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 174080)
[ 3661.294763] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 174336)
[ 3661.294975] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 174592)
[ 3661.295188] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 174848)
[ 3661.295401] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 175104)
[ 3661.295612] EXT4-fs warning (device sdb1): ext4_end_bio:329: I/O error -5 writing to inode 13 (offset 0 size 0 starting block 175360)
[ 3661.296658] sd 6:0:0:0: [sdb] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 3661.296663] sd 6:0:0:0: [sdb] CDB: opcode=0x2a 2a 00 00 15 16 90 00 00 f0 00
[ 3661.296667] blk_update_request: I/O error, dev sdb, sector 1382032
[ 3661.399997] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 3661.400094] Aborting journal on device sdb1-8.
[ 3661.400101] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 3661.530153] EXT4-fs error (device sdb1): ext4_put_super:808: Couldn't clean up the journal
[ 3661.530158] EXT4-fs (sdb1): Remounting filesystem read-only
[ 3661.530160] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 3916.926702] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[ 3916.992312] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3916.992424] scsi host7: usb-storage 2-1:1.0
[ 3917.073743] usb 2-1: USB disconnect, device number 6
[ 3917.433495] usb 2-1: new SuperSpeed USB device number 7 using xhci_hcd
[ 3917.499576] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3917.499683] scsi host8: usb-storage 2-1:1.0
[ 3917.572757] usb 2-1: USB disconnect, device number 7
[ 3925.418372] usb 2-1: new SuperSpeed USB device number 8 using xhci_hcd
[ 3925.484956] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3925.485435] scsi host9: usb-storage 2-1:1.0
[ 3925.555741] usb 2-1: USB disconnect, device number 8
[ 3927.215236] usb 2-1: new SuperSpeed USB device number 9 using xhci_hcd
[ 3927.281711] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 3927.282206] scsi host10: usb-storage 2-1:1.0
[ 3927.551550] usb 2-1: USB disconnect, device number 9
[ 5369.193444] wlp3s0: deauthenticating from e8:50:8b:b9:61:d7 by local choice (Reason: 3=DEAUTH_LEAVING)

Last edited by remn (2016-02-02 04:33:10)

jasonwryan · 2016-01-31 07:43:45

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_code

Those I/O errors on sdb1 (which I presume is the USB drive) look bad...

paulkerry · 2016-01-31 15:07:47

Your dmesg output shows it is recognised as sdb with a ext3 filesystem which has problems. If you plug it in again and dmesg assigns sdb again, have you tried using...

gparted /dev/sdb

to create a new partition table and then format it as a fat filesystem which is the most regular type for usb sticks?

Last edited by paulkerry (2016-01-31 15:09:58)

mich41 · 2016-01-31 15:44:53

It looks like it disconnected from USB after few seconds for some reason. Did you unplug it?

If not then the $1M question is - does it work on any other machine or with any other OS?

remn · 2016-01-31 16:54:35

Thanks for the replies. Sorry, I'll be sure to use code tags in the future.

I tried running

gparted /dev/sdb

but got the following error message:

Error opening /dev/sdb: No medium found

Which is strange since sdb shows when I run dmesg.

I'll try plugging the drive into another computer later and see if it shows up.

mich41 · 2016-01-31 19:26:30

remn wrote:

Which is strange since sdb shows when I run dmesg.

There's nothing strange here, because the device disconnects after few seconds. Read your dmesg. And please edit your previous post and add code tags, it really looks messy.

R00KIE · 2016-01-31 21:47:40

This [1] comes to mind. I know it's a different model of flash drive but I would try it on a USB2 port to see if it works properly before declaring that flash drive broken.

[1] https://bbs.archlinux.org/viewtopic.php?id=206875

remn · 2016-02-02 04:37:46

mich41 wrote:

remn wrote:
Which is strange since sdb shows when I run dmesg.
There's nothing strange here, because the device disconnects after few seconds. Read your dmesg. And please edit your previous post and add code tags, it really looks messy.

I added code tags to the post. Sorry for the sloppy formatting. Luckily this is just a cheap 8GB flash drive so it's not a big loss. I was just curious to understand what had gone wrong, but this looks like a real mess so I'll just move on. Thanks for the replies!

Arch Linux

#1 2016-01-31 06:52:20

flash drive not recognized after attempted install of a .iso file

#2 2016-01-31 06:59:33

Re: flash drive not recognized after attempted install of a .iso file

#3 2016-01-31 07:37:43

Re: flash drive not recognized after attempted install of a .iso file

#4 2016-01-31 07:43:45

Re: flash drive not recognized after attempted install of a .iso file

#5 2016-01-31 15:07:47

Re: flash drive not recognized after attempted install of a .iso file

#6 2016-01-31 15:44:53

Re: flash drive not recognized after attempted install of a .iso file

#7 2016-01-31 16:54:35

Re: flash drive not recognized after attempted install of a .iso file

#8 2016-01-31 19:26:30

Re: flash drive not recognized after attempted install of a .iso file

#9 2016-01-31 21:47:40

Re: flash drive not recognized after attempted install of a .iso file

#10 2016-02-02 04:37:46

Re: flash drive not recognized after attempted install of a .iso file

Board footer