Re: Easy way to recover disk

2001-01-04 Thread Julian Stacey [EMAIL PROTECTED]
Warner Losh wrote: > OK. I have a disk drive that is failing in random ways. Today blocks > 123 456 and 293 might be unreadable. Tomorrow, it might be these and > 27 or it might just be 27. It is an IDE drive. I was wondering if anybody > had a program that would read the entire disk and kee

Re: Easy way to recover disk (fwd)

2000-12-30 Thread Mark Hittinger
> :I thought the linux badblocks program found bad blocks and keep the > :user from using them. I want to read the entire disk and the parts > :that don't read I want to try again later to see if I can maybe get > :lucky. The linux program creates a data file which the fsckext program uses to a

Re: Easy way to recover disk

2000-12-30 Thread Matt Dillon
:In message <[EMAIL PROTECTED]> Matthew Jacob :writes: :: Isn't this what the Linux badblocks program is for? Why don't you take that :: and find a way to feed this into badsect(8)... : :I thought the linux badblocks program found bad blocks and keep the :user from using them. I want to read th

Re: Easy way to recover disk

2000-12-30 Thread Aleksandr A.Babaylov
Warner Losh writes: > The only thing I couldn't figure out how to do was to mount the file. > Since I grabbed the disk partition, I wasn't sure I could just use > vnconfig since there was no FreeBSD label on that partition. vnconfig -s labels /dev/vn... -- @BABOLO http://links.ru/ To Unsu

Re: Easy way to recover disk

2000-12-29 Thread Warner Losh
In message <[EMAIL PROTECTED]> Matthew Jacob writes: : No, badblocks always reads the whole disk- it emits a list of badblocks. : It's e2fsck that is then used to tell the filesystem that these blocks are : unavailable. Ah. Yes. I see now. It would be useful. Before I discovered this I hacke

RE: Easy way to recover disk

2000-12-29 Thread Matthew Jacob
On Fri, 29 Dec 2000, Jonathan Graehl wrote: > What do you mean, you can have multiple outstanding reads like in SCSI? > I thought the IDE protocol was fundamentally unable to handle the > concept. I dunno- check out Soren's work. > > I also thought that IDE drives have been transparently rem

RE: Easy way to recover disk

2000-12-29 Thread Jonathan Graehl
What do you mean, you can have multiple outstanding reads like in SCSI? I thought the IDE protocol was fundamentally unable to handle the concept. I also thought that IDE drives have been transparently remapping bad blocks (and failing only when they run out of spares) for quite a few years now.

Re: Easy way to recover disk

2000-12-29 Thread Matthew Jacob
On Fri, 29 Dec 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Matthew Jacob >writes: > : Isn't this what the Linux badblocks program is for? Why don't you take that > : and find a way to feed this into badsect(8)... > > I thought the linux badblocks program found bad blocks and keep

Re: Easy way to recover disk

2000-12-29 Thread Warner Losh
In message <[EMAIL PROTECTED]> Matthew Jacob writes: : Isn't this what the Linux badblocks program is for? Why don't you take that : and find a way to feed this into badsect(8)... I thought the linux badblocks program found bad blocks and keep the user from using them. I want to read the entire

Re: Easy way to recover disk

2000-12-29 Thread Matthew Jacob
Isn't this what the Linux badblocks program is for? Why don't you take that and find a way to feed this into badsect(8)... > OK. I have a disk drive that is failing in random ways. Today blocks > 123 456 and 293 might be unreadable. Tomorrow, it might be these and > 27 or it might just be 27

Easy way to recover disk

2000-12-29 Thread Warner Losh
OK. I have a disk drive that is failing in random ways. Today blocks 123 456 and 293 might be unreadable. Tomorrow, it might be these and 27 or it might just be 27. It is an IDE drive. I was wondering if anybody had a program that would read the entire disk and keep a list/bitmap of the bad b