The 'partitions' are only numbers in a table that OS's refer to to see
what block starts the next partition and where it ends. I'm assuming
that your problem with the partition is actually with the filesystem on
that partition. With it unmounted, run e2fsck -cc on it.
The -cc means that a non-distructive read/write badblocks test will run
on it. With modern drives you should not actually find any bad blocks
unless the drive is at end-of-life and has used up its remapping space.
However, if it completes fine you'll know that writing beyond the 70%
range worked for the drive.
Which partition has the problem?
Also, I have only one window OS, but I don't k now why both hda1 and
hda2 are for window partitions, can I delete both of them?
I haven't run an MS product since windows 3.1 so I don't know. But
since you don't need windows and you know that neither partition is
needed, you should be able to remove them. This may end up changing the
numbering of the extended partition from hda3 to either 1 or 2.
However, the partitions in it should still start at hda5.
Please see following partition information and the debian boot is in
Master section.
sudo fdisk -l
Disk /dev/hda: 32.0 GB, 32003112960 bytes 255 heads, 63 sectors/track,
3890 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 255 2048256 7 HPFS/NTFS
/dev/hda2 256 1275 8193150 b W95 FAT32
/dev/hda3 1276 3890 21004987+ 5 Extended
/dev/hda5 1276 1504 1839411 83 Linux
/dev/hda6 2296 2298 24066 83 Linux
/dev/hda7 2299 2364 530113+ 82 Linux swap
/ Solaris /dev/hda8 2365 3890 12257563+ 83
Linux /dev/hda9 * 1505 1863 2883636 83 Linux
/dev/hda10 1864 2295 3470008+ 83 Linux
Since hda3 goes from cylinder 1276 to 3890 yet hda10 ends at 2295, there
should also be some free space at the end.
Good luck,
Doug.