Deleting..Partitions do not end on a cylinder boundary

colinj

New Member
Have had the deleting issue for the second time.
Fixdisk made things better the first time, but not having as much luck now.

Partition sda1 - Unrecognised partition type, aborting...

Humax HDR-Fox T2 (humax) 1.03.12/3.10

To return to the menu, type: exit


humax# fdisk -lu /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 8 2104510 1052251+ 83 Linux
Partition 1 does not end on cylinder boundary
/dev/sda2 2104512 1932539166 965217327+ 83 Linux
Partition 2 does not end on cylinder boundary
/dev/sda3 1932539168 1953520063 10490448 83 Linux
Partition 3 does not end on cylinder boundary

Any thoughts or suggestions would be great
 
The warnings about the partition boundary are nothing to be worried about, partition boundary alignment is an outdated concept which some older tools still warn about.

Partition sda1 - Unrecognised partition type, aborting...
This is the first problem - luckily partition 1 is not important and you can reformat it without losing anything (the EPG data it holds will come back).

Try this from the command line first then retry fix-disk:

Code:
humax# umount /mnt/hd1
humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda1
 
Just checked what's installed in CFW 3.10 and gdisk -l /dev/sda is probably the best tool to use for listing the partitions.
 
The warnings about the partition boundary are nothing to be worried about, partition boundary alignment is an outdated concept which some older tools still warn about.


This is the first problem - luckily partition 1 is not important and you can reformat it without losing anything (the EPG data it holds will come back).

Try this from the command line first then retry fix-disk:

Code:
humax# umount /mnt/hd1
humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda1
Thanks for the help af123, that seems to have sorted the deleting issue.
Fixdisk does report an error at LDA 0 which seems to go around in a loop (I think it did that last time).
 
Back
Top