| === [1]vncm is now known as vncm | ||
| === StFS_ is now known as StFS | ||
| apw | j4s0nmchr1st0s (N,BFTL), i don't think that makes any sense | 09:04 |
|---|---|---|
| === ara is now known as Guest56698 | ||
| === [1]vncm is now known as vncm | ||
| tjaalton | 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:45 |
| smb | tjaalton, no | 13:49 |
| tjaalton | I'll try an earlier one.. | 13:50 |
| tjaalton | it's a remote system so kinda awkward to test things | 13:50 |
| smb | tjaalton, question is how broken, broken means | 13:50 |
| tjaalton | smb: trying to access /dev/sda fails | 13:52 |
| tjaalton | so no wonder it got dropped from the arrays | 13:52 |
| tjaalton | it's a hp microserver that has worked ~4y without issues | 13:53 |
| smb | 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:53 |
| smb | Some unfortunate coincidence with resetting the disk on reboot? | 13:54 |
| tjaalton | yeah could be | 13:56 |
| smb | Sometimes weird shit happens. I had a SSD turning into a brick after resume... not any kind of pre-warning | 13:58 |
| tjaalton | yeah one of mine broke while I was at the (last) uds | 14:03 |
| === caribou_ is now known as caribou | ||
| === henrix_ is now known as henrix | ||
| bjf | zyga, trusty kernel and lts-hwe-trusty are being respun | 17:56 |
| === vmesons is now known as vmeson | ||
| === vmeson is now known as vmesons | ||
| === vmesons is now known as vmeson | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!