TeraByte Unlimited

Hi Folks,

So I got a few read errors the other day and figured I'd check my HDDs. Using the linux command "fdisk -l" to list the partitions prior to running badblocks, I got "Partition 1 does not start on physical sector boundary."

While not a critical error (in so far as I can tell), it shows up on both my GPT disks (as opposed to my MBR drives).

Is this just a case of resizing the partitions and sliding them around?

And while I'm at it, does Bootit have a "badblocks" capability that I haven't seen?

Thanks

It's just and old leftover non-issue warning it puts out.

On 11/25/2019 6:52 AM, johnstrasser wrote:
> Hi Folks,
>
> So I got a few read errors the other day and figured I'd check my HDDs. Using the linux command "fdisk -l" to list the partitions prior to running badblocks, I got "Partition 1 does not start on physical sector boundary."
>
> While not a critical error (in so far as I can tell), it shows up on both my GPT disks (as opposed to my MBR drives).
>
> Is this just a case of resizing the partitions and sliding them around?
>
> And while I'm at it, does Bootit have a "badblocks" capability that I haven't seen?
>
> Thanks
>
>