SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2015-08-26 18:45:34

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

[Solved] Weird happenings with USB sticks - HELP!

Used this from the old #! Wiki:

HOWTO copy a CrunchBang 10 Statler ISO image to USB in Linux

:!: WARNING, the following instructions will destroy any existing data on your USB stick.

1. Insert your USB stick and learn how your USB stick is recognized by the system, enter the command:

sudo ls -l /dev/disk/by-id/*usb*

This should produce output along the lines of:

lrwxrwxrwx 1 root root  9 2010-03-15 22:54 /dev/disk/by-id/usb-_USB_DISK_2.0_077508380189-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 2010-03-15 22:54 /dev/disk/by-id/usb-_USB_DISK_2.0_077508380189-0:0-part1 -> ../../sdb1

2. Unmount the usb stick, then use this command to write (as root) the image iso to your USB stick.
:!: Replace /dev/sdX with the actual hard disk device learned from the command above. In this example /dev/sdb NOT /dev/sdb1
:!: Replace the name of the iso image below by the actual name of the iso image you downloaded.

sudo dd if=/path/to/iso/crunchbang-10-20101205-openbox-i686.iso of=/dev/sdX bs=4M;sync

All being well, you should now have a bootable CrunchBang Statler USB stick.

and as seen below:

sudo ls -l /dev/disk/by-id/*usb*

shows some really weird and different outputs.

Here's my 5 USB Sticks done one at a time.
====================

1.  2GB DataTraveler

- thunar simply does not mount it - it has #! Waldorf on it.
Boots to:  #! Live Session / Install / Memory Test
Image Link: http://postimg.org/image/al26swrih/

gparted reports: Invalid partition table - recursive partition on /dev/sdb.

 26 Aug 15 | 13:45:00 ~
    $ usb1
alias usb1 = ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
sdb
sdb1
sdb

 26 Aug 15 | 13:45:40 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
lrwxrwxrwx 1 root root  9 Aug 26 13:40 /dev/disk/by-id/usb-Kingston_DataTraveler_2.0_001CC07CE9A2F96021550244-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 13:40 /dev/disk/by-id/usb-Kingston_DataTraveler_2.0_001CC07CE9A2F96021550244-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Aug 26 12:37 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb

 26 Aug 15 | 13:45:42 ~
    $ 

====================

2.  4GB ScanDisk Cruzer Edge

- thunar automounts at: /media/sector11/Debian 8.0.0 amd64 1/
Boots to: Debian GNU/Linux - Install - no Live
Image Link: http://postimg.org/image/9ciwl0oy1/

gparted reports: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. (Ignore)
gparted continues: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.

 26 Aug 15 | 13:51:46 ~
    $ usb1
alias usb1 = ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
sdb
sdb
sdb1
sdb2

 26 Aug 15 | 13:52:37 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11:
lrwxrwxrwx 1 root root  9 Aug 26 12:37 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 13:51 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 13:51 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 26 13:51 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0-part2 -> ../../sdb2

 26 Aug 15 | 13:52:43 ~
    $

====================

3.  4GB Cruser Blade

- thunar automounts at: /media/sector11/Debian 8.1.0 amd64 1/ - shows empty
Boots to: flashing cursor
Image link: http://postimg.org/image/6pysqc8cp/

 26 Aug 15 | 14:05:10 ~
    $ usb1
alias usb1 = ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
sdb
sdb
sdb1

 26 Aug 15 | 14:05:15 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11:
lrwxrwxrwx 1 root root  9 Aug 26 12:37 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 14:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_4C532000030822116285-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 14:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_4C532000030822116285-0:0-part1 -> ../../sdb1

 26 Aug 15 | 14:05:23 ~
    $ 

====================

4.  8GB Cruser Blade

- thunar automounts at: /media/sector11/Debian testing amd64 1/ - populated
Boots to: Debian GNU/Linux - Install - no Live
Image link: http://postimg.org/image/kmbmfytzd/

gparted reports: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.

gparted continuses: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.

 26 Aug 15 | 15:03:15 ~
    $ usb1
alias usb1 = ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
sdb
sdb1
sdb2

 26 Aug 15 | 15:03:22 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11:
lrwxrwxrwx 1 root root  9 Aug 26 15:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 15:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 26 15:03 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0-part2 -> ../../sdb2

 26 Aug 15 | 15:03:29 ~
    $ 

====================

5.  8gb Sony

- thunar automounts at: /media/sector11/Sony_8GM/ - shows empty
Boots to: GRUB
Image link: http://postimg.org/image/5cbr8ryh5/

 26 Aug 15 | 14:45:45 ~
    $ usb1
alias usb1 = ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
sdb
sdb1

 26 Aug 15 | 14:45:50 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11:
lrwxrwxrwx 1 root root  9 Aug 26 14:44 /dev/disk/by-id/usb-Sony_Storage_Media_9B3001308300077634-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 14:44 /dev/disk/by-id/usb-Sony_Storage_Media_9B3001308300077634-0:0-part1 -> ../../sdb1

 26 Aug 15 | 14:45:57 ~
    $ 

====================
This is STRANGE! So I thought add an ISO yo the sony stick

8gb Sony is the ONLY usb stick plugged in:

 26 Aug 15 | 15:15:54 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11:
lrwxrwxrwx 1 root root  9 Aug 26 15:09 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 15:15 /dev/disk/by-id/usb-Sony_Storage_Media_9B3001308300077634-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 26 15:15 /dev/disk/by-id/usb-Sony_Storage_Media_9B3001308300077634-0:0-part1 -> ../../sdb1

Where is that "SanDisk_Cruzer_Blade" coming from?  It is EVERYWHERE!!!!
Image link: http://postimg.org/image/6h5te5ky1/

And I can't use the dd command to put an ISO on anything.  sad

HELP Please


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

Help fund CrunchBang, donate to the project!

#2 2015-08-26 19:35:33

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Well, been searching the net ... want to "reformat" a stick ... nothing plugged in and I get:

 26 Aug 15 | 16:31:43 ~
    $ usb
alias usb = sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
lrwxrwxrwx 1 root root 9 Aug 26 15:09 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 Aug 26 16:04 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
 
 26 Aug 15 | 16:31:54 ~
    $ 

GREAT ... Just ... great!

Any idea where they are hiding in my system?

OK so I found them ... how the heck do I kill/delete/blow-it-up/nuke_it/deep_six it?

 26 Aug 15 | 16:51:43 ~
    $ ls -l /dev/disk/by-id/*
lrwxrwxrwx 1 root root  9 Aug 26 14:58 /dev/disk/by-id/ata-HL-DT-ST_DVDRAM_GSA-H10L_K13E7OM1751 -> ../../sr0
lrwxrwxrwx 1 root root  9 Aug 26 14:58 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part10 -> ../../sda10
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part11 -> ../../sda11
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part12 -> ../../sda12
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 26 15:09 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part9 -> ../../sda9
lrwxrwxrwx 1 root root  9 Aug 26 15:09 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 16:04 /dev/disk/by-id/usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 14:58 /dev/disk/by-id/wwn-0x50014ee2b39c6bec -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part10 -> ../../sda10
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part11 -> ../../sda11
lrwxrwxrwx 1 root root 11 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part12 -> ../../sda12
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 26 15:09 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 26 16:03 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 Aug 26 14:58 /dev/disk/by-id/wwn-0x50014ee2b39c6bec-part9 -> ../../sda9
 
 26 Aug 15 | 16:51:50 ~
    $ 

What the heck is

wwn-0x50014ee2b39c6bec

looks like it matches

ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817

·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#3 2015-08-26 19:49:08

ohnonot
...again
Registered: 2012-05-22
Posts: 2,205

Re: [Solved] Weird happenings with USB sticks - HELP!

have you tried rebooting?

Offline

#4 2015-08-26 19:52:43

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Every morning!

And I rebooted 5 times testing the USP sticks to see if they would boot ... the last I tried was the 8GB Sony


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#5 2015-08-26 20:03:24

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

Can we see the output of:

grep -ri '/dev/disk' /usr/lib/udev/rules.d/

Offline

#6 2015-08-26 20:25:02

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

@ Head_on_a_Stick - Not here - doesn't exist:

 26 Aug 15 | 17:07:35 ~
    $ grep -ri '/dev/disk' /usr/lib/udev/rules.d/
grep: /usr/lib/udev/rules.d/: No such file or directory
 
 26 Aug 15 | 17:07:36 ~
    $ sudo grep -ri '/dev/disk' /usr/lib/udev/rules.d/
[sudo] password for sector11: 
grep: /usr/lib/udev/rules.d/: No such file or directory
 
 26 Aug 15 | 17:07:55 ~
    $ 

This is interesting ...

 26 Aug 15 | 17:12:20 ~
    $ ls -l /dev/disk/
total 0
drwxr-xr-x 2 root root 620 Aug 26 16:15 by-id
drwxr-xr-x 2 root root  60 Aug 26 16:15 by-path
drwxr-xr-x 2 root root 260 Aug 26 16:15 by-uuid
 
 26 Aug 15 | 17:12:24 ~
    $ ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 Aug 26 14:58 ata-HL-DT-ST_DVDRAM_GSA-H10L_K13E7OM1751 -> ../../sr0
lrwxrwxrwx 1 root root  9 Aug 26 14:58 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part10 -> ../../sda10
lrwxrwxrwx 1 root root 11 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part11 -> ../../sda11
lrwxrwxrwx 1 root root 11 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part12 -> ../../sda12
lrwxrwxrwx 1 root root 10 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 26 15:09 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 26 14:58 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 26 16:03 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Aug 26 14:58 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 Aug 26 14:58 ata-WDC_WD5000AAKX-22ERMA0_WD-WCC2EMF62817-part9 -> ../../sda9
lrwxrwxrwx 1 root root  9 Aug 26 15:09 usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 16:04 usb-SanDisk_Cruzer_Edge_200608761118FA825D92-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 26 14:58 wwn-0x50014ee2b39c6bec -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part1 -> ../../sda1
lrwxrwxrwx 1 root root 11 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part10 -> ../../sda10
lrwxrwxrwx 1 root root 11 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part11 -> ../../sda11
lrwxrwxrwx 1 root root 11 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part12 -> ../../sda12
lrwxrwxrwx 1 root root 10 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 26 15:09 wwn-0x50014ee2b39c6bec-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug 26 14:58 wwn-0x50014ee2b39c6bec-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part6 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 26 16:03 wwn-0x50014ee2b39c6bec-part7 -> ../../sda7
lrwxrwxrwx 1 root root 10 Aug 26 14:58 wwn-0x50014ee2b39c6bec-part8 -> ../../sda8
lrwxrwxrwx 1 root root 10 Aug 26 14:58 wwn-0x50014ee2b39c6bec-part9 -> ../../sda9
 
 26 Aug 15 | 17:12:43 ~
    $ ls -l /dev/disk/by-path
total 0
lrwxrwxrwx 1 root root 9 Aug 26 16:04 pci-0000:00:02.1-usb-0:10:1.0-scsi-0:0:0:0 -> ../../sdb
 
 26 Aug 15 | 17:12:54 ~
    $ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 11 Aug 26 16:03 25564c1c-325d-4331-b354-47a5a344e667 -> ../../sda11
lrwxrwxrwx 1 root root 10 Aug 26 14:58 3139da3e-24b0-4b50-ae55-59a9cf65635e -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug 26 16:03 51766402-83a0-4d92-936f-99f5e0d3a664 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 26 16:03 83133c48-526a-42a2-915e-94297bf62f5e -> ../../sda7
lrwxrwxrwx 1 root root 10 Aug 26 14:58 9c8f5b02-2631-4eee-afec-71c40f5ba863 -> ../../sda8
lrwxrwxrwx 1 root root 10 Aug 26 16:03 9d5d27f0-99f5-4683-bd3b-512d2edea365 -> ../../sda6
lrwxrwxrwx 1 root root 10 Aug 26 14:58 9f6ebf48-e240-4424-8224-604039145621 -> ../../sda9
lrwxrwxrwx 1 root root 11 Aug 26 16:03 b40e4226-13a7-41bb-814e-3736e138e418 -> ../../sda12
lrwxrwxrwx 1 root root 11 Aug 26 16:03 d1597bcd-7863-4433-a910-ce2d4e93ca00 -> ../../sda10
lrwxrwxrwx 1 root root 10 Aug 26 16:03 f0a43c79-a1da-411d-8579-74192abcfe1d -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 26 16:03 f1956805-a50e-4c94-b687-81ebd1c165f8 -> ../../sda1
 
 26 Aug 15 | 17:13:03 ~
    $ 

Hmmmmmmmmm:   10 Aug 26 16:03

10 August 1826
10 August 1926
10 August 2026
10 August 2126
...
10 August 2626

In the year 2626 if S11 is still sane ....
Don't mind me I'm going crazy tith this and have been for a while ... but after a month or so of searching I give up and came asking for help.

{ still lol lol lol lol lol  }


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#7 2015-08-26 20:39:48

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

Sorry I'm in FreeBSD at the moment...

grep -ri '/dev/disk' /lib/udev/rules.d/

Offline

#8 2015-08-26 21:15:26

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

 26 Aug 15 | 18:06:08 ~
    $ grep -ri '/dev/disk' /lib/udev/rules.d/
/lib/udev/rules.d/60-persistent-storage.rules:# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
/lib/udev/rules.d/60-persistent-storage-dm.rules:# These rules create symlinks in /dev/disk directory.
 
 26 Aug 15 | 18:06:12 ~
    $ 

I HATE symlinks and I'd get rid of UUID's entirely if I could ... but that just me remembering the days before UUID's when:

/dev/sda1, /dev/sda2, /dev/sdb1,  etc was good enough and I had 4 HDD's with multiple partitions on each. {sigh}


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#9 2015-08-26 21:25:51

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

What is the content of /lib/udev/rules.d/60-persistent-storage.rules?

Offline

#10 2015-08-26 21:36:40

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Contents: cat /lib/udev/rules.d/60-persistent-storage.rules

 26 Aug 15 | 18:35:39 ~
    $ cat /lib/udev/rules.d/60-persistent-storage.rules
# do not edit this file, it will be overwritten on update

# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
# scheme based on "Linux persistent device names", 2004, Hannes Reinecke <hare@suse.de>

# forward scsi device event to corresponding block device
ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST=="block", ATTR{block/*/uevent}="change"

ACTION=="remove", GOTO="persistent_storage_end"

# enable in-kernel media-presence polling
ACTION=="add", SUBSYSTEM=="module", KERNEL=="block", ATTR{parameters/events_dfl_poll_msecs}=="0", ATTR{parameters/events_dfl_poll_msecs}="2000"
ACTION=="add", ATTR{removable}=="1", ATTR{events_poll_msecs}=="-1", ATTR{events_poll_msecs}="2000"

SUBSYSTEM!="block", GOTO="persistent_storage_end"

# skip rules for inappropriate block devices
KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*|zram*|mmcblk[0-9]*rpmb", GOTO="persistent_storage_end"

# ignore partitions that span the entire disk
TEST=="whole_disk", GOTO="persistent_storage_end"

# for partitions import parent information
ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"

# virtio-blk
KERNEL=="vd*[!0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}"
KERNEL=="vd*[0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}-part%n"

# ATA devices using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="ATA", IMPORT{program}="ata_id --export $devnode"
# ATA/ATAPI devices (SPC-3 or later) using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", ATTRS{scsi_level}=="[6-9]*", IMPORT{program}="ata_id --export $devnode"

# Run ata_id on non-removable USB Mass Storage (SATA/PATA disks in enclosures)
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", ATTR{removable}=="0", SUBSYSTEMS=="usb", IMPORT{program}="ata_id --export $devnode"
# Otherwise, fall back to using usb_id for USB devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"

# scsi devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="scsi"
KERNEL=="cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="cciss"
KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n"

# firewire
KERNEL=="sd*[!0-9]|sr*", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}"
KERNEL=="sd*[0-9]", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}-part%n"

KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mmcblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}-part%n"
KERNEL=="mspblk[0-9]", SUBSYSTEMS=="memstick", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mspblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}-part%n"

# by-path (parent device path)
ENV{DEVTYPE}=="disk", DEVPATH!="*/virtual/*", IMPORT{builtin}="path_id"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"

# skip unpartitioned removable media devices from drivers which do not send "change" events
ENV{DEVTYPE}=="disk", KERNEL!="sd*|sr*", ATTR{removable}=="1", GOTO="persistent_storage_end"

# probe filesystem metadata of optical drives which have a media inserted
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
  IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
# single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
  IMPORT{builtin}="blkid --noraid"

# probe filesystem metadata of disks
KERNEL!="sr*", IMPORT{builtin}="blkid"

# watch metadata changes by tools closing the device after writing
KERNEL!="sr*", OPTIONS+="watch"

# by-label/by-uuid links (filesystem metadata)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"

# by-id (World Wide Name)
ENV{DEVTYPE}=="disk", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}"
ENV{DEVTYPE}=="partition", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}-part%n"

# by-partlabel/by-partuuid links (partition metadata)
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_UUID}=="?*", SYMLINK+="disk/by-partuuid/$env{ID_PART_ENTRY_UUID}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="disk/by-partlabel/$env{ID_PART_ENTRY_NAME}"

# add symlink to GPT root disk
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_GPT_AUTO_ROOT}=="1", SYMLINK+="gpt-auto-root"

LABEL="persistent_storage_end"
 
 26 Aug 15 | 18:35:44 ~
    $ 

·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#11 2015-08-26 21:50:43

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

Anything in dmesg?

dmesg|grep -i 'by-id\|blade'

Offline

#12 2015-08-26 22:27:23

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Yup, same {heavily censored}

 26 Aug 15 | 19:16:57 ~
    $ dmesg|grep -i 'by-id\|blade'
[  261.595866] usb 1-10: Product: Cruzer Blade
[  262.717742] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
[  595.881133] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
[  625.390555] usb 1-10: Product: Cruzer Blade
[  626.392271] scsi 8:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
 
 26 Aug 15 | 19:17:01 ~
    $ 

I'm glad your finding all this {heavily censored} stuff 'cuz I haven't a clue.  There is NOTHING plugged in except the Brother printer.

usb://Brother/HL-1110%20series?serial=F4N936063

Even my keyboard and mouse are the old PS/2 connectors so no USB there.

Colour me puzzled!

But no SanDisk Cruzer Edge there at least.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#13 2015-08-26 22:35:06

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

Sector11 wrote:

Colour me puzzled!

+1

I have no idea what's going on here hmm

Let me think about this for a bit.

Offline

#14 2015-08-26 23:24:50

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

This is my BunsenLabs OOTB - not even my NVIDIA drivers:

No SanDisk present:

sector11@bunsenlabs:~$ ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-ls: cannot access /dev/disk/by-id/*usb*: No such file or directory
sector11@bunsenlabs:~$ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
ls: cannot access /dev/disk/by-id/*usb*: No such file or directory
sector11@bunsenlabs:~$ grep -ri '/dev/disk' /lib/udev/rules.d/
/lib/udev/rules.d/60-persistent-storage.rules:# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
/lib/udev/rules.d/60-persistent-storage-dm.rules:# These rules create symlinks in /dev/disk directory.
sector11@bunsenlabs:~$ cat /lib/udev/rules.d/60-persistent-storage.rules
# do not edit this file, it will be overwritten on update

# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
# scheme based on "Linux persistent device names", 2004, Hannes Reinecke <hare@suse.de>

# forward scsi device event to corresponding block device
ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST=="block", ATTR{block/*/uevent}="change"

ACTION=="remove", GOTO="persistent_storage_end"

# enable in-kernel media-presence polling
ACTION=="add", SUBSYSTEM=="module", KERNEL=="block", ATTR{parameters/events_dfl_poll_msecs}=="0", ATTR{parameters/events_dfl_poll_msecs}="2000"
ACTION=="add", ATTR{removable}=="1", ATTR{events_poll_msecs}=="-1", ATTR{events_poll_msecs}="2000"

SUBSYSTEM!="block", GOTO="persistent_storage_end"

# skip rules for inappropriate block devices
KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*|zram*|mmcblk[0-9]*rpmb", GOTO="persistent_storage_end"

# ignore partitions that span the entire disk
TEST=="whole_disk", GOTO="persistent_storage_end"

# for partitions import parent information
ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"

# virtio-blk
KERNEL=="vd*[!0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}"
KERNEL=="vd*[0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}-part%n"

# ATA devices using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="ATA", IMPORT{program}="ata_id --export $devnode"
# ATA/ATAPI devices (SPC-3 or later) using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", ATTRS{scsi_level}=="[6-9]*", IMPORT{program}="ata_id --export $devnode"

# Run ata_id on non-removable USB Mass Storage (SATA/PATA disks in enclosures)
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", ATTR{removable}=="0", SUBSYSTEMS=="usb", IMPORT{program}="ata_id --export $devnode"
# Otherwise, fall back to using usb_id for USB devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"

