3 ms·

10 years ago would have been 5.04 to 5.10. You did very well to only have that one issue to sort out! Thinks are so much better one decade later.

dijit 11y ago
Ehh, not quite. I was working on a dev server (which was pretty identical to the prod servers), vmhost/kvm/ubuntu 10.04 LTS. One day I'm staging my updates, to make sure they work when I go to prod.. I do my apt-get and reboot into the new kernel.. but- nothing can be mounted. No developers can work either, they depend on that machine.. I'm looking at it and I can mount the drives from busybox after the kernel panics.. No idea what's going on. I'm asking around in #ubuntu on freenode, since googling is getting me nowhere. 'Just reinstall it' they say. 'Sometimes it's better not to know why these things happen' :| I found the issue, some person was smart enough to think lvm2 was called 'lvm' and then initramfs all my previous kernels during the upgrade procedure- so I couldn't boot into old kernels either. Lost a day of dev time (although it was only 3 developers and me)
- ownagefool 11y ago
  Given that we're talking about 10.04 LTS, I imagine this is from a little while ago and you don't have your devs rely in a single server nowdays?
  - dijit 11y ago
    Was a very small company, they do everything with VPS's now. No more physical hardware to maintain.
dijit 11y ago
Another story about ubuntu; and this time I'm the idiot; When you're a sysadmin who's only dealt with one type of linux for a long time you forget what the different distro's do.. there really isn't that much, naming conventions/subtle commands etc; But, apt's packages have the nature of 'always run the latest service if upgraded', a notion that does not exist in centos/rhel/fedora/bsd etc; So, apt-get upgrade on our production database server means the server goes away for a while; not 'the packages are available to be used when you restart the service at midnight'* :p oops.

dijit 11y ago

Ehh, not quite. I was working on a dev server (which was pretty identical to the prod servers), vmhost/kvm/ubuntu 10.04 LTS. One day I'm staging my updates, to make sure they work when I go to prod.. I do my apt-get and reboot into the new kernel.. but- nothing can be mounted. No developers can work either, they depend on that machine.. I'm looking at it and I can mount the drives from busybox after the kernel panics.. No idea what's going on. I'm asking around in #ubuntu on freenode, since googling is getting me nowhere. 'Just reinstall it' they say. 'Sometimes it's better not to know why these things happen' :| I found the issue, some person was smart enough to think lvm2 was called 'lvm' and then initramfs all my previous kernels during the upgrade procedure- so I couldn't boot into old kernels either. Lost a day of dev time (although it was only 3 developers and me)

ownagefool 11y ago
Given that we're talking about 10.04 LTS, I imagine this is from a little while ago and you don't have your devs rely in a single server nowdays?
- dijit 11y ago
  Was a very small company, they do everything with VPS's now. No more physical hardware to maintain.

dijit 11y ago

Another story about ubuntu; and this time I'm the idiot; When you're a sysadmin who's only dealt with one type of linux for a long time you forget what the different distro's do.. there really isn't that much, naming conventions/subtle commands etc; But, apt's packages have the nature of 'always run the latest service if upgraded', a notion that does not exist in centos/rhel/fedora/bsd etc; So, apt-get upgrade on our production database server means the server goes away for a while; not 'the packages are available to be used when you restart the service at midnight'* :p oops.