Re: old snapshot install images?

[Toomas Soome]

just for an update: apparently this was buggy BIOS and the BIOS update did fix 
it. The curious fact was that the gptzfsboot INT13 calls were failing, while 
pmbr INT13 calls were doing OK also the usb stick boot had no apparent problems.

rgds,
toomas


> On 3. mai 2017, at 21:53, Toomas Soome  wrote:
> 
>> 
>> On 3. mai 2017, at 21:23, Michael W. Lucas > > wrote:
>> 
>> On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote:
>>> 
 On 3. mai 2017, at 21:06, Michael W. Lucas  
 wrote:
 
 On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
> There was many issues fixed step by step and some fixes for particular 
> problem did reveal next one (at least in some systems), and indeed, it 
> can cause some problems if you are caught in middle of updates. From my 
> point of view, the most important question is if the current “current” is 
> ok:)
 
 
 Agreed 500%.
 
 The latest snapshot is NOT ok.
 
>>> 
>>> What is the error there?
>> 
>> 
>> error 1
>> error 1
>> gptzfsboot: error 1 lba 4294967288
>> gptzfsboot: error 1 lba 1
>> gptzfsboot: no ZFS pools located, can't boot
>> 
>> My first thought was that the BIOS was looking at a different drive,
>> not the SATADOMs, so I disabled booting from all the spinning drives
>> in the BIOS.
>> 
>> On a related note: my script at http://www-old.michaelwlucas.com/zm.sh 
>>  
>> > >
>> also gives the same error at boot.
>> 
> 
> well, yea, i know what it is. sigh. Welcome to the x86 hell.
> 
> error 1 is: Invalid command. And it is resulting firstly from drvsize() (the 
> lone “error 1” messages) and then from drvread(). Now the question is, did 
> you do the install from usb stick or cd, and has this system booted fbsd from 
> the disk before?
> 
> The question is up because, the boot2 is only using INT13 extended read 
> (INT13 EAX=0x4200) and INT13 EAX=0x4800 to get disk size; if the read is now 
> getting error but was working before, it is pointing towards the error from 
> 0x4800 (drvsize) is triggering the error with read - meaning we should 
> probably attempt the disk reset on error.
> 
> As an first take on possible fix, I think we need to address the drvsize() to 
> get size from INT13 0x800 as biosdisk.c bd_int13probe() does, and reset the 
> disk on error. And if this is not enough, then check further.
> 
> However, since you have the system to test with, the testing is all on you;) 
> So if you are up to the task, poke me in private (mail or irc) and we can 
> work it out - no need to kill the list with all that noise;)
> 
> rgds,
> toomas 
> 
> ___
> freebsd-current@freebsd.org  mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current 
> 
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org 
> "

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Toomas Soome]

> On 3. mai 2017, at 21:53, Toomas Soome  wrote:
> 
> 
>> On 3. mai 2017, at 21:23, Michael W. Lucas > > wrote:
>> 
>> On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote:
>>> 
 On 3. mai 2017, at 21:06, Michael W. Lucas > wrote:
 
 On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
> There was many issues fixed step by step and some fixes for particular 
> problem did reveal next one (at least in some systems), and indeed, it 
> can cause some problems if you are caught in middle of updates. From my 
> point of view, the most important question is if the current “current” is 
> ok:)
 
 
 Agreed 500%.
 
 The latest snapshot is NOT ok.
 
>>> 
>>> What is the error there?
>> 
>> 
>> error 1
>> error 1
>> gptzfsboot: error 1 lba 4294967288
>> gptzfsboot: error 1 lba 1
>> gptzfsboot: no ZFS pools located, can't boot
>> 
>> My first thought was that the BIOS was looking at a different drive,
>> not the SATADOMs, so I disabled booting from all the spinning drives
>> in the BIOS.
>> 
>> On a related note: my script at http://www-old.michaelwlucas.com/zm.sh 
>> 
>> also gives the same error at boot.
>> 
> 
> well, yea, i know what it is. sigh. Welcome to the x86 hell.
> 
> error 1 is: Invalid command. And it is resulting firstly from drvsize() (the 
> lone “error 1” messages) and then from drvread(). Now the question is, did 
> you do the install from usb stick or cd, and has this system booted fbsd from 
> the disk before?
> 
> The question is up because, the boot2 is only using INT13 extended read 
> (INT13 EAX=0x4200) and INT13 EAX=0x4800 to get disk size; if the read is now 
> getting error but was working before, it is pointing towards the error from 
> 0x4800 (drvsize) is triggering the error with read - meaning we should 
> probably attempt the disk reset on error.
> 
> As an first take on possible fix, I think we need to address the drvsize() to 
> get size from INT13 0x800 as biosdisk.c bd_int13probe() does, and reset the 
> disk on error. And if this is not enough, then check further.
> 
> However, since you have the system to test with, the testing is all on you;) 
> So if you are up to the task, poke me in private (mail or irc) and we can 
> work it out - no need to kill the list with all that noise;)
> 
> rgds,
> toomas 
> 

