Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
Thelma On 11/24/2020 10:08 PM, the...@sys-concept.com wrote: > I'm getting a kernel panic when booting a new system. > > kernel panic - not syncing: VFS: unable to mount root fs on unknown-block > (0,0) > > fstab: > LABEL=boot/boot vfatnoauto,noatime 1 2 > root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b/ > ext4noatime 0 1 > LABEL=swapnoneswapsw 0 0 > > I even use: emerge --ask sys-kernel/genkernel > genkernel all > > So all the driver are compile-in (nothing should be missing) > > ls -al /boot/vmlinu* /boot/initramfs* > -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 > /boot/initramfs-5.4.72-gentoo-x86_64.img > -rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo > -rwxr-xr-x 1 root root 8513920 Nov 24 21:18 > /boot/vmlinuz-5.4.72-gentoo-x86_64 This problem is solved, it seems to me I was booting old kernel. Removing old kernel and re-running: grub-mkconfig -o /boot/grub/grub.cfg Solved the problem.
[gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
I'm getting a kernel panic when booting a new system. kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0) fstab: LABEL=boot /boot vfatnoauto,noatime 1 2 root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / ext4noatime 0 1 LABEL=swap noneswapsw 0 0 I even use: emerge --ask sys-kernel/genkernel genkernel all So all the driver are compile-in (nothing should be missing) ls -al /boot/vmlinu* /boot/initramfs* -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920 Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64 But at the end of the compilation I get: * Kernel compiled successfully! * * --no-bootloader set; Skipping bootloader update ... * * Required kernel parameter: * * root=/dev/$ROOT * * Where $ROOT is the device node for your root partition as the * one specified in /etc/fstab * If you require Genkernel's hardware detection features, you MUST * tell your bootloader to use the provided initramfs file '/boot/initramfs-5.4.72-gentoo-x86_64.img'. * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * Do NOT report kernel bugs as genkernel bugs unless your bug * is about the default genkernel configuration... * * Make sure you have the latest ~arch genkernel before reporting bugs. -- Thelma
Re: [gentoo-user] boot partition size
On 11/24/2020 04:21 PM, Michael wrote: > On Tuesday, 24 November 2020 21:51:53 GMT the...@sys-concept.com wrote: >> I run gentoo installation from: >> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks >> >> parted -a optimal /dev/nvme0n1 >> >> Device StartEndSectors Size Type >> /dev/nvme0n1p12048 6143 40962M BIOS boot >> /dev/nvme0n1p26144 268287 262144 128M EFI System >> /dev/nvme0n1p3 26828813168631048576 512M Linux filesystem >> /dev/nvme0n1p4 1316864 3907027119 3905710256 1.8T Linux filesystem > > I am not clear if this is a UEFI MoBo or not. If yes, you can use the UEFI > boot manager, instead of Legacy BIOS and you do not need a 'BIOS boot > partition'. If instead you will be booting this disk both in Legacy BIOS and > UEFI modes, then leave the 'BIOS boot partition' as you have it. When you > install GRUB in the MBR it will drop in there its Stage 2 binary code. > > >> When I compiled kernel and run: make install >> it complained not enough space on disk >> >> sh ./arch/x86/boot/install.sh 5.4.72-gentoo arch/x86/boot/bzImage \ >> System.map "/boot" >> cat: write error: No space left on device >> make[1]: *** [arch/x86/boot/Makefile:155: install] >> >> /dev/nvme0n1p4 1.8T 3.5G 1.7T 1% / >> cgroup_root 10M 0 10M 0% /sys/fs/cgroup >> udev 10M 0 10M 0% /dev >> tmpfs16G 0 16G 0% /dev/shm >> /dev/sda2 6.4M 6.4M 2.0K 100% /boot >> >> (sda2 - I think is a bootable USB) > > Your /boot mountpoint should be used for /dev/nvme0n1p2, if this is a UEFI > installation. If as you report above /boot is on /dev/sda2 you have not > followed the handbook correctly. In particular you have not mounted /dev/ > nvme0n1p2 as /mnt/gentoo/boot before you chrooted into /mnt/gentoo. That was the case, I just mounted the "/dev/nvme0n1p2" partition on /boot and it worked. But now I'm getting an error with installing grub. grub-install --target=x86_64-efi --efi-directory=/boot Installing for x86_64-efi platform. grub-install: error: /boot doesn't look like an EFI partition. fdisk is showing the /dev/nvme0n1p2 is EFI /dev/nvme0n1p26144 268287 262144 128M EFI System No, don't need BIOS, boot partition (created it by mistake), I think I can remove this partition with fdisk /dev/nvme0n1p12048 6143 40962M BIOS boot
Re: [gentoo-user] Re: Grub and multiple distros on LVM [was duplicate gentoo system ...]
On Tue, 24 Nov 2020 23:25:38 - (UTC), Grant Edwards wrote: > >> In grub, does chainloading an LVM virtual partition work the same as > >> chainloading a "real" partition? > > > > I suspect not as GRUB will be reading the menu files and GRUB doesn't > > read from LVM volumes. > > Then what does grub's "lvm" module do, and how does it read the > distro's .cfg files from the LVM volumes in which the various distros > are installed? Maybe what you want. I haven't used LVM or GRUB much n the past several years, so maybe it is OK now, although a quick web search before I posted implied it wasn't. RTFM time? -- Neil Bothwick After all is said and done let there not be more said than done. pgplqXceJjpzT.pgp Description: OpenPGP digital signature
[gentoo-user] Re: Grub and multiple distros on LVM [was duplicate gentoo system ...]
On 2020-11-24, Neil Bothwick wrote: > On Tue, 24 Nov 2020 19:04:20 - (UTC), Grant Edwards wrote: > >> In grub, does chainloading an LVM virtual partition work the same as >> chainloading a "real" partition? > > I suspect not as GRUB will be reading the menu files and GRUB doesn't > read from LVM volumes. Then what does grub's "lvm" module do, and how does it read the distro's .cfg files from the LVM volumes in which the various distros are installed? -- Grant
Re: [gentoo-user] boot partition size
the...@sys-concept.com wrote: > I run gentoo installation from: > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks > > parted -a optimal /dev/nvme0n1 > > Device StartEndSectors Size Type > /dev/nvme0n1p12048 6143 40962M BIOS boot > /dev/nvme0n1p26144 268287 262144 128M EFI System > /dev/nvme0n1p3 26828813168631048576 512M Linux filesystem > /dev/nvme0n1p4 1316864 3907027119 3905710256 1.8T Linux filesystem > > When I compiled kernel and run: make install > it complained not enough space on disk > > sh ./arch/x86/boot/install.sh 5.4.72-gentoo arch/x86/boot/bzImage \ > System.map "/boot" > cat: write error: No space left on device > make[1]: *** [arch/x86/boot/Makefile:155: install] > > /dev/nvme0n1p4 1.8T 3.5G 1.7T 1% / > cgroup_root 10M 0 10M 0% /sys/fs/cgroup > udev 10M 0 10M 0% /dev > tmpfs16G 0 16G 0% /dev/shm > /dev/sda2 6.4M 6.4M 2.0K 100% /boot > > (sda2 - I think is a bootable USB) > >From that last tidbit, yep, /boot appears to be full. I think the smallest I ever used for /boot was like 300MBs or so. Right now, mine is about 400MBs and is 30% used. I'd think 100MBs would suffice if you don't keep to many old kernels laying about. I cleaned out old kernels a while back. Generally when I reach about 50% or so, I clean house. This is du -shc /boot for my system. Maybe it will help you determine the minimum size needed. root@fireball / # du -shc /boot/* 0 /boot/boot 102K /boot/config-4.19.40-2 110K /boot/config-5.6.7-2 34M /boot/grub 6.9M /boot/grub2 8.9M /boot/initramfs-4.19.40-3.img 8.9M /boot/initramfs-5.6.7-2.img 7.0M /boot/kernel-4.19.40-3 11M /boot/kernel-5.6.7-2 12K /boot/lost+found 1.2M /boot/memtest86-iso 363K /boot/memtest86plus 152K /boot/mt500rc1.bin 4.0M /boot/System.map 4.0M /boot/System.map-5.4.32 4.0M /boot/System.map-5.4.32.old 4.0M /boot/System.map.old 94M total root@fireball / # Let's see. Kernel: 12MBs at least. Grub, not sure which one is in actual use but picking largest one: 35MBs. Stupid init thingy: 10MBs. System.map file: 4MBs. That's 61MBs. 100MBs would be a bit of a squeeze but doable. Future needs may cause trouble tho. Hope that helps. Dale :-) :-)
Re: [gentoo-user] Re: duplicate gentoo system - errors
On Tue, 24 Nov 2020 18:37:43 +, antlists wrote: > Personally, I wouldn't use dm-crypt, but then I'm not particularly into > crypto. It's a laptop that could be lost or stolen, not using some form of encryption would be insane. I don't use dm-crypt on desktop systems as long as the environment is secure. -- Neil Bothwick "We can't solve problems by using the same kind of thinking we used when we created them." (Albert Einstein) pgpjP2r1VpITm.pgp Description: OpenPGP digital signature
Re: [gentoo-user] boot partition size
On Tuesday, 24 November 2020 21:51:53 GMT the...@sys-concept.com wrote: > I run gentoo installation from: > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks > > parted -a optimal /dev/nvme0n1 > > Device StartEndSectors Size Type > /dev/nvme0n1p12048 6143 40962M BIOS boot > /dev/nvme0n1p26144 268287 262144 128M EFI System > /dev/nvme0n1p3 26828813168631048576 512M Linux filesystem > /dev/nvme0n1p4 1316864 3907027119 3905710256 1.8T Linux filesystem I am not clear if this is a UEFI MoBo or not. If yes, you can use the UEFI boot manager, instead of Legacy BIOS and you do not need a 'BIOS boot partition'. If instead you will be booting this disk both in Legacy BIOS and UEFI modes, then leave the 'BIOS boot partition' as you have it. When you install GRUB in the MBR it will drop in there its Stage 2 binary code. > When I compiled kernel and run: make install > it complained not enough space on disk > > sh ./arch/x86/boot/install.sh 5.4.72-gentoo arch/x86/boot/bzImage \ > System.map "/boot" > cat: write error: No space left on device > make[1]: *** [arch/x86/boot/Makefile:155: install] > > /dev/nvme0n1p4 1.8T 3.5G 1.7T 1% / > cgroup_root 10M 0 10M 0% /sys/fs/cgroup > udev 10M 0 10M 0% /dev > tmpfs16G 0 16G 0% /dev/shm > /dev/sda2 6.4M 6.4M 2.0K 100% /boot > > (sda2 - I think is a bootable USB) Your /boot mountpoint should be used for /dev/nvme0n1p2, if this is a UEFI installation. If as you report above /boot is on /dev/sda2 you have not followed the handbook correctly. In particular you have not mounted /dev/ nvme0n1p2 as /mnt/gentoo/boot before you chrooted into /mnt/gentoo. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Grub and multiple distros on LVM [was duplicate gentoo system ...]
On Tue, 24 Nov 2020 19:04:20 - (UTC), Grant Edwards wrote: > In grub, does chainloading an LVM virtual partition work the same as > chainloading a "real" partition? I suspect not as GRUB will be reading the menu files and GRUB doesn't read from LVM volumes. -- Neil Bothwick "A hundred years of forgetting and it all comes rushing back..." pgpgKNstLxtuP.pgp Description: OpenPGP digital signature
[gentoo-user] boot partition size
I run gentoo installation from: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks parted -a optimal /dev/nvme0n1 Device StartEndSectors Size Type /dev/nvme0n1p12048 6143 40962M BIOS boot /dev/nvme0n1p26144 268287 262144 128M EFI System /dev/nvme0n1p3 26828813168631048576 512M Linux filesystem /dev/nvme0n1p4 1316864 3907027119 3905710256 1.8T Linux filesystem When I compiled kernel and run: make install it complained not enough space on disk sh ./arch/x86/boot/install.sh 5.4.72-gentoo arch/x86/boot/bzImage \ System.map "/boot" cat: write error: No space left on device make[1]: *** [arch/x86/boot/Makefile:155: install] /dev/nvme0n1p4 1.8T 3.5G 1.7T 1% / cgroup_root 10M 0 10M 0% /sys/fs/cgroup udev 10M 0 10M 0% /dev tmpfs16G 0 16G 0% /dev/shm /dev/sda2 6.4M 6.4M 2.0K 100% /boot (sda2 - I think is a bootable USB) -- Thelma
Re: [gentoo-user] duplicate gentoo system - errors
On Tue, Nov 24, 2020 at 9:49 AM Walter Dnes wrote: > > On Tue, Nov 24, 2020 at 07:56:07PM +1100, Adam Carter wrote > > > 3) AMD code runs only on same or newer AMD, because it has the 3DNow! > > >instruction set the others lack. > > > > > > > FYI 3dnow and 3dnowext went away some time ago. It's not in any of the > > Bulldozer or Zen CPUs. > > So you're saying that newer AMDs may not run code optimized for older > AMDs ??? It depends on what you mean by "optimized." If you mean using -march, then yes, newer AMD OR Intel CPUs may not run software built for older ones. They get rid of instructions as well as adding them, and some lines have instructions not present in others. If you use -mtune then the code will work on any amd64 processor - AMD or Intel. If you use -march then you generally need to rebuild everything without it (or at least @system) before you go switching CPUs. -- Rich
Re: [gentoo-user] duplicate gentoo system - errors
On Tuesday, 24 November 2020 17:23:41 GMT the...@sys-concept.com wrote: > On 11/23/2020 01:29 AM, Neil Bothwick wrote: > > On Sun, 22 Nov 2020 18:27:53 -0700, the...@sys-concept.com wrote: > >>> I would confirm that you are really booted from the new disk and not > >>> the old one. It is possible that the MBR from the new disk was used > >>> to boot, but if /etc/fstab says /boot is mounted from /dev/sda1 then > >>> that does seem wrong. I almost always put an empty file in the root > >>> of each partition named for the disk/partition just so I can be sure > >>> what's actually mounted. Is /etc/fstab identical on both disks? > >>> What does fstab say about where / is mounted from? > >> > >> You are absolutely correct. I was booting the whole time the Western > >> Digital (old drive). :-/ My mistake, once I removed the WD drive the > >> new M.2 SSD doesn't even boot. > > > > Check the settings in your BIOS/firmware to make sure it detects the > > drive and is set to boot from it. > > I'm back. > > Yes, BIOS recognized the system, I have one SATA disk connected to it and it > is booting OK. But disconnected it so I don't mess something up. You'll need to reconnect the old SATA in a minute - see below. > >> I think the easiest way would be to re-install the Getnoo from scratch > > > > And if it still doesn't work because of a firmware issue, you still have > > a non-booting system but with no OS installed either. It's better to try > > and diagnose the problem rather than throwing everything away in the hope > > that the problem goes with it. > > I booted from Gontoo bootable USB and running: blkid > showing: > blkid > /dev/loop0: TYPE="squashfs" > /dev/nvme0n1p1: UUID="5db43d49-810a-4806-955e-d59c4d35ec23" > BLOCK_SIZE="4096" TYPE="ext2" > PARTUUID="743a7887-c02e-4855-8cb7-865247682bff" /dev/nvme0n1p2: > UUID="0c23b340-b5c6-437d-bde9-c5539e64677a" BLOCK_SIZE="4096" TYPE="ext4" > PARTUUID="696091c3-ed27-4a4a-b371-8fd59e2b7a4d" /dev/nvme0n1p3: > UUID="77e449db-7dca-410d-9e70-50165c6ccbb8" TYPE="swap" > PARTUUID="b2871b7b-5bd0-4db3-90a5-50545b129a97" > > > Disk /dev/nvme0n1: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors > Disk model: Force MP600 > 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: gpt > Disk identifier: FE896335-0C8D-487E-9391-ED43A85D3292 > > Device StartEndSectors Size Type > /dev/nvme0n1p1 204810506231048576 512M Linux filesystem > /dev/nvme0n1p21050624 1971752959 1970702336 939.7G Linux filesystem > /dev/nvme0n1p3 3840102400 3907028991 66926592 31.9G Linux swap > > Shouldn't: /dev/nvme0n1p1 be "Bios Boot" > Do I need to change it with "fdisk" The /dev/nvme0n1p1 partition type should be whatever the /dev/sda1 of the old disk was. If you are using a GPT disk on a Legacy BIOS MoBo, with a Hybrid MBR configuration, then yes, it should be a 'BIOS Boot partition' to contain the GRUB Stage 2 code. However, if /dev/nvme0n1p1 is just a conventional /boot partition with an ext2 fs as you show above, containing your /boot/grub/ directory files, then 'Linux filesystem' is the correct partition type. > When trying to mount /boot > mount /dev/nvme0n1p1 /mnt/gentoo/boot > livecd ~ # ll /mnt/gentoo/boot/ > total 16 > drwx-- 2 root root 16384 Nov 22 22:26 lost+found > > There is nothing there. So the contents of /dev/sda1 were not copied over. Were the contents of /dev/sda2 copied over to dev/nvme0n1p2 ? > I'm not sure if there is a point of fixing it at this point. It might take > less time to reinstall gentoo. It will take much less time to use clonezilla to clone the whole disk as I originally suggested, change the UUIDs of the partitions, update GRUB on the new disk, then update GRUB on the old disk. Alternatively, it will also take less time to use Gparted to create and format the partitions you want, then use rsync/tar/cp to copy over the filesystem contents from the old to the new partitions, then update GRUB. If /dev/nvme0n1p1 is the only partition which needs fixing and since this is a small partition in size, it won't take long to reconnect /dev/sda to the MoBo, boot a LiveUSB and run: dd if=/dev/sda1 of=/dev/nvme0n1p1 If you have not copied over the MBR boot loader in sector 0, or have not installed afresh GRUB on the new disk, then you will also need to copy over the MBR sector: dd if=/dev/sda of=/dev/nvme0n1 bs=446 count=1 Or, if you want to also copy over the MBR partition table as it was on the old disk, change the block size to 512 bytes: dd if=/dev/sda of=/dev/nvme0n1 bs=512 count=1 Any of the above should take significantly less time than reinstalling gentoo, then fishing old ebuilds of your required applications from the attic, fetching corresponding source files, only to discover they won't compile on the new installation because of whatever changes may have taken
[gentoo-user] Grub and multiple distros on LVM [was duplicate gentoo system ...]
On 2020-11-24, antlists wrote: > >> Cool, I'll have to read up on using volumes for that. How far back in >> time can you go before you get to distros that would have problems? > > How old is LVM? It's been around for ages, I think. We regularly run into customers running distros that came out 10 years ago. Not long ago, I was working with a customer who was running RHEL 6 and kernel 2.6.32 on production machines. Yes, RHEL 6 is still supported (though not for long). According to the LVM Wikipedia page, 2.6.32 is old enough that journalling filesystems didn't work correctly on top of LVM. That said, it's quite possible RH backported LVM improvements to 2.6.32 so that's not an issue. Right now, I have a small "grub" partition which has menu that allows chainloading any of dozen or so main partitions, each of which has a linux distro installed (with a bootloader installed in that partition). I've been reading up on LVM vs. grub, and all of the examples I find of booting multiple distros on LVM don't seem to be chainloading. Rather they point the "master" grub at the root "partition" and that partition's .cfg file. However, that assumes that the distro uses grub, and that the .cfg file is compatible with the "master" grub executables. I'd rather not rely on that assumption and just do chainloading like I always have. In grub, does chainloading an LVM virtual partition work the same as chainloading a "real" partition? -- Grant
Re: [gentoo-user] Re: duplicate gentoo system - errors
On 24/11/2020 16:51, Grant Edwards wrote: On 2020-11-24, Neil Bothwick wrote: On Tue, 24 Nov 2020 16:38:59 - (UTC), Grant Edwards wrote: But actual partitions? Yes. Each with a separate Linux distro installed. Perhaps you can do that with a volume manager instead of partitions (using partitions has worked fine for the past 20 years, so I've never looked into it). Of course you can, and it makes adding and removing distros much simpler. Cool, I'll have to read up on using volumes for that. How far back in time can you go before you get to distros that would have problems? How old is LVM? It's been around for ages, I think. The other nice advantage of LVM is that if you've got a big archive disk, you can migrate the partitions to that disk and move them off of your live system (but you can migrate them back if you need them). Personally, I wouldn't use dm-crypt, but then I'm not particularly into crypto. Read up on it, but I would be surprised if it didn't support stuff right back to last century. Cheers, Wol
Re: [gentoo-user] duplicate gentoo system - errors
On 11/23/2020 01:29 AM, Neil Bothwick wrote: > On Sun, 22 Nov 2020 18:27:53 -0700, the...@sys-concept.com wrote: > >>> I would confirm that you are really booted from the new disk and not >>> the old one. It is possible that the MBR from the new disk was used >>> to boot, but if /etc/fstab says /boot is mounted from /dev/sda1 then >>> that does seem wrong. I almost always put an empty file in the root >>> of each partition named for the disk/partition just so I can be sure >>> what's actually mounted. Is /etc/fstab identical on both disks? >>> What does fstab say about where / is mounted from? >> >> You are absolutely correct. I was booting the whole time the Western >> Digital (old drive). :-/ My mistake, once I removed the WD drive the >> new M.2 SSD doesn't even boot. > > Check the settings in your BIOS/firmware to make sure it detects the > drive and is set to boot from it. I'm back. Yes, BIOS recognized the system, I have one SATA disk connected to it and it is booting OK. But disconnected it so I don't mess something up. >> I think the easiest way would be to re-install the Getnoo from scratch > > And if it still doesn't work because of a firmware issue, you still have > a non-booting system but with no OS installed either. It's better to try > and diagnose the problem rather than throwing everything away in the hope > that the problem goes with it. I booted from Gontoo bootable USB and running: blkid showing: blkid /dev/loop0: TYPE="squashfs" /dev/nvme0n1p1: UUID="5db43d49-810a-4806-955e-d59c4d35ec23" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="743a7887-c02e-4855-8cb7-865247682bff" /dev/nvme0n1p2: UUID="0c23b340-b5c6-437d-bde9-c5539e64677a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="696091c3-ed27-4a4a-b371-8fd59e2b7a4d" /dev/nvme0n1p3: UUID="77e449db-7dca-410d-9e70-50165c6ccbb8" TYPE="swap" PARTUUID="b2871b7b-5bd0-4db3-90a5-50545b129a97" Disk /dev/nvme0n1: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: Force MP600 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: gpt Disk identifier: FE896335-0C8D-487E-9391-ED43A85D3292 Device StartEndSectors Size Type /dev/nvme0n1p1 204810506231048576 512M Linux filesystem /dev/nvme0n1p21050624 1971752959 1970702336 939.7G Linux filesystem /dev/nvme0n1p3 3840102400 3907028991 66926592 31.9G Linux swap Shouldn't: /dev/nvme0n1p1 be "Bios Boot" Do I need to change it with "fdisk" When trying to mount /boot mount /dev/nvme0n1p1 /mnt/gentoo/boot livecd ~ # ll /mnt/gentoo/boot/ total 16 drwx-- 2 root root 16384 Nov 22 22:26 lost+found There is nothing there. I'm not sure if there is a point of fixing it at this point. It might take less time to reinstall gentoo.
[gentoo-user] Re: duplicate gentoo system - errors
On 2020-11-24, Neil Bothwick wrote: > On Tue, 24 Nov 2020 16:38:59 - (UTC), Grant Edwards wrote: > >> > But actual partitions? >> >> Yes. Each with a separate Linux distro installed. >> >> Perhaps you can do that with a volume manager instead of partitions >> (using partitions has worked fine for the past 20 years, so I've >> never looked into it). > > Of course you can, and it makes adding and removing distros much > simpler. Cool, I'll have to read up on using volumes for that. How far back in time can you go before you get to distros that would have problems? -- Grant
Re: [gentoo-user] Re: duplicate gentoo system - errors
On Tue, 24 Nov 2020 16:38:59 - (UTC), Grant Edwards wrote: > > But actual partitions? > > Yes. Each with a separate Linux distro installed. > > Perhaps you can do that with a volume manager instead of partitions > (using partitions has worked fine for the past 20 years, so I've never > looked into it). Of course you can, and it makes adding and removing distros much simpler. I've also done it on this laptop with btrfs subvolumes, a different subvolume for each distro's root but a shared /home subvolume. All of them on a dm-crypt device, so only one password needed whichever distro is used. -- Neil Bothwick Can vegetarians eat animal crackers? pgp2gNd1RtPBq.pgp Description: OpenPGP digital signature
[gentoo-user] Re: duplicate gentoo system - errors
On 2020-11-24, Jack wrote: > I only have two or three such distros I use for testing, but I have > each in a VirtualBox machine. For me, spinning up a VM is easier > than a real reboot. I don't trust VMs when testing drivers for PCI cards or applicatoins that use raw Ethernet. -- Grant
[gentoo-user] Re: duplicate gentoo system - errors
On 2020-11-24, Neil Bothwick wrote: > On Tue, 24 Nov 2020 15:01:35 - (UTC), Grant Edwards wrote: > >> > Can you imagine an fstab with 22 partitions? Doesn't bear thinking >> > about. >> >> Yes. I have one with 12 and often wish it had more. >> >> It comes in handy when you need to test drivers and applications >> against different distros, and your customers use 4-5 different >> versions of RHEL, 4-5 different versions of Ubuntu, a couple random >> versions of SuSe, Mint, Arch, etc. You could of course, have 12 (or >> 22) different hard drives that you swap in/out of the machine, but >> that's tiresome and expensive. > > But actual partitions? Yes. Each with a separate Linux distro installed. Perhaps you can do that with a volume manager instead of partitions (using partitions has worked fine for the past 20 years, so I've never looked into it).
Re: [gentoo-user] Re: duplicate gentoo system - errors
On 11/24/20 10:41 AM, Neil Bothwick wrote: On Tue, 24 Nov 2020 15:01:35 - (UTC), Grant Edwards wrote: Can you imagine an fstab with 22 partitions? Doesn't bear thinking about. Yes. I have one with 12 and often wish it had more. It comes in handy when you need to test drivers and applications against different distros, and your customers use 4-5 different versions of RHEL, 4-5 different versions of Ubuntu, a couple random versions of SuSe, Mint, Arch, etc. You could of course, have 12 (or 22) different hard drives that you swap in/out of the machine, but that's tiresome and expensive. But actual partitions? Without some sort of volume management? I have 27 btrfs subvolumes on one system, but I wouldn't want to do that with partitions. And you don't find yourself wishing for more with a volume manager, just create whatever you need... which is how I reached 27. I only have two or three such distros I use for testing, but I have each in a VirtualBox machine. For me, spinning up a VM is easier than a real reboot.
Re: [gentoo-user] Re: duplicate gentoo system - errors
On Tue, 24 Nov 2020 15:01:35 - (UTC), Grant Edwards wrote: > > Can you imagine an fstab with 22 partitions? Doesn't bear thinking > > about. > > Yes. I have one with 12 and often wish it had more. > > It comes in handy when you need to test drivers and applications > against different distros, and your customers use 4-5 different > versions of RHEL, 4-5 different versions of Ubuntu, a couple random > versions of SuSe, Mint, Arch, etc. You could of course, have 12 (or > 22) different hard drives that you swap in/out of the machine, but > that's tiresome and expensive. But actual partitions? Without some sort of volume management? I have 27 btrfs subvolumes on one system, but I wouldn't want to do that with partitions. And you don't find yourself wishing for more with a volume manager, just create whatever you need... which is how I reached 27. -- Neil Bothwick DOS never says "EXCELLENT command or filename"... pgpv3_BgVa1I4.pgp Description: OpenPGP digital signature
[gentoo-user] Re: duplicate gentoo system - errors
On 2020-11-24, Neil Bothwick wrote: > On Tue, 24 Nov 2020 09:20:52 +, Peter Humphrey wrote: > >> Can you imagine an fstab with 22 partitions specified with UUIDs? >> Doesn't bear thinking about. > > Can you imagine an fstab with 22 partitions? Doesn't bear thinking > about. Yes. I have one with 12 and often wish it had more. It comes in handy when you need to test drivers and applications against different distros, and your customers use 4-5 different versions of RHEL, 4-5 different versions of Ubuntu, a couple random versions of SuSe, Mint, Arch, etc. You could of course, have 12 (or 22) different hard drives that you swap in/out of the machine, but that's tiresome and expensive. -- Grant
Re: [gentoo-user] duplicate gentoo system - errors
On Tue, Nov 24, 2020 at 07:56:07PM +1100, Adam Carter wrote > > 3) AMD code runs only on same or newer AMD, because it has the 3DNow! > >instruction set the others lack. > > > > FYI 3dnow and 3dnowext went away some time ago. It's not in any of the > Bulldozer or Zen CPUs. So you're saying that newer AMDs may not run code optimized for older AMDs ??? -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] duplicate gentoo system - errors
On Tue, 24 Nov 2020 09:20:52 +, Peter Humphrey wrote: > My workstation has one NVMe drive and two SATAs. They're always > detected in the same order, so I've no need to render my fstab > illegible with UUIDs. I could use labels, but why bother? The old > system ain't broke, so I've no need to fix it. But you can fix it in your own time, waiting until it breaks is never convenient. > Can you imagine an fstab with 22 partitions specified with UUIDs? > Doesn't bear thinking about. Can you imagine an fstab with 22 partitions? Doesn't bear thinking about. ;-) -- Neil Bothwick Anything is possible if you don't know what you are talking about. pgpaS31xRtgax.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Converting Unix time to local time
On Monday, 23 November 2020 21:47:11 GMT Jack wrote:
> For many years, I've had this small script in my home directory -
> unfortunately I rarely remember to use it. I have no idea
> where I got it, but it's got a timestamp of about four years ago.
> However, now that I actually look at it,
> the author is a frequent contributor to this list,
> so it was likely mentioned here.
>
> #!/usr/bin/awk -f
>
##
###
> # log-emerge:
> #
> # A filter which converts the time stamp on emerge log files to a human
> # readable form.
> #
> # Written by Alan Mackenzie , 2015-10-20.
> # This script is in the public domain.
> #
> # To use, pipe all or part of a log file through this filter.
>
##
###
> {
> sec = strtonum(substr($1, 1, 11))
> $1 = strftime("%Y-%m-%d %H:%M:%S %z", sec, 0) ":"
> print
> }
I didn't read the earlier msgs in this thread,
but I've long used my own Bash function (in .bashrc ) :
# translate UNIX date to human-readable
function th { date -d @$1 ; }
eg the last line in emerge.log is "1606047812: *** terminating." ,
so I hilite the number & drop it into the function :
th 1606047812
which gives the timestamp
Sun Nov 22 07:23:32 AM EST 2020
HTH
--
,,
SUPPORT ___//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT`-O--O---' purslowatcadotinterdotnet
Re: [gentoo-user] duplicate gentoo system - errors
On Tuesday, 24 November 2020 10:43:25 GMT Michael wrote: > On Tuesday, 24 November 2020 09:20:52 GMT Peter Humphrey wrote: > > My workstation has one NVMe drive and two SATAs. They're always detected > > in the same order, so I've no need to render my fstab illegible with > > UUIDs. I could use labels, but why bother? The old system ain't broke, so > > I've no need to fix it. > > It depends on the bus and disk technology. I have an ARM driven box with a > conventional 1TB spinning SATA drive and a USB stick. You can never tell > which one will be detected as /dev/sda and which as /dev/sdb. If you have > more than one pluggable devices the same identification problem is likely to > arise. LABELs and/or UUIDs solve this problem - reliably. Yes, I have several USB sticks, but specifically because they're transient I expect those to have sdX assigned chronologically. I don't boot with them inserted, so I still don't need anything more than /dev/sdX in fstab. > > Can you imagine an fstab with 22 partitions specified with UUIDs? Doesn't > > bear thinking about. > > Copying and pasting the output of blkid helps complete the fstab easily and > commented lines allow me to explain to myself block device location and > purpose, should I need to revisit it some months/years later. That's still much more complex than my setup, and less legible. To a degree, this is a hobby machine, so I create, delete and move partitions more often than many people do. I couldn't possibly work with UUIDs; it'd be as bad as trying to read someone else's perl code. :) -- Regards, Peter.
Re: [gentoo-user] duplicate gentoo system - errors
On Tuesday, 24 November 2020 09:20:52 GMT Peter Humphrey wrote: > On Monday, 23 November 2020 19:02:57 GMT antlists wrote: > > If you're messing about with disks, partitions, etc, you NEED to have a > > basic understanding of UUIDs. > > That may be true if you have more than one disk of a given type, but if you > have only one SATA drive and one NVMe, for instance, there's no chance of > their being misnumbered at boot. > > My workstation has one NVMe drive and two SATAs. They're always detected in > the same order, so I've no need to render my fstab illegible with UUIDs. I > could use labels, but why bother? The old system ain't broke, so I've no > need to fix it. It depends on the bus and disk technology. I have an ARM driven box with a conventional 1TB spinning SATA drive and a USB stick. You can never tell which one will be detected as /dev/sda and which as /dev/sdb. If you have more than one pluggable devices the same identification problem is likely to arise. LABELs and/or UUIDs solve this problem - reliably. > Can you imagine an fstab with 22 partitions specified with UUIDs? Doesn't > bear thinking about. Copying and pasting the output of blkid helps complete the fstab easily and commented lines allow me to explain to myself block device location and purpose, should I need to revisit it some months/years later. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Converting Unix time to local time
On Tuesday, 24 November 2020 09:28:13 GMT I wrote: > There should be a one-liner in awk too. Someone will come along in a minute > and tell us. At least, I hope so because I'd like to use it too. I should have added my thanks for the script. Rude of me. -- Regards, Peter.
Re: [gentoo-user] Converting Unix time to local time
On Monday, 23 November 2020 21:47:11 GMT Jack wrote:
> For many years, I've had this small script in my home directory -
> unfortunately I rarely remember to use it. I have no idea where I got
> it, but it's got a timestamp of about four years ago. However, now
> that I actually look at it, the author is a frequent contributor to
> this list, so it was likely mentioned here.
>
> #!/usr/bin/awk -f
>
##
###
> # log-emerge:
> #
> # A filter which converts the time stamp on emerge log files to a human
> # readable form.
> #
> # Written by Alan Mackenzie , 2015-10-20.
> # This script is in the public domain.
> #
> # To use, pipe all or part of a log file through this filter.
>
##
###
> {
> sec = strtonum(substr($1, 1, 11))
> $1 = strftime("%Y-%m-%d %H:%M:%S %z", sec, 0) ":"
> print
> }
There should be a one-liner in awk too. Someone will come along in a minute and
tell us.
At least, I hope so because I'd like to use it too.
--
Regards,
Peter.
Re: [gentoo-user] duplicate gentoo system - errors
On Monday, 23 November 2020 19:02:57 GMT antlists wrote: > If you're messing about with disks, partitions, etc, you NEED to have a > basic understanding of UUIDs. That may be true if you have more than one disk of a given type, but if you have only one SATA drive and one NVMe, for instance, there's no chance of their being misnumbered at boot. My workstation has one NVMe drive and two SATAs. They're always detected in the same order, so I've no need to render my fstab illegible with UUIDs. I could use labels, but why bother? The old system ain't broke, so I've no need to fix it. Can you imagine an fstab with 22 partitions specified with UUIDs? Doesn't bear thinking about. -- Regards, Peter.
Re: [gentoo-user] duplicate gentoo system - errors
> 3) AMD code runs only on same or newer AMD, because it has the 3DNow! >instruction set the others lack. > FYI 3dnow and 3dnowext went away some time ago. It's not in any of the Bulldozer or Zen CPUs.
