[kwlug-disc] Disk longevity ...

Bob Jonkman bjonkman at sobac.com
Tue Feb 15 17:57:49 EST 2022


On 2022-02-13 13:07, Khalid Baheyeldin wrote:
 > Do it in two stages, with a few days in between. First to 18.04, then 
a few days after, go for 20.04.

There's something to be said for not letting the OS get too far out of 
date. I worked on a server still running Ubuntu 12.04, but couldn't run 
do-release-upgrade because the repositories for 14.04 are no longer online.

When I set up new servers I create a few extra LVs each 15 GB in size 
for "spare" and "backupOS" which I use for a clean install of a new OS, 
install the packages (with dpkg --set-selections), and then point the 
new fstab to the old LVs for /home, /srv, /opt, /var/lib/mysql or 
/var/lib/postgresql, and /usr/local, and copy the necessary config files 
from the former root LV's /etc (yes, salt or ansible would be useful here).

That gives a 100% failsafe backout if there's some incompatibility with 
old apps and new OS libraries and tools. I'm looking at you, PHP...

--Bob.


On 2022-02-13 13:07, Khalid Baheyeldin wrote:
> On Sun, Feb 13, 2022 at 12:59 PM Ron Singh <ronsingh149 at gmail.com> wrote:
> 
>> That is the exact HDD we use in a Raid50 array in our workplace server,
>> running since 2011 on an Asus ATX P6X58D-E. Zero failures since and likely
>> only rebooted twice a year as my IT guy is plenty conservative about
>> applying OS patches(MS SVR2012). Damn good drives.
>>
> 
> I guess the saying : "they don't make them like they used to" is very true
> in this case.
> 
> And yeah Khalid, I should be less nervous about doing a dist-upgrade,
>> especially on the server edition of Ubuntu:-)
>> My travel laptop is still on Lubuntu 16.04, I will do the upgrade to 18.04
>> and then onto 20.04 and see how that goes. It might be a challenge as the
>> GUI changes from LXDE to LXqT, but worth a shot since it's an easily
>> re-buildable OS profile(small amount of /home contents).
>>
> 
> Do it in two stages, with a few days in between.
> First to 18.04, then a few days after, go for 20.04.
> 
> The reason I say this is that I had to do a couple of test servers that
> way, and certain things did not work, due to changes in parameters (e.g.
> MySQL obsoleted a few things, and it would not start unless I deleted the
> obsolete ones).
> Another thing was cleanup of some package removed a crucial component (SSL
> certificate, but my memory is vague here).
> None of this happened when I did only one upgrade at a time, and let it
> 'settle' which is the normal workflow for upgrades that I follow.
> 
> 
> _______________________________________________
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> https://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org

-- 
Bob Jonkman <bjonkman at sobac.com>          Phone: +1-519-635-9413
SOBAC Microcomputer Services             http://sobac.com/sobac/
Software   ---   Office & Business Automation   ---   Consulting
GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA







More information about the kwlug-disc mailing list