mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: "H.Rosmanith (Kernel Mailing List)" <kernel@wildsau.idv.uni.linz.at>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: usb-storage: how to ruin your hardware(?)
Date: 21 Aug 2003 08:17:20 +0200	[thread overview]
Message-ID: <1061446640.3390.51.camel@workshop.saharacpt.lan> (raw)
In-Reply-To: <200308210205.h7L25PI6012011@wildsau.idv.uni.linz.at>

On Thu, 2003-08-21 at 04:05, H.Rosmanith (Kernel Mailing List) wrote:
> -- Start of PGP signed section.
> > For the vast majority of USB storage devices, it's not possible to kill the
> > device like you did.
> > 
> > It looks like the device firmware needs certain data on the first sector to
> > operate.  The usb-storage communication is working just fine, but the
> > device is refusing commands.
> 
> aha. do you know why the device is refusing commands? it relys on sector0
> to contain some vital information and if this is not there, it refuses
> commands?
> 

We sell a make of flashdisk (what we call your 'usb bar') that use
sector 0 with its encryption scheme.  Basically as soon as you
'encrypt' or 'password protect' or whatever the device, you cannot
get a valid partition table, and sector 0 is not writable, so
repartitioning fails.  I have not tried to just put a fs on the
whole disk, but I assume it will fail as well, as it should start
at sector 0.

Anyhow, the only way to fix this if you lost the password, is to
format the device with the software that comes with the device
(windows based only for ours) - might be the same thing your side,
you just got the device into  'lock down mode' via some fluke.

Hope this might be of some help, else take it back.  Our side
at least if not burned or damaged, we would replace it.


Regards,

-- 
Martin Schlemmer



  parent reply	other threads:[~2003-08-21  6:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21  1:34 H.Rosmanith (Kernel Mailing List)
2003-08-21  1:55 ` Matthew Dharm
2003-08-21  2:05   ` H.Rosmanith (Kernel Mailing List)
2003-08-21  2:35     ` Brandon Stewart
2003-08-21  6:17     ` Martin Schlemmer [this message]
2003-08-21 10:16   ` Maciej Soltysiak
2003-08-21  7:11 ` Alan Cox
2003-08-22 10:44   ` H.Rosmanith (Kernel Mailing List)
2003-08-27 15:11     ` H.Rosmanith (Kernel Mailing List)
2003-08-27 15:37       ` Richard B. Johnson
2003-08-27 19:33         ` root
2003-08-27 19:58           ` Richard B. Johnson
2003-08-28  2:59         ` H.Rosmanith (Kernel Mailing List)
2003-08-28 13:44           ` Andries Brouwer
2003-08-28 16:18             ` H.Rosmanith (Kernel Mailing List)
2003-08-28 20:25               ` Andries Brouwer
2003-08-29 10:25               ` Henning P. Schmiedehausen
2003-08-29 16:11                 ` H.Rosmanith (Kernel Mailing List)
2003-09-09  9:57                   ` Peter Werner
2003-09-15 22:57                     ` H.Rosmanith (Kernel Mailing List)
2003-08-27 16:10       ` Bas Mevissen
     [not found] <mMAP.NQ.15@gated-at.bofh.it>
     [not found] ` <mMUh.12N.19@gated-at.bofh.it>
     [not found]   ` <mUI5.7Hp.27@gated-at.bofh.it>
2003-08-21 12:35     ` Ihar 'Philips' Filipau
2003-08-22  1:06       ` jw schultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1061446640.3390.51.camel@workshop.saharacpt.lan \
    --to=azarah@gentoo.org \
    --cc=kernel@wildsau.idv.uni.linz.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome