On Mon, 6 Jul 2026 15:46:29 -0600 Charles Curley <[email protected]> wrote:
> > Nope. Stock, bog-standard except for the addition of one SATA card. > > root@hawk:~# lspci -vs 4:0 > 04:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA > controller (prog-if 01 [AHCI 1.0]) Subsystem: JMicron Technology > Corp. Device 0000 Flags: bus master, fast devsel, latency 0, IRQ 31 > I/O ports at d200 [size=128] > I/O ports at d180 [size=128] > I/O ports at d100 [size=128] > I/O ports at d080 [size=128] > I/O ports at d000 [size=128] > Memory at f7c10000 (32-bit, non-prefetchable) [size=8K] > Expansion ROM at f7c00000 [disabled] [size=64K] > Capabilities: [80] Power Management version 3 > Capabilities: [90] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Capabilities: [c0] Express Legacy Endpoint, IntMsgNum 0 > Capabilities: [100] Advanced Error Reporting > Capabilities: [150] Device Serial Number > 00-00-00-00-00-00-00-00 Capabilities: [160] Power Budgeting <?> > Capabilities: [1b8] Latency Tolerance Reporting > Capabilities: [300] Secondary PCI Express > Capabilities: [900] L1 PM Substates > Kernel driver in use: ahci > Kernel modules: ahci > > root@hawk:~# > > That suggests a test to try when I get a chance: power down the DVD > drive, move the boot SSD to that card and the one HD currently on that > card to the motherboard. It may be several days before I get to it, > though. Well, I may have a diagnosis. In any case, I have other problems which will delay further work on this. I made the above changes, except I left the DVD drive powered and on the above SATA card. On booting, I added "fsck.mode=force" to the linux line. fack failed the root partition. That is on the SSD, now on the SATA card. manually fscking that several times produced two to four errors of the form "directory has no checksum" and "directory corrupted". On each pass the errors showed up in different inode numbers. Also, for the halibut, I fscked the home partition, which should have been completely untouched by the boot process. Similar errors obtained. I then powered down, removed power from the DVD drive, and moved the SSD to the other SATA port on the card. This time both home and root had similar issues. I then shut the system down, and hooked the SSD up to another computer via a USB-SATA adapter (Bus 001 Device 008: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge). I may have cooked the SSD in the process. I couldn't read the device on the other computer. Also, the power connector was warm when I took it off the SSD. I then set the computer under discussion back up as it had been originally. It refused even to power on. I unhooked the SSD from data and power. The computer now boots. I have booted finnix (a rescue Linux), and will fsck the hard drive while I contemplate my next move. But I suspect a replacement SSD and SATA card are in order. It will take me a few days to get replacements, during which time I can run memory tests. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/

