Page 1 of 1

Is problem machine, not drive?

Posted: Sat Apr 02, 2016 2:56 am
by kilaueabart
Some time last year I replaced an apparently ailing rotary hard drive with a 500GB SSD, and successfully installed Ubuntu LT 12.04 on it as /dev/sdb1, followed later by a desktop-less Ubuntu 15.10 at /dev/sdb2, each of them allotted a too-generous roughly 250GB.

Maybe three months ago, I started to have trouble with 12.04 on the SSD. I decided to back up what I needed and reformat /dev/sdb1 for a fresh install. But all attempts to reformat the partition, as well as the whole drive, fell short. My guess was the drive had gone bad, and I really regretted not remembering where I had bought it and whether I had a warranty on it.

Today I received and installed a new, smaller SSD, and set about installing Ubuntu 12.04 on it. Well, same problem, which I will try to illustrate with a screen shot.
Screenshot from 2016-04-01 14-18-44.png
This suggests to me that there must be something wrong with my nice X1000 that prevents proper communication with some devices. So far, /dev/sda which contains all my AOS stuff plus a slightly sickly version of Ubuntu 12.04 seems OK.

What can I do to precisely analyze the situation?

Re: Is problem machine, not drive?

Posted: Sat Apr 02, 2016 5:09 am
by jdupuis
Hello, Sir!

After Boot-up with Ubuntu 12.04. Use GParted, choose your new SSD drive and create an MS-DOS Partion Table then format as one FAT32 Primary. <Restart> This should take care of your "bad sector". Delete the FAT32 partition so it shows "Unallocated". During install "Use Entire Disk" or "Do Something Else" to set up as you like.
I did this with the recent SATA HD I just added to my X1000 and went without a hitch. Hope this helps.

Cheers!
John