Probing USB devices

Cotobear · 04-08-2008, 02:29 PM

For the longest time I've been using 'fdisk -l' to find the device node of a usb drive. Obviously fdisk requires root privileges and so I was wondering if there was a better way of finding out what it is. Something that doesn't require root privileges would be nice.

Coto

T3slider · 04-08-2008, 03:06 PM

Cotobear, maybe check the output of `dmesg` after plugging it in? (Should be right at the end)

Alien Bob · 04-08-2008, 03:15 PM

Perhaps that the output of '/sbin/blkid' will help you as non-root user.

Eric

Cotobear · 04-08-2008, 03:25 PM

Thanks both. Problem solved.

BCarey · 04-08-2008, 09:58 PM

Quote:

Originally Posted by Alien Bob

Perhaps that the output of '/sbin/blkid' will help you as non-root user.

Eric

Cool, thanks. I never knew about this. Very useful!

Brian

rkrishna · 04-12-2008, 02:25 AM

i think this is the best

Code:

 lsscsi

and this one i learned from slack 11, boot screen

Code:

 /sbin/rescan-scsi-bus

which is there in rc.scanbus script

Quote:

sh /etc/rc.d/rc.scanluns

rkrishna · 04-12-2008, 02:28 AM

i jsut tried /sbin/blkid and the bash fonts got screwed up

Code:

bash-3.1$ /sbin/blkid 
/dev/hda9: UUID="f005cbfc-7216-11da-a190-379ae730a0ef" SEC_TYPE="ext2" TYPE="ext3" 
/dev/hda1: LABEL="‰G&‰G
                       ^_É" UUID="D4EF-69CD" TYPE="┴°▒├" 
/␍␊┴/⎽␍▒1: LABEL="           FAT32   ¾┬≠¬"À├
                                             V´»" UUID="47DE-8133" TYPE="┴°▒├" 
/␍␊┴/␤␍▒7: UUID="855197▒0-86°2-435°-8␍82-02␉471°␍5°59" SEC_TYPE="␊│├2" TYPE="␊│├3" 
/␍␊┴/␤␍▒5: LABEL="           FAT32   ú3ÉŽÑ¼øπŽÁ½│" UUID="873B-0FA6" TYPE="┴°▒├" 
␉▒⎽␤-3.1$

any idea?

T3slider · 04-12-2008, 05:04 PM

That sometimes happens with random commands for me too (not reproducible, and it hasn't happened for a while -- usually sometimes when switching from X to a VT) -- I think the solution is to issue `reset`, followed by Ctrl+L twice (instead of the enter key -- Ctrl+L I think is the line-feed key combo that should always work, even if the mapping of the enter key is screwed up). I don't have that memorized, so Ctrl+L is probably wrong, but try it anyway (enter may work as well). It should be noted that this is more of a workaround instead of a preventative solution.

rkrishna · 04-13-2008, 07:00 AM

Code:

bash-3.1$ /sbin/blkid 
/dev/hda9: UUID="f005cbfc-7216-11da-a190-379ae730a0ef" SEC_TYPE="ext2" TYPE="ext3" 
/dev/hda1: LABEL="‰G&‰G
                       ^_É" UUID="D4EF-69CD" TYPE="┴°▒├" 
/␍␊┴/⎽␍▒1: LABEL="           FAT32   ¾┬≠¬"À├
                                             V´»" UUID="47DE-8133" TYPE="┴°▒├" 
/␍␊┴/␤␍▒7: UUID="855197▒0-86°2-435°-8␍82-02␉471°␍5°59" SEC_TYPE="␊│├2" TYPE="␊│├3" 
/␍␊┴/␤␍▒5: LABEL="           FAT32   ú3ÉŽÑ¼øπŽÁ½│" UUID="873B-0FA6" TYPE="┴°▒├" 
␉▒⎽␤-3.1$ ⎼␊⎽␊├   ---> reset
bash-3.1$ ls                                                                                            
bin  boot  data  dev  etc  home  lib  lost+found  media  mnt  opt  proc  root  sbin  srv  sys  tmp  usr  var
bash-3.1$

thank you,
that cntrl+l didnt worked
but the "reset" command helped,

earlier also i noticed that ,i got this kind of characters, what i used to do is. jsut close the terminal and open a new

just 'reset' saved me
but this is handy.. thankyou

T3slider · 04-13-2008, 04:05 PM

lol, Ctrl+L was stupid advice and I knew better. I use Ctrl+L to clear the console every day -- I don't know what I was thinking there. It should be Ctrl+J. And the instructions should have said Ctrl+J, followed by `reset`, followed by Ctrl+J. That way, if the enter key is messed up, you can proceed with Ctrl+J a first time to get a new line with no text on it, then type reset, then Ctrl+J to enter the command. But if the enter key still works, there's no need to use this Ctrl+J mumbo jumbo. (This info was all thanks to onebuck, so thank him, not me).