You are right, Gene! I did not notice that it was written to partition
"/dev/sda1", because I didn't expect this test to only be written to a
partition instead of test writing to the whole disk. I have not noticed
this detail in the answer when replying to it, shame on me.
My recommendation was to use the command like this:
sudo dd if=/dev/zero of=/dev/WritingToThisDisk bs=8M status=progress
Long Wind, the test works only if you overwrite the full disk. So, as
Gene pointed out, after the test which you did by now it cannot be
concluded what I concluded in my former answer!
We by now only know that writing to the 14 GB of partition "/dev/sda1"
worked correctly, but we do not know where on the disk this 14 GB are
actually located and we also still do not know about the rest of the
disk and if it continues to work fine also for a bigger data load
occupying the electronics for longer time.
So, if you are interested to still know about your old drive, although
you said that you already installed successfully to a new drive, then
you may want to direct the test all the device and not only a partition
of it.
Best regards,
Marco.
Thank Marco! i can't do test on whole disk because i have useful files in other partitions. smartctl report gives me some confidence in the problem disk. i've installed buster to the problem disk and am using it now to write this mail. i can backup files in problem disk if they r important. below is layout of problem disk reported by fdisk:
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: ST3320311CS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x059a302a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 1606500 29768444 28161945 13.4G 83 Linux
/dev/sda2 92164905 215047779 122882875 58.6G 7 HPFS/NTFS/exFAT
/dev/sda3 215048192 625137663 410089472 195.6G 7 HPFS/NTFS/exFAT
/dev/sda4 29768445 89305334 59536890 28.4G 83 Linux
Partition table entries are not in disk order.