Failed installation: How to define root file system?

luiznetto · 2020-02-21 20:51:36

Hi, hello everybody. First time here, but definitely not new to Linux.
I am trying to install BunsenLabs Linux to the first partition on the hard drive of my laptop. The aforementioned hard drive is 80 GB, partinioned as follows:

sda1 ext4 16.8 GB B presently empty
sda2 swap 2 GB
sda3 ext4 63.2 GB Debian

Somewhere during the installation, before it is supposed to start writing the data on partition 1, I get the following message:

!! Partition disks
No root file system is defined. Please correct this from the partition menu.

But I have no idea how to do this. I tried everything. I installed Linux many times in the past, I have, as I said, Debian installed on the 3rd partition of the same disk, and I never had this kind of difficulty before.

Any help is deeply appreciated. Thanks in advance.

rbh · 2020-02-21 21:05:51

Are you installing from USB-disk? You have checed the downloaded iso? You have used cp or dd to write the usb?
Du you use Helium or Lithium dev (Lithium dv is stable...)
Du you get it before or after partiononing?

Can you test installation again, choose advanced install? If you get the error again, note on wich stage.

Last edited by rbh (2020-02-21 21:06:29)

luiznetto · 2020-02-21 21:22:53

I am installing from a CD-RW; I downloaded the iso image and burned it onto the disk. It's Helium. I don't think I partitioned the disk, I just chose the option "erase all data on the partition, write it all over with zeroes" which looked reasonable to me (unfortunately, I think it erased the label on the partition as well, it wasn't supposed to do that). I'll try again, and report back to you. Thanks.

rbh · 2020-02-21 21:41:19

luiznetto wrote:

I don't think I partitioned the disk, I just chose the option "erase all data on the partition, write it all over with zeroes"

You have better controll with choosing "Expert installer"... If you are going to sell the pc, it is nesseceary to overwrite old information. Not else...

Last edited by rbh (2020-02-21 21:41:42)

damo · 2020-02-21 22:43:47

luiznetto wrote:

...
Somewhere during the installation, before it is supposed to start writing the data on partition 1, I get the following message:
!! Partition disks
No root file system is defined. Please correct this from the partition menu.
But I have no idea how to do this. ....

Did you follow HowTo: Install BunsenLabs with the Graphical Installer? The section on Partitioning describes setting the mountpoint for root.

luiznetto · 2020-02-21 23:21:35

I finally managed to install the system using "Expert Mode", but many of the options that were offered me I didn't understand, so I'm not sure I did the right thing. But now I'm having trouble updating the system. I try

sudo apt-get update

and I get some error messages about signatures, etc. (sorry I failed to copy from terminal). I'd like to uninstall some packages and install new ones. I used an older version of Helium, maybe that's the source of my difficulties.

Last edited by luiznetto (2020-02-26 03:13:21)

rbh · 2020-02-22 09:15:45

luiznetto wrote:

I used and older version of Helium, maybe that's the source of my difficulties.

Yes. It is allvays best to use latest iso. The apt-key has changed since the iso you used was published. To bee able to upgrade your system you have to import the new apt-key:

$ sudo gpg --import <(wget -qO- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc)

You can also redo the installation. It is a good excercise. If you have another computer accessible, you can examine the step you was unsure about, so you can make a choise not based on guessing. At least take a picture wit your mobile and look it up afterwards.

The debian installation is described here https://debian-handbook.info/browse/sta … steps.html The Debianbook is a little outdated. There is some small differences with the Bunsenlab Installation.

Damo gave you above the link to the BL-graphical installallation.

Last edited by rbh (2020-02-22 09:17:53)

rbh · 2020-02-22 09:26:25

luiznetto wrote:

hard drive is 80 GB, partinioned as follows:
sda1 ext4 16.8 GB B presently empty
sda2 swap 2 GB
sda3 ext4 63.2 GB Debian
I have, as I said, Debian installed on the 3rd partition of the same disk,

You intend to use sda1 for Bunsenlabs? 17 GB is enough for trying Bunsenlabs out. But if you enjoy it and install many packages, populate your /home with much user data, you will need more space.

Last edited by rbh (2020-02-22 09:27:00)

rbh · 2020-02-22 11:51:11

rbh wrote:

At least take a picture wit your mobile and look it up afterwards.

I forgot. The graphical installer has a good tool. In the left lover corner of the screen, there is a button to take a screenshot.
The screenshots is saved in /var/log/installer/, with the installer logs.

ohnonot · 2020-02-24 07:40:06

The installer's partitioning tool isn't the most intuitive.
I guess the most important thing is that the partition you want to install on reads "mounted on: /" or some such.
I’m sure this guide also mentions it.

luiznetto · 2020-03-04 22:58:53

rbh wrote:

luiznetto wrote:
I used and older version of Helium, maybe that's the source of my difficulties.
Yes. It is allvays best to use latest iso. The apt-key has changed since the iso you used was published. To bee able to upgrade your system you have to import the new apt-key:
$ sudo gpg --import <(wget -qO- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc)

I did, and this is what I got:

luiz@bunsen:~$ sudo gpg --import <(wget -qO- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc)
gpg: directory '/root/.gnupg' created
gpg: keybox '/root/.gnupg/pubring.kbx' created
gpg: can't open '/dev/fd/63': No such file or directory
gpg: Total number processed: 0
luiz@bunsen:~$ sudo apt-get update
Ign:1 https://deb.debian.org/debian stretch InRelease
Hit:2 https://deb.debian.org/debian-security stretch/updates InRelease
Hit:3 https://deb.debian.org/debian stretch-updates InRelease
Hit:4 https://deb.debian.org/debian stretch-backports InRelease
Hit:5 https://deb.debian.org/debian stretch Release
Get:6 https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease [5,183 B]
Get:7 https://eu.pkg.bunsenlabs.org/debian helium InRelease [5,197 B]
Ign:6 https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease
Ign:7 https://eu.pkg.bunsenlabs.org/debian helium InRelease
Fetched 10.4 kB in 35s (289 B/s)
Reading package lists... Done
W: GPG error: https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5  (BunsenLabs Repository Signing Key) <>
W: The repository 'https://pkg.bunsenlabs.org/debian stretch-backports InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: https://eu.pkg.bunsenlabs.org/debian helium InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5  (BunsenLabs Repository Signing Key) <>
W: The repository 'https://pkg.bunsenlabs.org/debian helium InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
luiz@bunsen:~$

The reason I used an onder iso is that I wanted to burn it onto a disk, and my laptop only burns CDs, not DVDs. More recent isos are too big for me.

Last edited by luiznetto (2020-03-04 23:17:53)

luiznetto · 2020-03-04 23:14:05

rbh wrote:

You intend to use sda1 for Bunsenlabs? 17 GB is enough for trying Bunsenlabs out. But if you enjoy it and install many packages, populate your /home with much user data, you will need more space.

I mean to continue using Debian Buster as my main system, but I want to have a lighter Linux to test on sda1. I don't intend to install too many packages. So far BunsenLabs has used 19% of the space available at sda1. I mostly like what I see up to this point, but as far as I can see BunsenLabs has a few limitations. For example, my USB sound card doesn't work with BunsenLabs.

rbh · 2020-03-04 23:29:32

luiznetto wrote:

I mean to continue using Debian Buster as my main system, but I want to have a lighter Linux to test on sda1. I don't intend to install too many packages. So far BunsenLabs has used 19% of the space available at sda1. I mostly like what I see up to this point, but as far as I can see BunsenLabs has a few limitations. For example, my USB sound card doesn't work with BunsenLabs.

Bunsen Labs is not more limited than Debian! Bunsen Labs is Debian, with some additions, specific configs and helpfiles.
Can you use it on Debian, can you use it on BunsenLabs!

#1 2020-02-21 20:51:36

Failed installation: How to define root file system?

#2 2020-02-21 21:05:51

Re: Failed installation: How to define root file system?

#3 2020-02-21 21:22:53

Re: Failed installation: How to define root file system?

#4 2020-02-21 21:41:19

Re: Failed installation: How to define root file system?

#5 2020-02-21 22:43:47

Re: Failed installation: How to define root file system?

#6 2020-02-21 23:21:35

Re: Failed installation: How to define root file system?

#7 2020-02-22 09:15:45

Re: Failed installation: How to define root file system?

#8 2020-02-22 09:26:25

Re: Failed installation: How to define root file system?

#9 2020-02-22 11:51:11

Re: Failed installation: How to define root file system?

#10 2020-02-24 07:40:06

Re: Failed installation: How to define root file system?

#11 2020-03-04 22:58:53

Re: Failed installation: How to define root file system?

#12 2020-03-04 23:14:05

Re: Failed installation: How to define root file system?

#13 2020-03-04 23:29:32

Re: Failed installation: How to define root file system?

Board footer