From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bryan Ferris Subject: bug#33999: CP437: Invalid Argument on init Date: Thu, 10 Jan 2019 07:15:10 -0800 Message-ID: References: <20190109200804.5619d668@scratchpost.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000147b29057f1c0cb0" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50497) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghc3w-00030K-9J for bug-guix@gnu.org; Thu, 10 Jan 2019 10:16:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghc3v-00072f-6y for bug-guix@gnu.org; Thu, 10 Jan 2019 10:16:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:54808) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ghc3v-00072N-0e for bug-guix@gnu.org; Thu, 10 Jan 2019 10:16:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ghc3u-0005tC-Ht for bug-guix@gnu.org; Thu, 10 Jan 2019 10:16:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 33999@debbugs.gnu.org --000000000000147b29057f1c0cb0 Content-Type: text/plain; charset="UTF-8" I've linked to two videos here, one of the boot (the screen with the GNU logo and "100% freedom" on it) and one of the init (where Shepherd reports errors, I think it's dmesg?). Boot: https://drive.google.com/file/d/1YMbCI3BvznhMI_eYYTxMvxJC2SKlNqSJ/view?usp=sharing Init: https://drive.google.com/file/d/1CZov16Xrpy9D8DMN9eHeANjR7UHh2WpL/view?usp=sharing On Thu, Jan 10, 2019 at 6:31 AM Bryan Ferris wrote: > I've attached two videos here, one of the boot (the screen with the GNU > logo and "100% freedom" on it) and one of the init (where Shepherd reports > errors, I think it's dmesg?). > > On Wed, Jan 9, 2019, 13:18 Bryan Ferris >> I assume that it is related because the error is printed once for each >> failed service but I have no better reason than that. I can send a video of >> my boot tonight... It might be a little blurry though, all I have is my >> phone camera. If there's a way for me to start a screen recorder during >> init or capture the logs that it prints as a text file I'd be happy to do >> that, I just don't know of a way to. >> >> >> >> On Jan 9, 2019 11:08, "Danny Milosavljevic" >> wrote: >> >> Hi, >> >> apparently the message is printed by fsck.fat and is harmless (although >> we should >> still fix it). Are you sure that the services fail because of it? >> >> > (file-systems (cons* >> > (file-system >> > (device (file-system-label "ESP")) >> > (mount-point "/boot/efi") >> > (type "fat") >> >> Try adding (check? #f) here for testing purposes. >> >> > ) >> >> >> --000000000000147b29057f1c0cb0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've linked to = two videos here, one of the boot (the screen with the GNU=20 logo and "100% freedom" on it) and one of the init (where Shepher= d=20 reports errors, I think it's dmesg?).

Boot: https://drive.google.com/file/d/1YMbCI3BvznhMI_eYYTxMvx= JC2SKlNqSJ/view?usp=3Dsharing

On Thu, Jan 10, 2019 at 6:31 AM Bryan Ferris <saffsnail@gmail.com> wrote:
I've a= ttached two videos here, one of the boot (the screen with the GNU logo and = "100% freedom" on it) and one of the init (where Shepherd reports= errors, I think it's dmesg?).

On Wed, Jan 9, 2019, 13:18 Bryan Ferris <saffsnail@gmail.com wrote:
I a= ssume that it is related because the error is printed once for each failed = service but I have no better reason than that. I can send a video of my boo= t tonight... It might be a little blurry though, all I have is my phone cam= era. If there's a way for me to start a screen recorder during init or = capture the logs that it prints as a text file I'd be happy to do that,= I just don't know of a way to.



On Jan 9, 2019 11:08, "Danny Milosavljevic" <dannym@s= cratchpost.org> wrote:
Hi,=

apparently the message is printed by fsck.fat and is harmless (although we = should
still fix it).=C2=A0 Are you sure that the services fail because of it?

>=C2=A0 =C2=A0(file-systems (cons*
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(f= ile-system
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0(device (file-system-label "ESP"))
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0(mount-point "/boot/efi")
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0(type "fat")

Try adding (check? #f) here for testing purposes.

>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0)<= br>

--000000000000147b29057f1c0cb0--