Closed dduran1210 closed 2 years ago
Hello,
Which installer are you using - the old installer script or the new dialog-based installer on the Live CD? The old script is somewhat rudimentary and isn't maintained anymore and may be removed in the future, so the Live CD and its installer is recommended instead.
If it's the former, can you provide the output of the script that has been run so far?
If it's the latter, there may be a log file at /tmp/massos-installerlogXXXXXXXXXX
, where XXXXXXXXX
is the timestamp. If there is, can you send/attach it? Running cat /tmp/massos-installerlog*
should give you its output.
Please also provide with the following information:
/dev/sda
, /dev/nvme0n1
, etc.)/sys/firmware/efi
exists or not).Also note that the old installer script requires an internet connection to download the rootfs tarball unless you manually download it and pass it as an argument, so check you are connected to the internet.
hello I am using the live CD installer.
I am installing on a 2TB internal hard drive. Disk Path is /dev/sda uefi mode.
I selected the partition 97.7gb (sda14) , made the efi partition (sda15) , then it asked me about swap. I selected no at first, because i have 3.91gb installed on sda2 partition. I have Linuxmint, xubuntu, BigLinux on other partitions. (they all use the same swap partition sda2) (am testing to find the best OS for me). I really like this MassOS on the live cd and would really like to install it.
thanks see attached log "swap problem"
dave
On Fri, Feb 25, 2022 at 4:39 PM The Sonic Master @.***> wrote:
Hello,
Which installer are you using - the old installer script or the new dialog-based installer on the Live CD? The old script isn't maintained anymore and may be removed in the future, so the Live CD and its installer is recommended instead.
If it's the former, can you provide the output of the script that has been run so far?
If it's the latter, there may be a log file at /tmp/massos-installerlogXXXXXXXXXX, where XXXXXXXXX is the timestamp. If there is, can you send/attach it? Running cat /tmp/massos-installerlog* should give you its output.
Please also provide with the following information:
- Drive type (Hard Drive/SSD/Flash Drive), whether it's an internal or external disk, and the disk's path (/dev/sda, /dev/nvme0n1, etc.)
- Whether you are booting and installing in Legacy BIOS or UEFI mode (if unsure, you can check by seeing if the directory /sys/firmware/efi exists or not).
Also note that the old installer script requires an internet connection to download the rootfs tarball unless you manually download it and pass it as an argument, so check you are connected to the internet.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#issuecomment-1051011349, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBEOQYX3DIOOC24PGC3U46WDXANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
There doesn't seem to be any log.
Try this one.
@.**:~$ cat /tmp/massos-installerlog mke2fs 1.46.5 (30-Dec-2021) Discarding device blocks: done Creating filesystem with 25600000 4k blocks and 6406144 inodes Filesystem UUID: 73f85f90-8bfa-4b2c-934b-472b863b0cb5 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done Writing inode tables: done Creating journal (131072 blocks): done Writing superblocks and filesystem accounting information: done
mount: /dev/sda14 mounted on /tmp/massos-installermnt20220226191242. mount: /dev/sda15 mounted on /tmp/massos-installermnt20220226191242/boot/efi. userdel: massos mail spool (/var/mail/massos) not found Entering chroot environment in /tmp/massos-installermnt20220226191242... chroot: failed to run command ‘/usr/sbin/mkinitramfs’: No such file or directory Exiting chroot environment... Chroot exited with unsuccessful exit code 127. @.***:~$
On Sat, Feb 26, 2022 at 8:26 AM Aaron @.***> wrote:
There doesn't seem to be any log.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#issuecomment-1051822033, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBGTC4PTTLJ3LAG5EX3U5CFCLANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
So the problem is occuring at generating the initramfs, and not being able to locate the mkinitramfs
utility. Previously you mentioned the problem being hanging at the disk setup stage. Are these issues related - is this the same issue or a different issue? If they are different, was the previous issue fixed?
The initramfs generation stage is not run until after the system is installed and the basic setup is done (the full order is disk setup --> installation (extracting squashfs) --> locale/keymap --> timezone --> root password --> user setup --> initramfs --> bootloader), so if the issues are the same or related, did it somehow skip all the way from disk setup to initramfs generation?
Additionally, what version of MassOS are you installing?
massos-2022.02.2-x86_64.iso
it is the same issue. i go thru the installation steps: 1. install...2. select manual partition....location, name.... then it copies the files...then i select the partition, and make the efi partition, and then it wants to create a swap partition....and I ALREADY HAVE A 4GB SWAP PARTITION INSTALLED.....so i select NO....AND get the error message that i sent you. I started all over again and at the "swap" request...i said YES....and selected the swap partition that is on the hard drive sda2....AND GET THE ERROR MESSAGE AGAIN...SAME ONE.
On Sat, Feb 26, 2022 at 5:22 PM The Sonic Master @.***> wrote:
So the problem is occuring at generating the initramfs, and not being able to locate the mkinitramfs utility. Previously you mentioned the problem being hanging at the disk setup stage. Are these issues related - is this the same issue or a different issue? If they are different, was the previous issue fixed?
The initramfs generation stage is not run until after the system is installed and the basic setup is done (the full order is disk setup --> installation (extracting squashfs) --> locale/keymap --> timezone --> root password --> user setup --> initramfs --> bootloader), so did it somehow skip all the way from disk setup to initramfs generation?
Additionally, what version of MassOS are you installing?
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#issuecomment-1052842192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBCX4HSSWRLK4KAKLFLU5FVFTANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
If you are doing option 2 (Install to existing partition) and already have a swap partition, you don't need to select No at the swap choice - you can select Yes and if you already have a swap partition, it will let you select your existing one and it won't reformat it. The same goes for the EFI system partition, if you already have one used by another operating system, it can share it and you don't need to create another.
I've noticed how the message could be misleading as it implies it's going to create another swap partition when it's actually just going to use an existing one you have. This wording has now been fixed in https://github.com/MassOS-Linux/livecd-installer/commit/461074f2c7979092abe211cd17bebaf63f36d617 - the next version of MassOS will include this rewording.
Was the swap partition already swapped on when you got to the installer stage? If so, you might have to manually swap it off with the swapoff
command - the installer will automatically swap it on when it needs to. Maybe something went wrong due to the Swap partition already being swapped on when running the installer - I am unsure. In either case, it might be best to reboot the live CD to restart the installer rather than just restarting the installer directly.
I tried to replicate your issue as closely as I could by installing Ubuntu in UEFI mode in a virtual machine with a swap partition, then booting a MassOS 2022.02.2 live CD and installing MassOS in a dual-boot on the same virtual machine. I had already set up my partitions manually using the Gparted application before running the installer. In the installer, I selected option 2 --> the partition to install MassOS on --> filesystem ext4 --> selected the EFI partition which was the same one also used by Ubuntu --> Selected Yes at the swap choice --> Selected the swap partition which Ubuntu also used --> Selected Yes at the confirmation prompt --> Waited for the installation to complete --> Went through the basic setup --> Successfully finished the installation. I was unable to replicate your issue.
ok, so how do i get the corrected livecd to download?
On Sun, Feb 27, 2022 at 5:46 AM The Sonic Master @.***> wrote:
If you are doing option 2 (Install to existing partition) and already have a swap partition, you don't need to select No at the swap choice - you can select Yes and if you already have a swap partition, it will let you select your existing one and it won't reformat it. The same goes for the EFI system partition, if you already have one used by another operating system, it can share it and you don't need to create another.
I've noticed how the message could be misleading as it implies it's going to create another swap partition when it's actually just going to use an existing one you have. This wording has now been fixed in @.*** https://github.com/MassOS-Linux/livecd-installer/commit/461074f2c7979092abe211cd17bebaf63f36d617
- the next version of MassOS will include this rewording.
Was the swap partition already swapped on when you got to the installer stage? If so, you might have to manually swap it off with the swapoff command - the installer will automatically swap it on when it needs to. Maybe something went wrong due to the Swap partition already being swapped on when running the installer - I am unsure. In either case, it might be best to reboot the live CD to restart the installer rather than just restarting the installer directly.
I tried to replicate your issue as closely as I could by installing Ubuntu in UEFI mode in a virtual machine with a swap partition, then booting a MassOS 2022.02.2 live CD and installing MassOS in a dual-boot on the same virtual machine. I had already set up my partitions manually using the Gparted application before running the installer. In the installer, I selected option 2 --> the partition to install MassOS on --> filesystem ext4 --> selected the EFI partition which was the same one also used by Ubuntu --> Selected Yes at the swap choice --> Selected the swap partition which Ubuntu also used --> Selected Yes at the confirmation prompt --> Waited for the installation to complete --> Went through the basic setup --> Successfully finished the installation. I was unable to replicate your issue.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#issuecomment-1053545146, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBADF3D6NG5HQOG3VJDU5IMKBANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Hi again....
OK, OK, OK......LOL.
i FOLLOWED YOUR LAST EMAIL STEPS AND I GOT IT INSTALLED.
I just don't know what i was doing wrong...except on the swap create, i was worried about how it wanted to format it and I assumed that it would screw up my other os's that were using it. But i realized it was no big deal...so i went ahead and accepted the format and it installed perfectly.
anyway, i THANK YOU very much for your patience.
I really like your program.
Dave
On Sun, Feb 27, 2022 at 10:16 AM Dave Duran @.***> wrote:
ok, so how do i get the corrected livecd to download?
On Sun, Feb 27, 2022 at 5:46 AM The Sonic Master @.***> wrote:
If you are doing option 2 (Install to existing partition) and already have a swap partition, you don't need to select No at the swap choice - you can select Yes and if you already have a swap partition, it will let you select your existing one and it won't reformat it. The same goes for the EFI system partition, if you already have one used by another operating system, it can share it and you don't need to create another.
I've noticed how the message could be misleading as it implies it's going to create another swap partition when it's actually just going to use an existing one you have. This wording has now been fixed in @.*** https://github.com/MassOS-Linux/livecd-installer/commit/461074f2c7979092abe211cd17bebaf63f36d617
- the next version of MassOS will include this rewording.
Was the swap partition already swapped on when you got to the installer stage? If so, you might have to manually swap it off with the swapoff command - the installer will automatically swap it on when it needs to. Maybe something went wrong due to the Swap partition already being swapped on when running the installer - I am unsure. In either case, it might be best to reboot the live CD to restart the installer rather than just restarting the installer directly.
I tried to replicate your issue as closely as I could by installing Ubuntu in UEFI mode in a virtual machine with a swap partition, then booting a MassOS 2022.02.2 live CD and installing MassOS in a dual-boot on the same virtual machine. I had already set up my partitions manually using the Gparted application before running the installer. In the installer, I selected option 2 --> the partition to install MassOS on --> filesystem ext4 --> selected the EFI partition which was the same one also used by Ubuntu --> Selected Yes at the swap choice --> Selected the swap partition which Ubuntu also used --> Selected Yes at the confirmation prompt --> Waited for the installation to complete --> Went through the basic setup --> Successfully finished the installation. I was unable to replicate your issue.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#issuecomment-1053545146, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBADF3D6NG5HQOG3VJDU5IMKBANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
You're welcome. I agree the message about adding a swap partition was misleading; it has now been reworded and this will be incorporated into the next version of MassOS. Glad it's now working for you.
Awesome, thanks! but now I got another BIG problem on here. the xfce4-terminal DOES NOT WORK !
"apt" is not found error message when i type sudo apt install......anything
dpkg is also not found error message.
can't install anything !
how do we fix this ?
On Sun, Feb 27, 2022 at 4:56 PM The Sonic Master @.***> wrote:
Closed #23 https://github.com/MassOS-Linux/MassOS/issues/23.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#event-6151166635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBDO67LOC6LM3EC2AALU5K22TANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
nevermind, I will just uninstall the OS and re-install it .
On Sun, Feb 27, 2022 at 5:17 PM Dave Duran @.***> wrote:
Awesome, thanks! but now I got another BIG problem on here. the xfce4-terminal DOES NOT WORK !
"apt" is not found error message when i type sudo apt install......anything
dpkg is also not found error message.
can't install anything !
how do we fix this ?
On Sun, Feb 27, 2022 at 4:56 PM The Sonic Master @.***> wrote:
Closed #23 https://github.com/MassOS-Linux/MassOS/issues/23.
— Reply to this email directly, view it on GitHub https://github.com/MassOS-Linux/MassOS/issues/23#event-6151166635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAV5VBDO67LOC6LM3EC2AALU5K22TANCNFSM5PIXDWPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
I ran the installer...got to "select partition" using fdisk? first line(recommended}....selected partition....selected "write" at the bottom
and there it sits...no "next" or "continue" buttons....nothing. tried dump choice...and it dumped....lol...into a hole in the ground i guess,
because we are stuck here.