public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: usb-storage: how to ruin your hardware(?)
Date: Fri, 29 Aug 2003 10:25:50 +0000 (UTC)	[thread overview]
Message-ID: <bin9ne$u7n$1@tangens.hometree.net> (raw)
In-Reply-To: 200308281618.h7SGIMMp014455@wildsau.idv.uni.linz.at

"H.Rosmanith (Kernel Mailing List)" <kernel@wildsau.idv.uni.linz.at> writes:

>> On Thu, Aug 28, 2003 at 04:59:14AM +0200, H.Rosmanith (Kernel Mailing List) wrote:
>> 
>> > the contradiction to this is that the flashdisk can be used
>> > in a "partition-less" state where it is possible to use the
>> > whole device at one: "mke2fs /dev/sdb". you have to use the
>> > vendor formating-tool to make the flashdisk look like an USB_FDD
>> > device. but even in USB_HDD mode with partitions, the partitions
>> > still look strange, not ending on cylinder boundaries and so on.
>> 
>> I have seen several posts from you, but all in this vague, almost
>> information-free style.

>the information is vague, because I don't exactly know how I manage
>to stop the drive working.

Back it up:

dd if=/dev/sda of=/tmp/save bs=512 count=<number of blocks on your flash disk>

Clean it:

dd if=/dev/zero of=/dev/sda bs=512 count=100

See what happens. If it does not work any longer, we can take a peek
at the backup (especially the first few sectors).

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire

"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!" 
      -- AOL CD when played backwards  (User Friendly - 200-10-15)

  parent reply	other threads:[~2003-08-29 10:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21  1:34 usb-storage: how to ruin your hardware(?) 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
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 [this message]
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='bin9ne$u7n$1@tangens.hometree.net' \
    --to=hps@intermeta.de \
    --cc=linux-kernel@vger.kernel.org \
    /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