# scsi devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="scsi"
KERNEL=="cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="cciss"
KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n"

# firewire
KERNEL=="sd*[!0-9]|sr*", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}"
KERNEL=="sd*[0-9]", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}-part%n"

KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mmcblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}-part%n"
KERNEL=="mspblk[0-9]", SUBSYSTEMS=="memstick", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mspblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}-part%n"

# by-path (parent device path)
ENV{DEVTYPE}=="disk", DEVPATH!="*/virtual/*", IMPORT{builtin}="path_id"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"

# skip unpartitioned removable media devices from drivers which do not send "change" events
ENV{DEVTYPE}=="disk", KERNEL!="sd*|sr*", ATTR{removable}=="1", GOTO="persistent_storage_end"

# probe filesystem metadata of optical drives which have a media inserted
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
  IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
# single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
  IMPORT{builtin}="blkid --noraid"

# probe filesystem metadata of disks
KERNEL!="sr*", IMPORT{builtin}="blkid"

# watch metadata changes by tools closing the device after writing
KERNEL!="sr*", OPTIONS+="watch"

# by-label/by-uuid links (filesystem metadata)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"

# by-id (World Wide Name)
ENV{DEVTYPE}=="disk", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}"
ENV{DEVTYPE}=="partition", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}-part%n"

# by-partlabel/by-partuuid links (partition metadata)
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_UUID}=="?*", SYMLINK+="disk/by-partuuid/$env{ID_PART_ENTRY_UUID}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="disk/by-partlabel/$env{ID_PART_ENTRY_NAME}"

# add symlink to GPT root disk
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_GPT_AUTO_ROOT}=="1", SYMLINK+="gpt-auto-root"

LABEL="persistent_storage_end"
sector11@bunsenlabs:~$ dmesg|grep -i 'by-id\|blade'
sector11@bunsenlabs:~$ 

·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#15 2015-08-26 23:32:35

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Debian 8 - #! look alike with some Bunsen added

 26 Aug 15 | 20:29:13 ~
    $ ls -l /dev/disk/by-id/*usb* | awk {'print (1)'} | cut -c 7-
ls: cannot access /dev/disk/by-id/*usb*: No such file or directory
 
 26 Aug 15 | 20:29:17 ~
    $ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
ls: cannot access /dev/disk/by-id/*usb*: No such file or directory
 
 26 Aug 15 | 20:29:34 ~
    $ dmesg|grep -i 'by-id\|blade'
 
 26 Aug 15 | 20:30:09 ~
    $ grep -ri '/dev/disk' /lib/udev/rules.d/
/lib/udev/rules.d/60-persistent-storage-dm.rules:# These rules create symlinks in /dev/disk directory.
/lib/udev/rules.d/60-persistent-storage.rules:# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
 
 26 Aug 15 | 20:30:43 ~
    $ cat /lib/udev/rules.d/60-persistent-storage.rules
# do not edit this file, it will be overwritten on update

# persistent storage links: /dev/disk/{by-id,by-uuid,by-label,by-path}
# scheme based on "Linux persistent device names", 2004, Hannes Reinecke <hare@suse.de>

# forward scsi device event to corresponding block device
ACTION=="change", SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST=="block", ATTR{block/*/uevent}="change"

ACTION=="remove", GOTO="persistent_storage_end"

# enable in-kernel media-presence polling
ACTION=="add", SUBSYSTEM=="module", KERNEL=="block", ATTR{parameters/events_dfl_poll_msecs}=="0", ATTR{parameters/events_dfl_poll_msecs}="2000"
ACTION=="add", ATTR{removable}=="1", ATTR{events_poll_msecs}=="-1", ATTR{events_poll_msecs}="2000"

SUBSYSTEM!="block", GOTO="persistent_storage_end"

# skip rules for inappropriate block devices
KERNEL=="fd*|mtd*|nbd*|gnbd*|btibm*|dm-*|md*|zram*|mmcblk[0-9]*rpmb", GOTO="persistent_storage_end"

# ignore partitions that span the entire disk
TEST=="whole_disk", GOTO="persistent_storage_end"

# for partitions import parent information
ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*"

# virtio-blk
KERNEL=="vd*[!0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}"
KERNEL=="vd*[0-9]", ATTRS{serial}=="?*", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/virtio-$env{ID_SERIAL}-part%n"

# ATA devices using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{vendor}=="ATA", IMPORT{program}="ata_id --export $devnode"
# ATA/ATAPI devices (SPC-3 or later) using the "scsi" subsystem
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="scsi", ATTRS{type}=="5", ATTRS{scsi_level}=="[6-9]*", IMPORT{program}="ata_id --export $devnode"

# Run ata_id on non-removable USB Mass Storage (SATA/PATA disks in enclosures)
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", ATTR{removable}=="0", SUBSYSTEMS=="usb", IMPORT{program}="ata_id --export $devnode"
# Otherwise, fall back to using usb_id for USB devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"

# scsi devices
KERNEL=="sd*[!0-9]|sr*", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="scsi"
KERNEL=="cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}!="?*", IMPORT{program}="scsi_id --export --whitelisted -d $devnode", ENV{ID_BUS}="cciss"
KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"
KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}-part%n"

# firewire
KERNEL=="sd*[!0-9]|sr*", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}"
KERNEL=="sd*[0-9]", ATTRS{ieee1394_id}=="?*", SYMLINK+="disk/by-id/ieee1394-$attr{ieee1394_id}-part%n"

KERNEL=="mmcblk[0-9]", SUBSYSTEMS=="mmc", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mmcblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/mmc-$env{ID_NAME}_$env{ID_SERIAL}-part%n"
KERNEL=="mspblk[0-9]", SUBSYSTEMS=="memstick", ATTRS{name}=="?*", ATTRS{serial}=="?*", ENV{ID_NAME}="$attr{name}", ENV{ID_SERIAL}="$attr{serial}", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}"
KERNEL=="mspblk[0-9]p[0-9]", ENV{ID_NAME}=="?*", ENV{ID_SERIAL}=="?*", SYMLINK+="disk/by-id/memstick-$env{ID_NAME}_$env{ID_SERIAL}-part%n"

# by-path (parent device path)
ENV{DEVTYPE}=="disk", DEVPATH!="*/virtual/*", IMPORT{builtin}="path_id"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="?*", SYMLINK+="disk/by-path/$env{ID_PATH}-part%n"

# skip unpartitioned removable media devices from drivers which do not send "change" events
ENV{DEVTYPE}=="disk", KERNEL!="sd*|sr*", ATTR{removable}=="1", GOTO="persistent_storage_end"

# probe filesystem metadata of optical drives which have a media inserted
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
  IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
# single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
  IMPORT{builtin}="blkid --noraid"

# probe filesystem metadata of disks
KERNEL!="sr*", IMPORT{builtin}="blkid"

# watch metadata changes by tools closing the device after writing
KERNEL!="sr*", OPTIONS+="watch"

# by-label/by-uuid links (filesystem metadata)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*", SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
ENV{ID_FS_USAGE}=="filesystem|other", ENV{ID_FS_LABEL_ENC}=="?*", SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"

# by-id (World Wide Name)
ENV{DEVTYPE}=="disk", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}"
ENV{DEVTYPE}=="partition", ENV{ID_WWN_WITH_EXTENSION}=="?*", SYMLINK+="disk/by-id/wwn-$env{ID_WWN_WITH_EXTENSION}-part%n"

# by-partlabel/by-partuuid links (partition metadata)
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_UUID}=="?*", SYMLINK+="disk/by-partuuid/$env{ID_PART_ENTRY_UUID}"
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="disk/by-partlabel/$env{ID_PART_ENTRY_NAME}"

# add symlink to GPT root disk
ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_GPT_AUTO_ROOT}=="1", SYMLINK+="gpt-auto-root"

LABEL="persistent_storage_end"
 
 26 Aug 15 | 20:30:57 ~
    $ 

·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#16 2015-08-27 06:17:54

ohnonot
...again
Registered: 2012-05-22
Posts: 2,205

Re: [Solved] Weird happenings with USB sticks - HELP!

i didn't really follow your dialog with HoaS, but...

