From: Michel <mi...@da...> - 2003-01-09 11:54:02
|
On Don, 2003-01-09 at 10:33, Geert Uytterhoeven wrote: > On 8 Jan 2003, Kulwant Bhogal wrote: > > > If it's the RDSK partition code, we can probably fix it by looking at > > > your RDB. You can extract the RDB by dumping the first 2 cylinders to a > > > file: > > > dd if=/dev/sdb of=rdb.dump bs=4k count=xxx > > > > > Set `xxx' such that `xxx*4096' equals the number of bytes in the first 2 > > > cylinders of the disk (use HdToolBox to find out the cylinder size). > > > Then sent us the output of `hexdump rdb.dump'. > > > > OK, because I got a count of 615 blocks per cylinder, I used > > 615*2*4096=5,038,080 as the count. So the commandline I used was: > > > > # dd if=/dev/sdb of=rdb.dump bs=4k count=5038080 ^^^^^^^^^^^^^^^^^^^ > > > > After a few moments I got back: > > > > dd: /dev/sdb: Input/output error > > > > ho hum. > > Looks like the driver itself has problems. Is the RDB really 20 gigs though? :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |