OK, yes, i see what you mean, but something still does not make sense here. How can it suddenly [just the other day] stop booting normally (ie, it freezes at that weird broken 2nd splash, which did not used to appear at all], but yet still be perfectly bootable via the grub recovery fsck option? Whilst i still would not understand what went wrong, but if it failed to boot both ways, that would sort of "make sense" [eg, maybe then a broken SSD]... but failing one way, & ok the other way... i can't understand this contradiction in its new behaviour.
Is there nothing else i should do? (i am writing this to you using my same Tower, in Maui... booted via that grub recovery option i keep mentioning, thus proving that the SSD cannot be "dead"].
Oh, i should correct my earlier typo error. When i said "hdd activity light" i should have said "ssd activity light"... & even that still might be wrong... it's the led on the Tower's Reset button, & i don't know actually if the light refers to the SSD or to the CPU. Sorry.
Is there nothing else i should do? (i am writing this to you using my same Tower, in Maui... booted via that grub recovery option i keep mentioning, thus proving that the SSD cannot be "dead"].
Oh, i should correct my earlier typo error. When i said "hdd activity light" i should have said "ssd activity light"... & even that still might be wrong... it's the led on the Tower's Reset button, & i don't know actually if the light refers to the SSD or to the CPU. Sorry.