[00:04] <tomreyn> the qwebirc person in #ubuntu has installed using the 18.04.1 server live installer, and ended up with fstab with the root file system saying pass_no = 0
[00:04] <tomreyn> fs_passno
[00:04] <tomreyn> another bug?
[00:06] <tomreyn> other file systems were also 0. fstab(5) http://manpages.ubuntu.com/manpages/bionic/en/man5/fstab.5.html states "The root filesystem should be specified with a fs_passno of 1. Other filesystems should have a fs_passno of 2."
[00:07] <tomreyn> their actual fstab: http://paste.ubuntu.com/p/ScBmr66SQH/
=== trippeh is now known as trippeh_
[01:38] <tomreyn> how do i file a bug against subiquity?
[01:39] <tomreyn> i got the issue above confirmed
[01:42] <tomreyn> got it
[02:05] <cryptodan> Well I got CentOS 5 installed on my server a PE4600 and the raid firmware will not flash
[02:24] <tomreyn> so we got bug 1785354
[02:24] <ubottu> bug 1785354 in subiquity "/etc/fstab: fs_passno is 0 for all file systems" [Undecided,New] https://launchpad.net/bugs/1785354
[02:25] <tomreyn> and (mnaybe more a feature request?) bug 1785356
[02:25] <ubottu> bug 1785356 in subiquity "Please generate version 4 block device UUIDs, not version 1" [Undecided,New] https://launchpad.net/bugs/1785356
[03:01] <cryptodan> nacc: whislock that AACRAID Issue that I ham plagued with goes all the way back to CentOS 5 on Kernel 2.6 supposedly validated by Dell to work back then
[03:21] <cryptodan> nacc: whaley this is what im getting now.  https://www.dell.com/community/PowerEdge-HDD-SCSI-RAID/Update-Firmware-PE4600/m-p/6129682/highlight/true#M49162 I have nothing on that channel
=== jelly-home is now known as jelly
=== lotuspsychje_ is now known as lotuspsychje
=== hammond is now known as Guest21290
=== JanC_ is now known as JanC
=== devil is now known as Guest3922
=== JanC_ is now known as JanC
[19:09] <cryptodan> why does ubuntu server come with the grub line of CONSOLE MODE commented out
[19:13] <cryptodan> Wished Ubuntu Server came defaulted with Console Mode enabled via grub so I can see what is going on with my server install
[19:31] <cryptodan> so any way I can get to see the console output on my server?  I used to be able to boot it up and see the IP in my router, and ssh to it then remove the comment and update grub.  I cant do that as it appears this fresh install is stuck on mounting home and the monitor is completely dark
[19:32] <cryptodan> 400 people yet no one knows
[19:35] <lotuspsychje> !aptience | cryptodan
[19:35] <lotuspsychje> !patience
[19:35] <ubottu> Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or https://ubuntuforums.org or https://askubuntu.com/
[19:36] <lotuspsychje> cryptodan: we have volunteers all ovber the world, on different timezones, they cant all be online at your question time, i hope you understand?
[19:40] <lotuspsychje> cryptodan: also try to be as specific as you can, start with ubuntu server version, kernel, where are you stuck at wich step? the more details, the more chance of solving
[19:40] <cryptodan> its all ubuntu server servers
[19:40] <cryptodan> regardless of which version I install I always have to ssh into and enable grub console to print out the booting messages of the server
[19:43] <cryptodan> thank you Ubuntu for not supporting older hardware and not making sure the drivers work like AACRAID
[20:02] <tomreyn> i'm not sure it was engineered in this way just to make *you* sad about this. maybe there were some other factors which influenced the decision making, just potentially.
[20:04] <cryptodan> I would imagine that every system admin would love to see their console boot messages as to help troubleshoot any post installation problems
[20:04] <cryptodan> you know such as kernel panics and what not
[20:04] <cryptodan> device loading problems
[20:15] <tomreyn> you will still get to see such on a serial console. you can also customize the installation, or deploy changes post intallation. many options.
[20:16] <cryptodan> should be simple for just one server sitting in a basement in a non-data center environment