Can't boot anything after r350387

Question

Can't boot anything after r350387

rqqb opened this issue 5 years ago · 18 comments

System information

FreeBSD	13-CURRENT r350387
Distribution Name
Distribution Version
Linux Kernel
Architecture
ZFS Version	5
SPL Version

Describe the problem you're observing

mountroot fails 'File system not recognised"

Describe how to reproduce the problem

Build/install e.g. r353029
with openzfs-2019061900

Include any warning/errors/backtraces from the system logs

rqqb commented 5 years ago

Yes.

Answer 1 · 2019-10-03T19:34:08.000Z

Your loader.conf should contain openzfs_load=YES as opposed to zfs_load=YES, can you verify that is the case?

Answer 2 · 2019-10-03T22:36:27.000Z

compiled openzfs-kmod after compile the kernel rev r350387 ?

Answer 3 · 2019-10-03T22:38:24.000Z

im beyond 353072 ...... . there are 3000 commits after r350387 and there is new openzfs-kmod on ports

Answer 4 · 2019-10-03T22:39:31.000Z

what kernel version my kernel ends on *48
checkout with uname -aK

Answer 5 · 2019-10-04T10:51:30.000Z

Yes They Are Problems Again I cannot compile openzfs-kmod against -HEAD from today update

Answer 6 · 2019-10-04T10:57:21.000Z

Yes I didn't recompile openzfs-kmod before installing the new kernel, so that's the original issue.

I can't compile current openzfs-kmod against my current system.

Answer 7 · 2019-10-04T10:58:55.000Z

I'll see if I can revert openzfs-kmod to the version I have running.

Answer 8 · 2019-10-04T11:03:29.000Z

/usr/ports/sysutils/openzfs-kmod/work/ZoF-27703da/module/os/freebsd/zfs/zfs_vnops.c:578:13: error: no member named
'wire_count' in 'struct vm_page'; did you mean 'ref_count'?
if (pp->wire_count == 0 && pp->valid == 0 &&
^~~~~~~~~~
ref_count
/usr/src/sys/vm/vm_page.h:213:8: note: 'ref_count' declared here
u_int ref_count; /* page references (A) */
^

this patch fixes this https://gist.githubusercontent.com/javashin/f60238463c20d5c67706a2a3f782b14b/raw/c60617e5cb3b00fd878dffd243b47b35a9c7f8b6/gistfile1.txt

Answer 9 · 2019-10-04T11:21:37.000Z

testing now ...

Answer 10 · 2019-10-04T11:30:19.000Z

Problem Solved uname -aK
FreeBSD hellbox-l440 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r353099M: Fri Oct 4 06:43:34 AST 2019 root@hellbox-l440:/usr/obj/usr/src/amd64.amd64/sys/DIABLO amd64 1300048

boots and works faster because i fetched some @mattmacy new fixes commits + the patch
all fine

Answer 11 · 2019-10-04T11:47:47.000Z

@rqqb compile/install new kernel and install this 2 packages with all the new commits and the patched kmod or patch the openzfs-kmod with gpatch -p1 -i ../patch from the dir work/ZoF*****
after make extract and then make deinstall reinstall clean

2-new-PKGS.zip

unzip inside they are
2 *.txz that can be installed with pkg install

Answer 12 · 2019-10-04T19:40:41.000Z

That panicked, see:

When I'm feeling stronger I'll boot off USB and see if I can roll back to my last good snapshot.

Answer 13 · 2019-10-04T23:39:26.000Z

That panicked, see:

When I'm feeling stronger I'll boot off USB and see if I can roll back to my last good snapshot.

What Did You Do Installed The PKGS ? better try patching because all is working here , well i have some things different i do have clang 9 on base i think you must have 8.0.1 i dont know if this can be an issue.

Answer 14 · 2019-10-11T13:28:13.000Z

@javashin @rqqb Can either of you please test the latest commit on projects/zfsbsd and if that fixes things I'll have the port updated. Thanks in advance.

Answer 15 · 2019-10-12T09:24:50.000Z

@freqlabs Im Rebuilding world because of new clang is going to be faster because i already have clang 9 in base i will compile everything openzfs related :) thanks

Answer 16 · 2019-10-16T13:09:17.000Z

Everything works fine with new commits from master this can be closed .

Answer 17 · 2019-10-16T15:16:24.000Z

Port has been bumped. Closing resolved.