Re: Problem booting current
If you boot cd/usb, zpool import -N zroot, then zpool get all, post the output. Sent from my iPhone > On 1. Jun 2022, at 16:54, Filippo Moretti wrote: > > > I installed CURRENT with memstick of May the 27th. > I tired first UEFI and all I got was a flashing - on screen > I then tried BIOS+ UEFI and I get a mountroot prompt > due to > zfs:zroot/ROOT/default failed with error 22 (wich is the same error I got > from current a few days ago)reported in a previous message. > Are there other setting I could try? > Sincerely > Filippo
Problem booting current
I installed CURRENT with memstick of May the 27th.I tired first UEFI and all I got was a flashing - on screenI then tried BIOS+ UEFI and I get a mountroot prompt due tozfs:zroot/ROOT/default failed with error 22 (wich is the same error I got from current a few days ago)reported in a previous message.Are there other setting I could try?SincerelyFilippo
Re: Problem booting CURRENT
After world I can no longer boot my system:cannot open /boot/lua/loader:no such file or directory If I try load /boot/kernel.old/kernel /boot/kernel/kernel can't find /boot/kernel.old/kernel nor /boot/kernel/kernelIt is rather strange I have never found these issues before.Filippo On Monday, May 30, 2022 at 09:34:43 AM GMT+2, Filippo Moretti wrote: I did not use GELI non was the hard disk encrypted.I did try to reinstall with snapshot of May the 27th and I had the same problem:I ended up reinstalling with UFS instead.Than you Filippo On Sunday, May 29, 2022 at 11:49:01 PM GMT+2, Graham Perrin wrote: On 27/05/2022 10:10, Filippo Moretti wrote: I run into this problem after rebboting my computer with CURRENT zfs:zroot/ROOT/default failed with error 22 the mountroot freezes and I have to power off to restart. I did not apgrade or any changes since I used it last time. Is it possible to recover my system? Filippo GELI encrypted?
Re: Problem booting CURRENT
I did not use GELI non was the hard disk encrypted.I did try to reinstall with snapshot of May the 27th and I had the same problem:I ended up reinstalling with UFS instead.Than you Filippo On Sunday, May 29, 2022 at 11:49:01 PM GMT+2, Graham Perrin wrote: On 27/05/2022 10:10, Filippo Moretti wrote: I run into this problem after rebboting my computer with CURRENT zfs:zroot/ROOT/default failed with error 22 the mountroot freezes and I have to power off to restart. I did not apgrade or any changes since I used it last time. Is it possible to recover my system? Filippo GELI encrypted?
Re: Problem booting CURRENT
On 27/05/2022 10:10, Filippo Moretti wrote: I run into this problem after rebboting my computer with CURRENT zfs:zroot/ROOT/default failed with error 22 the mountroot freezes and I have to power off to restart. I did not apgrade or any changes since I used it last time. Is it possible to recover my system? Filippo GELI encrypted?
Problem booting CURRENT
I run into this problem after rebboting my computer with CURRENTzfs:zroot/ROOT/default failed with error 22the mountroot freezes and I have to power off to restart.I did not apgrade or any changes since I used it last time.Is it possible to recover my system?Filippo
Problem booting -current via /boot/boot1 from GRUB
My -current box is set up to use GRUB to allow me to either run FreeBSD or Linux. A while back, I added a third option to allow me to boot FreeBSD with a serial console and just happened to make this the default. Once I had this working, I turned just turned the serial console mode on and off by editing /boot/boot.config. The documented way of booting FreeBSD from GRUB is to use the command kernel /boot/loader, but this stage of the boot sequence is too late to enable the serial console mode (because boot.config is read by boot2), so I've been using chainloader /boot/boot1 instead. This had been working fine for months now, but broke sometime in the last week. It looks like the recent changes to boot1 and boot2 are the problem. Now all I get is a register dump followed by a BTX halted message. Booting via the kernel /boot/loader method works fine. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Problem booting current on VAIO R505ES
I got around the lack of IRQ on pcic1 by means of a trick involving hw sets in loader.conf (thanks to the mobile contributors); now it won't mount root. I know what the problem is but not why; the loader brings the kernel in fine, and probes work fine; I'd presume if the partition were too high this would be where the failure would lie. However, the layout is (LBA): The data for partition 1 is: sysid 7,(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) start 63, size 33543657 (16378 Meg), flag 0 beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 33543720, size 8177085 (3992 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 41720805, size 8177085 (3992 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 49897890, size 28242270 (13790 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 --- %disklabel -r ad0s2 # /dev/ad0s2c: type: ESDI disk: ad0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 509 sectors/unit: 8177085 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 1638489 # (Cyl.0 - 65*) b: 1048576 2097152 swap# (Cyl. 130*- 195*) c: 81770850unused0 0 # (Cyl.0 - 508) e: 1048576 10485764.2BSD 2048 1638489 # (Cyl. 65*- 130*) f: 5031357 31457284.2BSD 2048 1638489 # (Cyl. 195*- 508*) %disklabel -r ad0s3 # /dev/ad0s3c: type: ESDI disk: ad0s3 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 509 sectors/unit: 8177085 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 1638489 # (Cyl.0 - 65*) b: 1048576 2097152 swap# (Cyl. 130*- 195*) c: 81770850unused0 0 # (Cyl.0 - 508) e: 1048576 10485764.2BSD 2048 1638489 # (Cyl. 65*- 130*) f: 5031357 31457284.2BSD 2048 1638489 # (Cyl. 195*- 508*) - Note that slice 2 begins JUST below a power of 2 (33554432), and boots fine. Slice 2 has stable on it, slice 3 current, slice 4 == /d and contains home dirs etc. Yes I know, I could make slice 1 smaller. However, I don't know an NTFS version of partition magic. Sony's reinstaller does allow me to make the partition smaller and I suspect I'll have to do this, with a complete reinstall of everything. However, especially on a new system where I might have to deal with the warranty, I like to leave the windoze system alone :-( Now, why is there a mount-root problem at 16mb where the bios limit should end up at 8mb. The bad line is at 2**25? Note that stable (once it is up) gets to all the slices just fine (that is how I've been installing, cross-compiling from -stable). -- Pete To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Problem booting current on VAIO R505ES
Pete Carah wrote: I got around the lack of IRQ on pcic1 by means of a trick involving hw sets in loader.conf (thanks to the mobile contributors); now it won't mount root. I know what the problem is but not why; the loader brings the kernel in fine, and probes work fine; I'd presume if the partition were too high this would be where the failure would lie. However, the layout is (LBA): Doesn't matter. The problem is in the Sony BIOS. I have a PCG-XG29, and a friend has a PCG-XG28, both of which are a precursor to the 505 you have. Specifically, it's an INT 13 implementation limitation. Yes I know, I could make slice 1 smaller. However, I don't know an NTFS version of partition magic. Sony's reinstaller does allow me to make the partition smaller and I suspect I'll have to do this, with a complete reinstall of everything. However, especially on a new system where I might have to deal with the warranty, I like to leave the windoze system alone :-( Partition Magic 7.x supports resizing NTFS partitions. Be aware that you will need to create a minimal (~33M -- God, when did that become minimal?!?) Windows FAT32 partititon, pretending that you are going to install a bootable OS on it, so that the Partition Magic Boot Easy program can locate its files, since the first stage boot loader is not capable of reading non FAT based parititions for loading copies of bootstraps or icons. Search the FreeBSD archives; I wrote up an extensive description of how you have to configure this. Now, why is there a mount-root problem at 16mb where the bios limit should end up at 8mb. The bad line is at 2**25? You mean GB. And -- again -- it's because of the Sony BIOS. Note that stable (once it is up) gets to all the slices just fine (that is how I've been installing, cross-compiling from -stable). Yes; that's how it works. Protected mode drivers don't use the BIOS to access the disk, so they can get anywhere on it. It's because of the Sony BIOS. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
