I am dissapointed to see "long answers" to "short spurious claims".
Nick, your long mail didn't help anything. Chris, your report sucks. Use sendbug and file a bug report with no details missing. Not one user has reported a drive missing on a ahci controller before you, and suddenly you say (paraphasing) "oh i hear this is very common!"). The intentionally vague way you approach this looks like you want to make us look bad. Nick Holland <[email protected]> wrote: > On 11/30/21 3:30 PM, Chris Bennett wrote: > > After looking over the list, it looks like many SSD's have compatibility > > problems, so I'm just going to switch over to a spinning drive. > > Sorry for the noise. > > > > categorical nonsense. > > SSDs work. Cheap ones work, expensive ones work. Some work better than > others, I wish cost predicted success, hasn't in my experience, but > some IBM branded SAN SSD drives have had an oddly low rate of failure at > work...but then each drive probably costs as much as one of my cars, > and stores a very modest amount of data...so maybe at the really high > end you get what you pay for. maybe. > > I've had nothing but problems with /some/ Samsung drives, good luck > with some junk no-name drives, but the key thing is...if the SATA or SAS > port the drive is plugged into works, the drive will be recognized and > work (though maybe better or worse than you wish...but that's not an OS > issue). > > For a system to boot, the BIOS must support the drive. For the system > to get installed, the OS must support the drive. You can boot a kernel > from a disk the OS doesn't recognize, and you can install the OS to a > drive the system can't boot from. The fact that you "see" the drive in > the BIOS means only that the drive is hooked up properly. Doesn't > indicate OS support. > > Make sure your BIOS is set to support the drives as "AHCI" if that's an > option. If you see "RAID", that won't work for good reasons. If the > drive is attached to a real RAID controller, the controller may not be > supported, or you may have it configured wrong (i.e., the drives are there, > but not configured on the RAID Card, so the RAID card isn't presenting > "drives" to the OS). > > Provide useful info rather than stomping your feet and saying "it worked > before!". Obviously, things are different. The answer is almost > certainly in the dmesg. > > Nick. >