the contents of my /dev/disk are quite similar (in that the subfolders contents don't match 100%, at least at first glance, and there seems to be more entries than actual partitions present on my machine).
but none of the symlinks are broken.
btw, you can also look at the directories with your file manager. sometimes helps to restore sanity.

whilst creating bootable usb, i sometimes experienced similar weirdness, "ghost" partitions.
usually gparted (a heavy gui blob, but most convenient to see what is happening) would throw a warning, sth about "partition tables... old ones being used instead".
but a reboot always fixed it.

btw, you got that one wrong:

Sector11 wrote:

Hmmmmmmmmm:   10 Aug 26 16:03

10 August 1826
10 August 1926
10 August 2026
10 August 2126
...
10 August 2626

10 is the size of the file, 26 is the day of the month.
the time (HH:MM) gets replaced by the year (YYYY) when the file is older than this year some months.

Offline

#17 2015-08-27 08:07:04

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: [Solved] Weird happenings with USB sticks - HELP!

Does this clear the entries:

sudo partprobe /dev/sdb

At any rate, I always just plug the USB stick in and use `dmesg|tail` to determine the block device.

Offline

#18 2015-08-28 01:55:37

johnraff
nullglob
From: Nagoya, Japan
Registered: 2009-01-07
Posts: 4,148
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Head_on_a_Stick wrote:

At any rate, I always just plug the USB stick in and use `dmesg|tail` to determine the block device.

Me too.

sudo tail -f /var/log/messages

in a terminal can be handy for a running commentary at times like this.


John
--------------------
( a boring Japan blog , Japan Links, idle twitterings  and GitStuff )
#! forum moderator    BunsenLabs

Offline

#19 2015-08-28 16:43:30

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Plugged in 8GB SanDisk Cruzer Blade:

 28 Aug 15 | 13:32:37 ~
    $ dmesg|tail
[17416.014675] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
[17416.014996] sd 6:0:0:0: Attached scsi generic sg2 type 0
[17416.017158] sd 6:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[17416.018547] sd 6:0:0:0: [sdb] Write Protect is off
[17416.018552] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[17416.019543] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[17416.031073]  sdb: sdb1 sdb2
[17416.034934] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[17416.461423] ISO 9660 Extensions: Microsoft Joliet Level 3
[17416.479819] ISO 9660 Extensions: RRIP_1991A
 
 28 Aug 15 | 13:32:39 ~
    $ sudo tail -f /var/log/messages
[sudo] password for sector11: 
Aug 28 13:32:23 bunsen kernel: [17416.014675] scsi 6:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
Aug 28 13:32:23 bunsen kernel: [17416.014996] sd 6:0:0:0: Attached scsi generic sg2 type 0
Aug 28 13:32:23 bunsen kernel: [17416.017158] sd 6:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
Aug 28 13:32:23 bunsen kernel: [17416.018547] sd 6:0:0:0: [sdb] Write Protect is off
Aug 28 13:32:23 bunsen kernel: [17416.019543] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Aug 28 13:32:23 bunsen kernel: [17416.031073]  sdb: sdb1 sdb2
Aug 28 13:32:23 bunsen kernel: [17416.034934] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Aug 28 13:32:24 bunsen org.gtk.Private.UDisks2VolumeMonitor[1033]: index_parse.c:191: indx_parse(): error opening /media/sector11/Debian testing amd64 1/BDMV/index.bdmv
Aug 28 13:32:24 bunsen org.gtk.Private.UDisks2VolumeMonitor[1033]: index_parse.c:191: indx_parse(): error opening /media/sector11/Debian testing amd64 1/BDMV/BACKUP/index.bdmv
Aug 28 13:32:24 bunsen org.freedesktop.Notifications[1033]: /home/sector11/.themes/NewSlickness-brushed/gtk-2.0/panel.rc:32: Unable to locate image file in pixmap_path: "shadows/window-bg.png"
Aug 28 13:35:41 bunsen kernel: [17614.510536] usb 1-10: USB disconnect, device number 2
Aug 28 13:35:42 bunsen kernel: [17614.870895] usb 2-10: new full-speed USB device number 2 using ohci-pci
Aug 28 13:35:42 bunsen kernel: [17615.071144] usb 2-10: not running at top speed; connect to a high speed hub
Aug 28 13:35:42 bunsen kernel: [17615.089188] usb 2-10: New USB device found, idVendor=0781, idProduct=5567
Aug 28 13:35:42 bunsen kernel: [17615.089192] usb 2-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 28 13:35:42 bunsen kernel: [17615.089194] usb 2-10: Product: Cruzer Blade
Aug 28 13:35:42 bunsen kernel: [17615.089196] usb 2-10: Manufacturer: SanDisk
Aug 28 13:35:42 bunsen kernel: [17615.089197] usb 2-10: SerialNumber: 200429068307CA908363
Aug 28 13:35:42 bunsen mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-10"
Aug 28 13:35:42 bunsen mtp-probe: bus: 2, device: 2 was not an MTP device
Aug 28 13:35:42 bunsen kernel: [17615.092258] usb-storage 2-10:1.0: USB Mass Storage device detected
Aug 28 13:35:42 bunsen kernel: [17615.092376] scsi7 : usb-storage 2-10:1.0
Aug 28 13:35:43 bunsen kernel: [17616.100679] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
Aug 28 13:35:43 bunsen kernel: [17616.100976] sd 7:0:0:0: Attached scsi generic sg2 type 0
Aug 28 13:35:43 bunsen kernel: [17616.111684] sd 7:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
Aug 28 13:35:43 bunsen kernel: [17616.124705] sd 7:0:0:0: [sdb] Write Protect is off
Aug 28 13:35:43 bunsen kernel: [17616.137723] sd 7:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Aug 28 13:35:43 bunsen kernel: [17616.205826]  sdb: sdb1 sdb2
Aug 28 13:35:43 bunsen kernel: [17616.254906] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Aug 28 13:35:54 bunsen kernel: [17627.093413] usb 2-10: USB disconnect, device number 2

Now I'll run: sudo partprobe /dev/sdb - had to remount it:

 28 Aug 15 | 13:35:29 ~
    $ sudo partprobe /dev/sdb
[sudo] password for sector11: 
Error: Could not stat device /dev/sdb - No such file or directory.
 
 28 Aug 15 | 13:36:41 ~
    $ sudo partprobe /dev/sdb
Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
 
 28 Aug 15 | 13:37:04 ~
    $ 

Is there no way to "reformat" these suckers and get them out of: ls -l /dev/disk/by-id/*

I simply cannot dd an ISO to them.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#20 2015-08-28 17:15:05

hhh
Cityspeak
Registered: 2010-08-04
Posts: 3,253

Re: [Solved] Weird happenings with USB sticks - HELP!

I've seen USB weirdness before, but to have 4 USB's go out simultaneously? You have multiple operating systems, it's the same on all of them?

dd or cp should work with the drive unmounted and regardless of the drive's current filesystem as it wipes the drive anyway.

When I reformat a drive after I've burned an ISO to it I usually dd all zero's to it...
https://wiki.archlinux.org/index.php/Se … pe_disk#dd

Then I fire up Gparted>Device>Create Partition Table>msdos, and then reformat the drive as FAT 32.


bunsenlabs     8)     forum mod squad

Offline

#21 2015-08-28 17:17:39

damo
#! gimpbanger
From: N51.5 W002.8 (mostly)
Registered: 2011-11-24
Posts: 5,434

Re: [Solved] Weird happenings with USB sticks - HELP!

usb3 drives often throw up parted errors, but I've always managed to write isos to them.


BunsenLabs Group on deviantArt
damo's gallery on deviantArt
Openbox themes
Forum Moderator smile

Offline

#22 2015-08-28 18:45:53

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

Booted into #! Wheezy

- and still there writing this post (also see post #14 and 15 here)

SanDick Cruzer Blade 8GB plugged in:

gparted:

/dev/sdb contains GPT signatures, indicating that it has a GPT table.  However, it does not have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are now using an msdos partition table.  Is this a GPT partition table?

Said: no

gparted shows: /dev/sdb

  • Partition: unallocated

  • File System: unalocated

  • Size: 7.45GiB

  • Used: ---

  • Unused: ---

  • Flags:

thunar shows:

file:///media/Debian%20testing%20amd64%201/.disk
file:///media/Debian%20testing%20amd64%201/boot
file:///media/Debian%20testing%20amd64%201/css
file:///media/Debian%20testing%20amd64%201/debian
file:///media/Debian%20testing%20amd64%201/dists
file:///media/Debian%20testing%20amd64%201/doc
file:///media/Debian%20testing%20amd64%201/efi
file:///media/Debian%20testing%20amd64%201/firmware
file:///media/Debian%20testing%20amd64%201/install
file:///media/Debian%20testing%20amd64%201/install.amd
file:///media/Debian%20testing%20amd64%201/isolinux
file:///media/Debian%20testing%20amd64%201/pics
file:///media/Debian%20testing%20amd64%201/pool
file:///media/Debian%20testing%20amd64%201/tools
file:///media/Debian%20testing%20amd64%201/autorun.inf
file:///media/Debian%20testing%20amd64%201/g2ldr
file:///media/Debian%20testing%20amd64%201/g2ldr.mbr
file:///media/Debian%20testing%20amd64%201/md5sum.txt
file:///media/Debian%20testing%20amd64%201/README.html
file:///media/Debian%20testing%20amd64%201/README.mirrors.html
file:///media/Debian%20testing%20amd64%201/README.mirrors.txt
file:///media/Debian%20testing%20amd64%201/README.source
file:///media/Debian%20testing%20amd64%201/README.txt
file:///media/Debian%20testing%20amd64%201/setup.exe
file:///media/Debian%20testing%20amd64%201/win32-loader.ini

Unmounted and ejected - then plugged it in again:

gparted:

/dev/sdb contains GPT signatures, indicating that it has a GPT table.  However, it does not have a valid fake msdos partition table, as it should.  Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables.  Or perhaps you deleted the GPT table, and are now using an msdos partition table.  Is this a GPT partition table?

Said: yes

gparted shows: /dev/sdb

  • Partition: unallocated

  • File System: unalocated

  • Size: 7.45GiB

  • Used: ---

  • Unused: ---

  • Flags:

 28 Aug 15 | 15:41:54 ~
    $ sudo ls -l /dev/disk/by-id/*usb*
[sudo] password for sector11: 
lrwxrwxrwx 1 root root  9 Aug 28 15:35 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 28 15:32 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 28 15:32 /dev/disk/by-id/usb-SanDisk_Cruzer_Blade_200429068307CA908363-0:0-part2 -> ../../sdb2
 
 28 Aug 15 | 15:42:02 ~
    $ 

NOW I'M ANGRY:

 28 Aug 15 | 15:42:02 ~
    $ dmesg|tail
[  180.957179] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.26 PQ: 0 ANSI: 5
[  180.957827] sd 7:0:0:0: Attached scsi generic sg2 type 0
[  180.959050] sd 7:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[  180.960693] sd 7:0:0:0: [sdb] Write Protect is off
[  180.960696] sd 7:0:0:0: [sdb] Mode Sense: 43 00 00 00
[  180.961541] sd 7:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  180.971670]  sdb: sdb1 sdb2
[  180.975138] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[  181.189390] ISO 9660 Extensions: Microsoft Joliet Level 3
[  181.190787] ISO 9660 Extensions: RRIP_1991A
 
 28 Aug 15 | 15:43:06 ~
    $ 

Microsoft!!!!!!!!!!!!!!!!!!!!!!!!!    What The Hell?  mad  mad


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#23 2015-08-28 18:54:40

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

@ hhh - trying this now:

dd if=/dev/zero of=/dev/sdb iflag=nocache oflag=direct bs=4096

Hope it works ... it's slow!


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

#24 2015-08-28 18:57:23

Sector11
#!'er to BL'er
From: SR11 Cockpit
Registered: 2010-05-05
Posts: 15,667
Website

Re: [Solved] Weird happenings with USB sticks - HELP!

@ HoaS & johnraff

I tried those and 'thought' I had posted results .. sad
Will check again later.


·  ↓   ↓   ↓   ↓   ↓   ↓  ·
BunsenLabs Forums now Open for Registration
·  ↑   ↑   ↑   ↑   ↑   ↑  · BL ModSquad

Offline

Be excellent to each other!

#25 2015-08-28 19:19:58

hhh
Cityspeak
Registered: 2010-08-04
Posts: 3,253

Re: [Solved] Weird happenings with USB sticks - HELP!

Sector11 wrote:

@ hhh - trying this now:

dd if=/dev/zero of=/dev/sdb iflag=nocache oflag=direct bs=4096

Hope it works ... it's slow!

Oh yeah, that 8G drive will take quite a while.


bunsenlabs     8)     forum mod squad

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo