Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!asgard!mjj From: mjj@mlb.dmt.csiro.au (Murray Jensen) Newsgroups: comp.unix.bsd Subject: Re: 2nd drive file ... (Actually wd ESDI problems) Message-ID: <195@asgard.mlb.dmt.csiro.au> Date: 16 Aug 92 16:46:50 GMT References: <16dfmeINN3u7@disaster.Germany.EU.net> Organization: CSIRO Division of Manufacturing Technology, Melbourne, Australia Lines: 23 >From article <16dfmeINN3u7@disaster.Germany.EU.net>, by bs@Germany.EU.net (Bernard Steiner): > Well, I don't have DOS. However, I noticed that dd'ing off 386bsd pertitions > will not find all bad blocks, whereas dd'ing off the 'd' 'partition' does. I used the 'c' partition because I have a DOS5 partition and a 386BSD partition (MS-DOS partitions not BSD partitions), and if I used the 'd' partition I would be told about bad sectors in the DOS partition, which bad144 can't do anything about. The 'c' partition covers the 386BSD area only, whereas the 'd' partition covers the whole disk. 'c' and 'd' are the same if you don't use DOS partitions. > BTW did your kernel actually print out the bad sectors or are you using a > modified kernel ? If it's the standard thing it does, would you mind > telling us about any magic flags you gave disklabel. No. I couldn't make the kernel print the errors - that's why you use dd. dd will tell you how many blocks it read before the error occurred, from this information and the (BSD) partition table you can work out the sector number to give to bad144. Murray... -- Murray Jensen, CSIRO Div of Manufacturing Tech, Phone: +61 3 487 9263 Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 484 0878 Internet: mjj@mlb.dmt.csiro.au ACSnet: mjj@asgard.dmt.oz