* boot fails after system reconfigure @ 2017-05-23 17:01 Catonano 2017-05-23 17:29 ` Leo Famulari 0 siblings, 1 reply; 10+ messages in thread From: Catonano @ 2017-05-23 17:01 UTC (permalink / raw) To: help-guix [-- Attachment #1: Type: text/plain, Size: 78 bytes --] I made a footage https://www.youtube.com/watch?v=UrfiR6zenC4&feature=youtu.be [-- Attachment #2: Type: text/html, Size: 197 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 17:01 boot fails after system reconfigure Catonano @ 2017-05-23 17:29 ` Leo Famulari 2017-05-23 17:35 ` Catonano 0 siblings, 1 reply; 10+ messages in thread From: Leo Famulari @ 2017-05-23 17:29 UTC (permalink / raw) To: Catonano; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 507 bytes --] On Tue, May 23, 2017 at 07:01:43PM +0200, Catonano wrote: > I made a footage > https://www.youtube.com/watch?v=UrfiR6zenC4&feature=youtu.be It says it can't find the filesystem labelled 'my-root'. These labels can be set and queried while creating filesystems, or afterwards with `fdisk`, `e2label` (from e2fsprogs) or `btrfs filesystem label` (from btrfs-progs). So, can you share the file-systems section of your system configuration? And, how is your storage partitioned and the filesystems laid out? [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 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 0 siblings, 2 replies; 10+ messages in thread From: Catonano @ 2017-05-23 17:35 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 2567 bytes --] 2017-05-23 19:29 GMT+02:00 Leo Famulari <leo@famulari.name>: > On Tue, May 23, 2017 at 07:01:43PM +0200, Catonano wrote: > > I made a footage > > https://www.youtube.com/watch?v=UrfiR6zenC4&feature=youtu.be > > It says it can't find the filesystem labelled 'my-root'. > > These labels can be set and queried while creating filesystems, or > afterwards with `fdisk`, `e2label` (from e2fsprogs) or `btrfs filesystem > label` > (from btrfs-progs). > > So, can you share the file-systems section of your system configuration? > And, how is your storage partitioned and the filesystems laid out? > The conf I used follows It's the same conf I used in the previous system generations. One of those generations is running right now ;; This is an operating system configuration template ;; for a "desktop" setup with GNOME and Xfce where the ;; root partition is encrypted with LUKS. (use-modules (gnu) (gnu system nss)) (use-service-modules desktop) (use-package-modules certs gnome) (use-service-modules databases) (operating-system (host-name "antelope") (timezone "Europe/Paris") (locale "it_IT.utf8") ;; Assuming /dev/sdX is the target hard disk, and "my-root" ;; is the label of the target root file system. (bootloader (grub-configuration (device "/dev/sda"))) (file-systems (cons (file-system (device "my-root") (title 'label) (mount-point "/") (type "ext4") ) %base-file-systems)) (users (cons (user-account (name "catonano") (comment "Alice's brother") (group "users") (supplementary-groups '("wheel" "netdev" "audio" "video")) (home-directory "/home/catonano")) %base-user-accounts)) ;; This is where we specify system-wide packages. (packages (cons* nss-certs ;for HTTPS access gvfs ;for user mounts %base-packages)) ;; Add GNOME and/or Xfce---we can choose at the log-in ;; screen with F1. Use the "desktop" services, which ;; include the X11 log-in service, networking with Wicd, ;; and more. (services (cons* (postgresql-service #:locale "it_IT.UTF-8") (gnome-desktop-service) (xfce-desktop-service) %desktop-services)) ;; Allow resolution of '.local' host names with mDNS. (name-service-switch %mdns-host-lookup-nss)) [-- Attachment #2: Type: text/html, Size: 3977 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 17:35 ` Catonano @ 2017-05-23 17:49 ` Catonano 2017-05-23 17:49 ` Leo Famulari 1 sibling, 0 replies; 10+ messages in thread From: Catonano @ 2017-05-23 17:49 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 869 bytes --] 2017-05-23 19:35 GMT+02:00 Catonano <catonano@gmail.com>: > > > 2017-05-23 19:29 GMT+02:00 Leo Famulari <leo@famulari.name>: > >> On Tue, May 23, 2017 at 07:01:43PM +0200, Catonano wrote: >> > I made a footage >> > https://www.youtube.com/watch?v=UrfiR6zenC4&feature=youtu.be >> >> It says it can't find the filesystem labelled 'my-root'. >> >> These labels can be set and queried while creating filesystems, or >> afterwards with `fdisk`, `e2label` (from e2fsprogs) or `btrfs filesystem >> label` >> (from btrfs-progs). >> >> So, can you share the file-systems section of your system configuration? >> And, how is your storage partitioned and the filesystems laid out? >> > > > The conf I used follows > > It's the same conf I used in the previous system generations. One of those > generations is running right now > Wait, I migt be wrong Give me a minute, please [-- Attachment #2: Type: text/html, Size: 1770 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 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 1 sibling, 1 reply; 10+ messages in thread From: Leo Famulari @ 2017-05-23 17:49 UTC (permalink / raw) To: Catonano; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 617 bytes --] On Tue, May 23, 2017 at 07:35:02PM +0200, Catonano wrote: > The conf I used follows > > It's the same conf I used in the previous system generations. One of those > generations is running right now [...] > (file-systems (cons (file-system > (device "my-root") > (title 'label) > (mount-point "/") > (type "ext4") > > ) > %base-file-systems)) What is the result of `fdisk -l` and `e2label /dev/foo`, where foo is the partition that should contain '/'? [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 17:49 ` Leo Famulari @ 2017-05-23 17:56 ` Catonano 2017-05-23 18:09 ` Leo Famulari 0 siblings, 1 reply; 10+ messages in thread From: Catonano @ 2017-05-23 17:56 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 5182 bytes --] 2017-05-23 19:49 GMT+02:00 Leo Famulari <leo@famulari.name>: > On Tue, May 23, 2017 at 07:35:02PM +0200, Catonano wrote: > > The conf I used follows > > > > It's the same conf I used in the previous system generations. One of > those > > generations is running right now > > [...] > > > (file-systems (cons (file-system > > (device "my-root") > > (title 'label) > > (mount-point "/") > > (type "ext4") > > > > ) > > %base-file-systems)) > > What is the result of `fdisk -l` and `e2label /dev/foo`, where foo is > the partition that should contain '/'? > 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 and this is fdisk -l Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sda: 238,5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb25f3f6c Dispositivo Avvio Start Fine Settori Size Id Tipo /dev/sda1 * 2048 587775 585728 286M 83 Linux /dev/sda2 587776 17364991 16777216 8G 82 Linux swap / Solaris /dev/sda3 17364992 500118191 482753200 230,2G 5 Esteso /dev/sda5 17367040 227082239 209715200 100G 83 Linux /dev/sda6 227084288 500118191 273033904 130,2G 83 Linux [-- Attachment #2: Type: text/html, Size: 6279 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 17:56 ` Catonano @ 2017-05-23 18:09 ` Leo Famulari 2017-05-23 18:26 ` Catonano 0 siblings, 1 reply; 10+ messages in thread From: Leo Famulari @ 2017-05-23 18:09 UTC (permalink / raw) To: Catonano; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 1167 bytes --] 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? [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 18:09 ` Leo Famulari @ 2017-05-23 18:26 ` Catonano 2017-05-23 18:27 ` Catonano 0 siblings, 1 reply; 10+ messages in thread From: Catonano @ 2017-05-23 18:26 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 1540 bytes --] 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: 2450 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 18:26 ` Catonano @ 2017-05-23 18:27 ` Catonano 2017-05-23 19:46 ` Catonano 0 siblings, 1 reply; 10+ messages in thread From: Catonano @ 2017-05-23 18:27 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- 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 --] ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: boot fails after system reconfigure 2017-05-23 18:27 ` Catonano @ 2017-05-23 19:46 ` Catonano 0 siblings, 0 replies; 10+ messages in thread From: Catonano @ 2017-05-23 19:46 UTC (permalink / raw) To: Leo Famulari; +Cc: help-guix [-- Attachment #1: Type: text/plain, Size: 58 bytes --] it works like a charm Sorry. As ii said, i lost my cool [-- Attachment #2: Type: text/html, Size: 107 bytes --] ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2017-05-23 19:46 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2017-05-23 19:46 ` Catonano
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).