On 5/28/07, Otavio Salvador <[EMAIL PROTECTED]> wrote:
"Matt Davis" <[EMAIL PROTECTED]> writes:
> fat_bootsector_read() returns all zeros to the buffer.
> The _device_seek() is seeking to the proper location, and there is
> actually data in that location, which I have confirmed via 'dd' (with
> appropriate bootsector signature)
This paragraph isn't clear to me.
When you say that there is actually data you means bootsector
signature or ordinary data?
dd reports a proper boot sector signature. Parted is reporting that
that same region is all 0x0.
> Is this some oddity with qemu and virtual disks? Fdisk and cfdisk
> read the partition's boot sector fine. It seeks to sector 63, sucks
> in 512b of bootsector data. And read returns sucessfully (512b read).
> The data it copies into diobuf is 0x0 for 512 bytes. I do not have a
> spare drive lying around, (although I can try to pick one up this
> week) to compare against. Sounds to me if qemu is doing something
> funky. But that's just some speculation right now. Although, parted
> does read other partitions fine.
dd returns only 0x0?
Nope, dd is reporting appropriate data, while parted says a successful
read of all 512 bytes is all 0x0.
-Matt
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
_______________________________________________
bug-parted mailing list
bug-parted@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-parted
