=== [1]vncm is now known as vncm === StFS_ is now known as StFS [09:04] j4s0nmchr1st0s (N,BFTL), i don't think that makes any sense === ara is now known as Guest56698 === [1]vncm is now known as vncm [13:45] is it normal that booting to a new kernel renders a drive in a md array broken? the server had uptime of 197 days and after booting (trusty) to -39 caused issues [13:49] tjaalton, no [13:50] I'll try an earlier one.. [13:50] it's a remote system so kinda awkward to test things [13:50] tjaalton, question is how broken, broken means [13:52] smb: trying to access /dev/sda fails [13:52] so no wonder it got dropped from the arrays [13:53] it's a hp microserver that has worked ~4y without issues [13:53] tjaalton, ok. but also the chance of a change in the kernel only affecting one drive sounds slim. I would rather believe in cosmic rays [13:54] Some unfortunate coincidence with resetting the disk on reboot? [13:56] yeah could be [13:58] Sometimes weird shit happens. I had a SSD turning into a brick after resume... not any kind of pre-warning [14:03] yeah one of mine broke while I was at the (last) uds === caribou_ is now known as caribou === henrix_ is now known as henrix [17:56] zyga, trusty kernel and lts-hwe-trusty are being respun === vmesons is now known as vmeson === vmeson is now known as vmesons === vmesons is now known as vmeson