From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bryan Ferris Subject: bug#33999: CP437: Invalid Argument on init Date: Wed, 9 Jan 2019 13:18:49 -0800 Message-ID: References: <20190109200804.5619d668@scratchpost.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f28ac5057f0d02bb" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:39764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ghLGe-0002VK-6L for bug-guix@gnu.org; Wed, 09 Jan 2019 16:20:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ghLGc-0005rq-KW for bug-guix@gnu.org; Wed, 09 Jan 2019 16:20:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:53353) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ghLGc-0005rm-H4 for bug-guix@gnu.org; Wed, 09 Jan 2019 16:20:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ghLGc-0003nU-CT for bug-guix@gnu.org; Wed, 09 Jan 2019 16:20:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190109200804.5619d668@scratchpost.org> 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 --000000000000f28ac5057f0d02bb Content-Type: text/plain; charset="UTF-8" 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. > ) --000000000000f28ac5057f0d02bb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 s= end 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 rec= order 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.
<= br>


--000000000000f28ac5057f0d02bb--