Anonym
tried to send bug report but connection timed out as gnome settings
as per email before.
re dmesg that was ok but would not copy I did in fact stop the process myself as i noticed there was nothing in the usb stick here is the output the usb mounts by default when placed in the usb slot.
maybe i could try another usb stick
dmesg output
------------------------------------------------------------------
[ 1742.516354] usb-storage: device scan complete
[ 1742.516843] scsi 9:0:0:0: Direct-Access SanDisk U3 Cruzer Micro 3.27 PQ: 0 ANSI: 2
[ 1742.517212] scsi 9:0:0:1: CD-ROM SanDisk U3 Cruzer Micro 3.27 PQ: 0 ANSI: 2
[ 1742.520038] sd 9:0:0:0: Attached scsi generic sg6 type 0
[ 1742.523331] sd 9:0:0:0: [sdf] 8015502 512-byte logical blocks: (4.10 GB/3.82 GiB)
[ 1742.524830] sd 9:0:0:0: [sdf] Write Protect is off
[ 1742.524833] sd 9:0:0:0: [sdf] Mode Sense: 03 00 00 00
[ 1742.524836] sd 9:0:0:0: [sdf] Assuming drive cache: write through
[ 1742.525329] sr1: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray
[ 1742.525408] sr 9:0:0:1: Attached scsi CD-ROM sr1
[ 1742.525468] sr 9:0:0:1: Attached scsi generic sg7 type 5
[ 1742.529944] sd 9:0:0:0: [sdf] Assuming drive cache: write through
[ 1742.529949] sdf: sdf1
[ 1742.532325] sd 9:0:0:0: [sdf] Assuming drive cache: write through
[ 1742.532328] sd 9:0:0:0: [sdf] Attached SCSI removable disk
[ 1742.800708] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 1981.688450] sg_write: data in/out 2080423089/4050 bytes for SCSI command 0xf3--guessing data in;
[ 1981.688452] program cat not setting count and/or reply_len properly
[ 2288.916667] sr 7:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2288.916672] sr 7:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 2288.916676] Info fld=0x46a96, ILI
[ 2288.916678] sr 7:0:0:0: [sr0] Add. Sense: Illegal mode for this track
[ 2288.916684] sr 7:0:0:0: [sr0] CDB: Read(10): 28 00 00 04 6a 78 00 00 20 00
[ 2288.916692] end_request: I/O error, dev sr0, sector 1157600
[ 2288.916696] Buffer I/O error on device sr0, logical block 289400
[ 2288.916700] Buffer I/O error on device sr0, logical block 289401
[ 2288.916704] Buffer I/O error on device sr0, logical block 289402
[ 2288.916707] Buffer I/O error on device sr0, logical block 289403
[ 2288.916709] Buffer I/O error on device sr0, logical block 289404
[ 2288.916712] Buffer I/O error on device sr0, logical block 289405
[ 2288.916714] Buffer I/O error on device sr0, logical block 289406
[ 2288.916717] Buffer I/O error on device sr0, logical block 289407
[ 2288.916719] Buffer I/O error on device sr0, logical block 289408
[ 2288.974928] sr 7:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2288.974932] sr 7:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 2288.974936] Info fld=0x46a96, ILI
[ 2288.974938] sr 7:0:0:0: [sr0] Add. Sense: Illegal mode for this track
[ 2288.974942] sr 7:0:0:0: [sr0] CDB: Read(10): 28 00 00 04 6a 96 00 00 02 00
[ 2288.974950] end_request: I/O error, dev sr0, sector 1157720
amnesia:~#
-------- Original-Nachricht --------
> Datum: Tue, 23 Nov 2010 00:12:22 +0100
> Von: anonym <anonym@???>
> An: "The T(A)ILS public development discussion list" <tails-dev@???>
> Betreff: Re: [T(A)ILS-dev] some problems
> 22/11/10 22:23, tim smy:
> > I was wondering how I might check to see which sda or sda1 the usb is
> > monuted on. I tried to install unetbootin from the command line but
> > its not available.
>
> Well, what I usually do is: insert the usb drive (but don't mount it)
> during a T(A)ILS session, then issue the command
>
> dmesg
>
> in a terminal. The device name appears at numerious times in the end of
> the output, within [square brackets]. For instance, I see something like
> the following:
>
> ...
> [1078315.361139] sd 19:0:0:0: Attached scsi generic sg4 type 0
> [1078315.362050] sd 19:0:0:0: [sdd] 3940479 512-byte logical blocks:
> (2.01 GB/1.87 GiB)
> [1078315.368128] sd 19:0:0:0: [sdd] Write Protect is off
> [1078315.368333] sd 19:0:0:0: [sdd] Mode Sense: 45 00 00 08
> [1078315.368338] sd 19:0:0:0: [sdd] Assuming drive cache: write through
> [1078315.371700] sd 19:0:0:0: [sdd] Assuming drive cache: write through
> [1078315.371710] sdd: sdd1
> [1078315.376917] sd 19:0:0:0: [sdd] Assuming drive cache: write through
> [1078315.376924] sd 19:0:0:0: [sdd] Attached SCSI removable disk
>
> which means that /dev/sdd is the device the usb drive was assigned. Then
> I simply do a
>
> cat /dev/cdrom > /dev/sdd
>
> which installs T(A)ILS to the usb drive.
>
> > Would it be woth formatting the usb first?
>
> No.
>
> Cheers!
>
--
GRATIS! Movie-FLAT mit über 300 Videos.
Jetzt freischalten unter
http://portal.gmx.net/de/go/maxdome
