On Tuesday 21 August 2018 10:56:56 Felix Miata wrote:
Gene Heskett composed on 2018-08-21 09:08 (UTC-0400):
Now that's a gotcha I did not know. How did it come that this was thought of beeing a good idea?
Yep. Exactly my thought when i spent 3-hours with a server refusing to boot after migration to a new hdd (i used a stretch flash to copy). Who the fuck toughs it was a good idea?!! Why not call it ext5 or ext4a or whatever?!!
+100
Now the question of the day is how the hell do we fix it?
As I implied 24 hours ago in this thread, it doesn't need fixing. Jessie came in between Wheezy and Stretch, a long time (two years?). There are multiple workarounds for those who skipped over Jessie:
1-Format the installation target using Wheezy or Jessie or old Knoppix or old anything in advance of starting the installer. Formatting is an /optional/ part of the installation process (as is partitioning).
I did try to do that, it showed me the partitions I had setup in gparted, but would not skip the selection and format steps.
2-As Dan wrote, use EXT3 instead of EXT4 (EXT3 can be converted to EXT4 later if desired. AFAIK, the incompatible options will not automatically be added on conversion.)
3-Format with the Stretch installer, but specify to omit the incompatible EXT4 options. I don't which it/they are, but my guess is the only one that is needed is "-O '^64bit'". All my Wheezys were eliminated around the time its support termination was announced, so no practical way here to test.
4-Use XFS instead of EXT4.
Thats been contemplated, but not being able to skip the partition and formatting stage, I don't know how.
If there is a way, plz advise.
But this morning, the first install wouldn't boot at, as if there was no grub on the drive, but I watched it install it. All I could see was no drive activity, and a blinking underline cursor in row/column 1. Several resets and a choose /sdb to boot from each time. So I started another install, non-graphical, which sorta worked below.
2nd try today I only told it a separate /home, and that seemed to work, but despite not choosing that in the initial menu, the speech-dispatcher drove me crazy. No volume control installed, and the keyboard echo to the terminal became so slow it screwed up my typing when I had become root and issued a killall to shut it up, as if it was waiting for the speech-dispatcher to finish. A gracefull stop as an option to the script in /etc/init.d was ignored, as root or as me.
Hell of a way to run a train.
I added the wiki's entries in sources.list.d/trinity.list, but then the keyserver refused my connection about 15 times so now I'm back on wheezy since I can't replace the xfce default.
So whats with keyserver.quickbuild.io this morning, I can ping it from stretch just fine. And the missus wants the papers before the storm arrives, so I'll do that next. She's a good girl but a Crossword addict.
5-Use a newer and/or custom kernel in Wheezy. http://ftp5.gwdg.de/pub/linux/debian/debian/pool/main/l/