From: Catonano <catonano@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: boot fails after system reconfigure
Date: Tue, 23 May 2017 20:27:00 +0200 [thread overview]
Message-ID: <CAJ98PDyKZMEDyJaUsuPjRT+an-tjoKkMkMd_DyHTqmEKYOe3zQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ98PDw5U6WUWGOjW7F4-PzS2kru7BSL1v8yZh6gZqYOm4vTxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
it's compiling the kernel
This will take a while
2017-05-23 20:26 GMT+02:00 Catonano <catonano@gmail.com>:
> 2017-05-23 20:09 GMT+02:00 Leo Famulari <leo@famulari.name>:
>
>> On Tue, May 23, 2017 at 07:56:07PM +0200, Catonano wrote:
>> > > > (file-systems (cons (file-system
>> > > > (device "my-root")
>> > > > (title 'label)
>> > > > (mount-point "/")
>> > > > (type "ext4")
>> > > >
>> > > > )
>> > > > %base-file-systems))
>> >
>> > This is e2label
>> >
>> > catonano@xps ~$ sudo e2label /dev/sda
>> > sda sda1 sda2 sda3 sda5 sda6
>> > catonano@xps ~$ sudo e2label /dev/sda1
>> > boot
>> > catonano@xps ~$ sudo e2label /dev/sda2
>> > e2label: Valore magic non corretto nel super-blocco nell'aprire
>> /dev/sda2
>> > /dev/sda2 contiene un file system swap
>> > catonano@xps ~$ sudo e2label /dev/sda3
>> > e2label: Attempt to read block from filesystem resulted in short read
>> > nell'aprire /dev/sda3
>> > Impossibile trovare un valido super-blocco per il file system.
>> > catonano@xps ~$ sudo e2label /dev/sda5
>> > root
>> > catonano@xps ~$ sudo e2label /dev/sda6
>> > home
>>
>> The issue is that there is no filesystem with the label 'my-root'. Did
>> this configuration really work previously with the same partition and
>> filesystem layout?
>>
>
> Oh gosh, no
>
> The conf file I pasted is not the one I used for the working generations
>
> The conf file I pasted is the one I used for playing with the qemu virtual
> machines !
>
> Now I'm reconiguring again with the hopeully right file
> I'll let you know
>
> Sorry, I have been panicking !
>
[-- Attachment #2: Type: text/html, Size: 2889 bytes --]
next prev parent reply other threads:[~2017-05-23 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:01 boot fails after system reconfigure Catonano
2017-05-23 17:29 ` Leo Famulari
2017-05-23 17:35 ` Catonano
2017-05-23 17:49 ` Catonano
2017-05-23 17:49 ` Leo Famulari
2017-05-23 17:56 ` Catonano
2017-05-23 18:09 ` Leo Famulari
2017-05-23 18:26 ` Catonano
2017-05-23 18:27 ` Catonano [this message]
2017-05-23 19:46 ` Catonano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ98PDyKZMEDyJaUsuPjRT+an-tjoKkMkMd_DyHTqmEKYOe3zQ@mail.gmail.com \
--to=catonano@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).