It is recognized as /dev/sdc1 and can be mounted and accessed with mount /dev/sdc1 /mnt
There is no icon for it on the desktop, unlike the case of other removable devices. I found another problem by doing this that should really be a new topic. It doesn't seem to play too nice with FreeBSD: Device Boot Start End Blocks Id System /dev/sdb1 * 48693 121602 585646299 a5 FreeBSD Partition 1 does not end on cylinder boundary. /dev/sdb2 14650 48692 273437697 5 Extended Partition 2 does not end on cylinder boundary. /dev/sdb5 14650 15258 4882432 82 Linux swap / Solaris /dev/sdb6 15258 18298 24413184 83 Linux /dev/sdb7 18298 48692 244140032 83 Linux Partition table entries are not in disk order For that reason, for example, Clonezilla doesn't want to save partitions on this drive. Comments on that subject would be welcome too. Robert "Tim" Kopp http://analytic.tripod.com/ ________________________________ From: chris (fool) mccraw <[email protected]> To: "General Linux/UNIX discussion and help, civil and on-topic" <[email protected]> Sent: Fri, November 12, 2010 12:51:02 PM Subject: Re: [PLUG] USB Key Not Detected On Fri, Nov 12, 2010 at 12:44, Robert Kopp <[email protected]> wrote: > lsusb mentions this device, and lsmod seems to indicate that usb_storage is > loaded. > > A Lexar keychain drive is immediately recognized and mounted. It could be that > the other one is just not automounted. How would I check this (it's been so >long > since I had to mount such a device manually that I forgot how to do it)? well, if 'dmesg' indicates that it sees a scsi drive, you can find out what its partition table is with 'fdisk -l' and then mount whatever partition exists (probably sdX1 for some alphabetical value of X) as: mount /dev/sdXY /mnt if dmesg doesn't spit out a bunch of stuff about how it found a new mass storage device and assigned it a drive letter, something deeper is wrong and posting the output here is going to be necessary for further troubleshooting. > I could solve the immediate problem by using Windows to copy the files from the > smaller drive that is not recognized by Maverick to the larger one that is. but that's a bummer! _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