FYI: This is the first take on the issue: https://reviews.freebsd.org/D10591

As this is system specific problem, the testing on that system will be needed 
(wont hurt to test on others as well;) Also it is still very likely we need to 
extend the drvread as well, but lets have small steps here.

rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Toomas Soome]

> On 3. mai 2017, at 21:23, Michael W. Lucas  wrote:
> 
> On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote:
>> 
>>> On 3. mai 2017, at 21:06, Michael W. Lucas  
>>> wrote:
>>> 
>>> On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
 There was many issues fixed step by step and some fixes for particular 
 problem did reveal next one (at least in some systems), and indeed, it can 
 cause some problems if you are caught in middle of updates. From my point 
 of view, the most important question is if the current “current” is ok:)
>>> 
>>> 
>>> Agreed 500%.
>>> 
>>> The latest snapshot is NOT ok.
>>> 
>> 
>> What is the error there?
> 
> 
> error 1
> error 1
> gptzfsboot: error 1 lba 4294967288
> gptzfsboot: error 1 lba 1
> gptzfsboot: no ZFS pools located, can't boot
> 
> My first thought was that the BIOS was looking at a different drive,
> not the SATADOMs, so I disabled booting from all the spinning drives
> in the BIOS.
> 
> On a related note: my script at http://www-old.michaelwlucas.com/zm.sh 
> 
> also gives the same error at boot.
> 

well, yea, i know what it is. sigh. Welcome to the x86 hell.

error 1 is: Invalid command. And it is resulting firstly from drvsize() (the 
lone “error 1” messages) and then from drvread(). Now the question is, did you 
do the install from usb stick or cd, and has this system booted fbsd from the 
disk before?

The question is up because, the boot2 is only using INT13 extended read (INT13 
EAX=0x4200) and INT13 EAX=0x4800 to get disk size; if the read is now getting 
error but was working before, it is pointing towards the error from 0x4800 
(drvsize) is triggering the error with read - meaning we should probably 
attempt the disk reset on error.

As an first take on possible fix, I think we need to address the drvsize() to 
get size from INT13 0x800 as biosdisk.c bd_int13probe() does, and reset the 
disk on error. And if this is not enough, then check further.

However, since you have the system to test with, the testing is all on you;) So 
if you are up to the task, poke me in private (mail or irc) and we can work it 
out - no need to kill the list with all that noise;)

rgds,
toomas 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Michael W. Lucas]

On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote:
> 
> > On 3. mai 2017, at 21:06, Michael W. Lucas  
> > wrote:
> > 
> > On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
> >> There was many issues fixed step by step and some fixes for particular 
> >> problem did reveal next one (at least in some systems), and indeed, it can 
> >> cause some problems if you are caught in middle of updates. From my point 
> >> of view, the most important question is if the current ???current??? is 
> >> ok:)
> > 
> > 
> > Agreed 500%.
> > 
> > The latest snapshot is NOT ok.
> > 
> 
> What is the error there?


error 1
error 1
gptzfsboot: error 1 lba 4294967288
gptzfsboot: error 1 lba 1
gptzfsboot: no ZFS pools located, can't boot

My first thought was that the BIOS was looking at a different drive,
not the SATADOMs, so I disabled booting from all the spinning drives
in the BIOS.

On a related note: my script at http://www-old.michaelwlucas.com/zm.sh
also gives the same error at boot.

-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Toomas Soome]

> On 3. mai 2017, at 21:06, Michael W. Lucas  wrote:
> 
> On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
>> There was many issues fixed step by step and some fixes for particular 
>> problem did reveal next one (at least in some systems), and indeed, it can 
>> cause some problems if you are caught in middle of updates. From my point of 
>> view, the most important question is if the current “current” is ok:)
> 
> 
> Agreed 500%.
> 
> The latest snapshot is NOT ok.
> 

What is the error there?

rgds,
toomas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Michael W. Lucas]

On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote:
> There was many issues fixed step by step and some fixes for particular 
> problem did reveal next one (at least in some systems), and indeed, it can 
> cause some problems if you are caught in middle of updates. From my point of 
> view, the most important question is if the current ???current??? is ok:)


Agreed 500%.

The latest snapshot is NOT ok.

==ml

-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Toomas Soome]

> On 3. mai 2017, at 19:52, Ngie Cooper  wrote:
> 
> 
>> On May 3, 2017, at 09:41, Michael W. Lucas  wrote:
>> 
>>> On Wed, May 03, 2017 at 09:37:04AM -0700, Ngie Cooper (yaneurabeya) wrote:
>>> Ok. I was curious because there has been a period of time when 512b/sector 
>>> disks have been broken and vice versa.
>>> 
>>> I’m going to operate under the impression that one of tsoome’s recent 
>>> changes to zfsboot fixed things (there was some breakage over the past 
>>> couple months based on posts to current@ and svn-src-*@), but I can’t count 
>>> on it 100%.
>> 
>> 
>> The most recent installer snapshot has the exact same problem.
>> 
>> Every installer snapshot on the FTP site has the exact same problem.
>> 
>> I've gotten some installer snapshots from October and from
>> mid-2015. Trying those.
>> 
>> My goal is to find out when the problem appeared and include the time
>> window in the PR.
> 
> Ok. How big is your freebsd-boot partition?
> Thanks,
> -Ngie


There was many issues fixed step by step and some fixes for particular problem 
did reveal next one (at least in some systems), and indeed, it can cause some 
problems if you are caught in middle of updates. From my point of view, the 
most important question is if the current “current” is ok:)

rgds,
toomas
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Ngie Cooper (yaneurabeya)]

> On May 3, 2017, at 10:39, Michael W. Lucas  wrote:
> 
> On Wed, May 03, 2017 at 09:52:09AM -0700, Ngie Cooper wrote:
>> Ok. How big is your freebsd-boot partition?
> 
> The size created by the installer. ;)
> 
> I've run another install, this one with the r317181 snapshot (20
> April.)
> 
> gpart show ada4 shows this (hand-copied)
> 
> 40   125045344ada4  GPT (60G)
> 40   1024 1 freebsd-boot (512K)
> 1064 984- free - (492K)
> 2048 4194304  2 freebsd-swap (2.0G)
> 4196352  1208483843 freebsd-zfs (58G)
> 125044736  648  - free - (324K)
> 
> ada5 is identical. It's a two-satadom mirror.
> 
> I used the guided install, had it blow the disks away.

Ok. You aren’t afflicted by the “freebsd-boot” partition is too small issue 
that many legacy users will have to suffer with coming from 8.x/9.x.
Cheers!
-Ngie


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: old snapshot install images?

[Michael W. Lucas]

On Wed, May 03, 2017 at 09:52:09AM -0700, Ngie Cooper wrote:
> Ok. How big is your freebsd-boot partition?

The size created by the installer. ;)

I've run another install, this one with the r317181 snapshot (20
April.)

gpart show ada4 shows this (hand-copied)

40 125045344ada4  GPT (60G)
40 1024 1 freebsd-boot (512K)
1064   984- free - (492K)
2048   4194304  2 freebsd-swap (2.0G)
41963521208483843 freebsd-zfs (58G)
125044736  648- free - (324K)

ada5 is identical. It's a two-satadom mirror.

I used the guided install, had it blow the disks away.


==ml

-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Ngie Cooper]

> On May 3, 2017, at 09:41, Michael W. Lucas  wrote:
> 
>> On Wed, May 03, 2017 at 09:37:04AM -0700, Ngie Cooper (yaneurabeya) wrote:
>> Ok. I was curious because there has been a period of time when 512b/sector 
>> disks have been broken and vice versa.
>> 
>> I’m going to operate under the impression that one of tsoome’s recent 
>> changes to zfsboot fixed things (there was some breakage over the past 
>> couple months based on posts to current@ and svn-src-*@), but I can’t count 
>> on it 100%.
> 
> 
> The most recent installer snapshot has the exact same problem.
> 
> Every installer snapshot on the FTP site has the exact same problem.
> 
> I've gotten some installer snapshots from October and from
> mid-2015. Trying those.
> 
> My goal is to find out when the problem appeared and include the time
> window in the PR.

Ok. How big is your freebsd-boot partition?
Thanks,
-Ngie
> 
> 
> -- 
> Michael W. LucasTwitter @mwlauthor 
> nonfiction: https://www.michaelwlucas.com/
> fiction: https://www.michaelwarrenlucas.com/
> blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Michael W. Lucas]

On Wed, May 03, 2017 at 09:37:04AM -0700, Ngie Cooper (yaneurabeya) wrote:
> Ok. I was curious because there has been a period of time when 512b/sector 
> disks have been broken and vice versa.
> 
> I???m going to operate under the impression that one of tsoome???s recent 
> changes to zfsboot fixed things (there was some breakage over the past couple 
> months based on posts to current@ and svn-src-*@), but I can???t count on it 
> 100%.


The most recent installer snapshot has the exact same problem.

Every installer snapshot on the FTP site has the exact same problem.

I've gotten some installer snapshots from October and from
mid-2015. Trying those.

My goal is to find out when the problem appeared and include the time
window in the PR.

==ml




-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Ngie Cooper (yaneurabeya)]

> On May 3, 2017, at 09:34, Michael W. Lucas  wrote:
> 
> On Wed, May 03, 2017 at 01:01:10AM -0700, Ngie Cooper wrote:
>> Hi Michael!
>> - What sources are you using/revision are you at?
> 
> Using r311461 amd64 install memstick at the moment. Uname says built
> "Thu Jan 5 22:46:38 UTC 2017”

Ok. What version were you going to?

>> - Are your drives the 512 byte/sector or 4kB/sector variety?
> 
> They all claim to be 512 byte/sector. FWIW. ;-)

Ok. I was curious because there has been a period of time when 512b/sector 
disks have been broken and vice versa.

I’m going to operate under the impression that one of tsoome’s recent changes 
to zfsboot fixed things (there was some breakage over the past couple months 
based on posts to current@ and svn-src-*@), but I can’t count on it 100%.

HTH,
-Ngie


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: old snapshot install images?

[Michael W. Lucas]

On Wed, May 03, 2017 at 01:01:10AM -0700, Ngie Cooper wrote:
> Hi Michael!
> - What sources are you using/revision are you at?

Using r311461 amd64 install memstick at the moment. Uname says built
"Thu Jan 5 22:46:38 UTC 2017"

> - Are your drives the 512 byte/sector or 4kB/sector variety?

They all claim to be 512 byte/sector. FWIW. ;-)


==ml

-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: old snapshot install images?

[Ngie Cooper]

Hi Michael!

> On May 2, 2017, at 12:15, Michael W. Lucas  wrote:
> 
> Hi,
> 
> About a year ago, I did a clean install on my desktop. No problems.
> 
> I tried a clean install now, and it dies with:
> 
> gtpzfsboot: error 1 lba 32
> error 1
> gptzfsboot: error 1 lba 4294967288
> gptzfsboot: error 1 lba 1
> gptzfsboot: no ZFS pools located, can't boot
> 
> The pool is visible in the live CD, and I can import it. I want to
> file a PR.
> 
> The sensible thing for me to do is to use old snapshot installers to
> determine when this machine could no longer install.
> 
> Unfortunately, the FTP servers only keep a month or so of snapshots.
> 
> ftp-archive doesn't have the old snapshots.
> 
> Does anyone have an archive of -current install media, either CD or
> ISO? I need to get this box back fairly quickly, but I don't mind
> burning a couple days to nail it down.

- What sources are you using/revision are you at?
- Are your drives the 512 byte/sector or 4kB/sector variety?
Thanks,
-Ngie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

old snapshot install images?

[Michael W. Lucas]

Hi,

About a year ago, I did a clean install on my desktop. No problems.

I tried a clean install now, and it dies with:

gtpzfsboot: error 1 lba 32
error 1
gptzfsboot: error 1 lba 4294967288
gptzfsboot: error 1 lba 1
gptzfsboot: no ZFS pools located, can't boot

The pool is visible in the live CD, and I can import it. I want to
file a PR.

The sensible thing for me to do is to use old snapshot installers to
determine when this machine could no longer install.

Unfortunately, the FTP servers only keep a month or so of snapshots.

ftp-archive doesn't have the old snapshots.

Does anyone have an archive of -current install media, either CD or
ISO? I need to get this box back fairly quickly, but I don't mind
burning a couple days to nail it down.

Thanks,
==ml

-- 
Michael W. LucasTwitter @mwlauthor 
nonfiction: https://www.michaelwlucas.com/
fiction: https://www.michaelwarrenlucas.com/
blog: http://blather.michaelwlucas.com/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"