On 11/13/17 14:24, Gregory Edigarov wrote: ... >> scsibus1 at ahci0: 32 targets >> -sd0 at scsibus1 targ 2 lun 0: <ATA, Samsung SSD 850, EXM0> SCSI3 0/direct >> fixed naa.50025388400562d4 >> +sd0 at scsibus1 targ 0 lun 0: <ATA, Samsung SSD 850, EXM0> SCSI3 0/direct >> fixed naa.50025388400563fe >> sd0: 976762MB, 512 bytes/sector, 2000409264 sectors, thin >> -sd1 at scsibus1 targ 3 lun 0: <ATA, Samsung SSD 850, EXM0> SCSI3 0/direct >> fixed naa.5002538c70007b02 >> -sd1: 1953514MB, 512 bytes/sector, 4000797360 sectors, thin >> +cd0 at scsibus1 targ 1 lun 0: <PLDS, DVD+-RW DS-8A8SH, KD51> ATAPI 5/cdrom >> removable >> ichiic0 at pci0 dev 31 function 3 "Intel 6 Series SMBus" rev 0x04: apic 0 >> int 19 >> iic0 at ichiic0
> My suspicion goes to SSDs. one of them have somehow become bad. I'm not able to say "no" to that. Been kinda leaning that direction, myself. These have been troublesome little beasts. Got several of the Samsung 850 series in this project, and never had so many problems with storage since I tried some off-brand (JTI?) disks around 20 years ago. Yes, I know, lots of people think these are the best around (Samsung, not JTI). *shrug* However, I did do a dd read over the first few GB (entire 'a' partition, partition table, mbr, etc.) of the disk to see if there were any read errors -- none. Whatever that's worth. If all else fails, I'll be moving the function to spare hw and totally rebuild this machine and see if it fixes it. Nick.
