Re: SanDisk SDCFB 48 Partition Table
Bastien CAZENAVE wrote:
>
> Hi,
> Maybe you guys from debian-boot could know about this...
>
> While trying to make a CompactFlash IDE SanDisk SDCFB 48 bootable, I
> experienced a problem with fdisk:
> when I wrote the new partition table to disk, erasing the old DOS/FAT16
> one shipped with the SDCFB, the system hanged up...
> Now, I just can't run fdisk anymore, I get the following error message:
>
> hda:hda: read_intr: error=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
> end_request: I/O error, dev 03:00, sector 0
> unable to read partition table
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> Using /dev/hda as default device!
> hda:hda: read_intr: error=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
> end_request: I/O error, dev 03:00, sector 0
> unable to read partition table
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> hda:hda: read_intr: error=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
> end_request: I/O error, dev 03:00, sector 0
>
> and the 'dd if=/dev/zero of=/dev/hda1 bs=512 count=1' command issues the
> following error message:
>
> hda:hda: read_intr: error=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=0, sector=0
> end_request: I/O error, dev 03:00, sector 0
> unable to read partition table
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> dd: /dev/hda1: No space left on device
> 1+0 records in
> 0+0 records out
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
>
> Is it a hardware problem (though it worked fine with the old FAT16
> slice) ?
> Or did I completely screw it up with the whole partitioning method ???
>
> Any comments or solutions are greatly welcome.
>
> Thanks.
Looks like a hardware thing to me, but i dont know about how your
hardware works.
Does linux detect it on bootup (can you see mention of it in dmesg ?)
Is it possible that it uses a sector size other than 512 bytes ?
If so you have to pass the argument to fdisk at run time.
Reply to: