I'm having one of the most perplexing issues I've ever encountered and can't seem to find any record of anyone having similar issues (though it's possible my search engine skills are failing me), so was wondering if anyone had any input.
I run Fedora 15 on a 128 GB Kingston SSD and have had no issues up to this point. Today, I installed some software (just libreoffice-base, nothing system related) and it seemed to install fine, but upon attempting to open libreoffice was getting a weird error message. Upon trying to run it a few more times, Java was crashing as detected by ABRT, so to eliminate the possibility that something was just borked, I went for the Windows approach and rebooted.
Upon rebooting, however, I was treated (consistently) to a ramdisk: inconsistent write kernel panic. Figuring something was messed up in the kernel/bootloader, I attempted to get into my bootloader options, but it would not accept my bootloader password, strangely. I then booted with the install CD into recovery mode and went into grub.conf and deleted my bootloader password. Upon rebooting, however, the bootloader was still asking for a password. Booting into recovery mode once more revealed that grub.conf appeared to be unaltered by my previous edit. I then pulled the drive out and stuck it in an external enclosure and accessed it with another computer, bringing us to the bottom line:
I apparently cannot permanently write to my SSD. With the drive mounted, I can view and edit files normally, and the changes appear to be persistent. However, upon unmounting/remounting, all writes have been reversed. This is probably the root cause of all of the above mentioned software and kernel panic issues.
My question is this: How do I go about figuring out whether this is a hardware problem or something else? I don't think it's a filesystem issue; the problem occurs on all three partitions that were on the drive and fsck reveals no problems. Has anyone heard of an issue like this, and is it likely that my SSD is just dead and needs to be RMA'd?
---------- Post added at 11:30 PM ---------- Previous post was at 10:31 PM ----------
Okay, the issue is definitely hardware related... The drive will not even format. Any attempt to format "completes successfully" but does not actually affect the disk... Any thoughts are still appreciated, however.