[Novalug] ARRG!! Strange SSD Revisited
jplace at unixsage.com
Thu Dec 23 11:33:40 EST 2010
1) Try just using raw partitions no lvm (doubtful)
2) do a text mode install from the DVD, sometimes extra errors come out
during install that may help localize it.
Odd problem to say the least... I am running 14 but I do not have any
On 12/23/2010 11:20 AM, Jon LaBadie wrote:
> A few days ago I started a short thread (Strange SSD)
> describing my problems trying to install Fedora 14
> on a Solid State Disk (MicroCenter house brand, 64GB).
> Feeling that drive may have been defective I returned
> it and purchased a similar drive from a different
> manufacturer (OCZ Agility 2).
> The new drive is acting the same way as first; after
> seeming to work it shifts from looking to the system
> as a SATA II interface to a SATA I. The system thinks
> it has no partitions, 0 capacity and all I/O fails.
> One major difference this time. I booted my Fedora 9
> image (same machine, different disk) and worked with
> the SSD for 2 days before attempting to install to it.
> The new SSD was partitioned as follows (MBR style):
> 1. 4GB Swap formatted and used under Fedora 9
> 2. 1GB Ext4 formatted, planned for /boot
> 3. 52GB Remainder as an LVM2 Physical Volume
> A Virtual Group of 30GB was created on the PV and
> formatted as Ext4 to be used as Fedora 14's root.
> This was then mounted under the running Fedora 9.
> Over about 30 hrs I random data into several (5)
> 5GB files mixed in a couple of reboots. Never
> a hiccup.
> Next, I tried to install Fedora 14 from an Installation
> DVD. First time it reached the "scanning storage"
> pop-up and hung. I restarted the install and got to
> the same pop-up. After a minute an error screen
> came up. A third attempt got an error screen with
> the option of "reinitializing the devices". I selected
> reinitialize and it found the partitions. However
> I got the error screen when I tried to redo the
> Next I tried the Fedora 14 Live CD, booted and clicked
> "Install to Disk" desktop icon. Again it errored
> while scanning storage.
> So, might it be an Anaconda bug? I did not see
> anything by googling for it. Suggestions?
More information about the Novalug