Post BA0eaW31hgewoL5PHM by theeclecticdyslexic@mstdn.social
(DIR) More posts by theeclecticdyslexic@mstdn.social
(DIR) Post #BA0cOtFLQT23NRB0W8 by wolf480pl@mstdn.io
0 likes, 0 repeats
@theeclecticdyslexic @unfa I think "unknown-block(259,1)" refers to a block device, not a block on the device.259 is seems to be the major device number for nvme devices, and 1 would be the second one of such devices - so likely nvme0n1 is 259,0 and nvme0n1p1 is 259.1So it seems either the SSD did not get detected, or it didn't have a first partition
(DIR) Post #BA0d9LdiC3lkl0j8LI by theeclecticdyslexic@mstdn.social
0 likes, 0 repeats
@wolf480pl @unfa ah yes that seems more appropriate now that I reread it!Not having an expected partition is pretty worrying...Lots of things could cause that, but the fast that comes to find feels unlikely "did you swap out your primary drive?" Is not high on the list of possibilities here...
(DIR) Post #BA0dL3A2ipPgvEQgtM by wolf480pl@mstdn.io
0 likes, 0 repeats
@theeclecticdyslexic @unfa more like "do you have dust in your M.2 socket" or "did your drive's firmware hang and needs a hard power-cycle"
(DIR) Post #BA0eaW31hgewoL5PHM by theeclecticdyslexic@mstdn.social
0 likes, 0 repeats
@wolf480pl @unfa firmware hang would suck, because that sounds like a thing that could just keep happening without clear cause in a way that feels nondeterministic
(DIR) Post #BA0ehTEcYp1i76pFgm by wolf480pl@mstdn.io
0 likes, 0 repeats
@theeclecticdyslexic @unfa it happens to me every 5th suspend-resume cycle, but usually a normal reboot fixes it...and also in that case it wouldn't get to the bootloader and the kernel, and in unfa's case it did, and firmware hanging *during* boot is not something I've ever seen
(DIR) Post #BA4LF3wLJuIdSNA3ZQ by unfa@mastodon.social
0 likes, 0 repeats
@wolf480pl @theeclecticdyslexic I think it was the latter thankfully. Went away after a hard reboot.