Re: ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

[Romain Dolbeau]

Le lun. 3 sept. 2018 à 20:34, Chris Ross  a écrit :
> :-(  I'm sorry to hear about this.  I'd been happy to think that if I backed
> off of worrying about a mirrored /boot, and just used a RAID1 as you did,

So far I don't even use RAID1 - ZFS is on a single disk, with /dev/sdd1
as the boot partition (ext2) and /dev/sdd2 as the root pool. I'd like
to move to a mirrored /boot (using std linux mdraid) + mirrored zpool,
but I don't want to destroy my non-ZFS install, as the ZFS install
isn't very stable (yet).

I've managed to boot ZFS again the beast, at last. The name of the pool
was no longer in grub.cfg, some packages had been removed at one
point (zfs-dkms among them, so no more module), the console=ttyS0
mask some messages (but allows for a prompt later...),and probably
some other stuff that I forgot. Removal of packages might be related
to the availability of spl-dkms in sid (but not zfs-dkms), which was
incompatible with my version. Not sure what was the original cause
of the problem, as I dist-upgraded the install to today's version
before trying (and succeeding) to boot again.

And more good news - the motherboard I got for cheap on ebay
from Germany works fine, so now I have 8 cores @ 1.4 GHz instead
of 4 @ 1.2 GHz :-)

Cordially,

-- 
Romain Dolbeau

Re: ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

[Chris Ross]

On Sun, Sep 02, 2018 at 10:54:31AM +0200, Romain Dolbeau wrote:
> Any suggestion or idea welcome...
> 
> BTW, did anyone else succeeded in having ZFS root on sparc64?

:-(  I'm sorry to hear about this.  I'd been happy to think that if I backed
off of worrying about a mirrored /boot, and just used a RAID1 as you did, 
that I could follow your example and get it working.

As of now, I haven't tried that though, so I'm behind where you were and even
behind where you are.  I hadn't gotten grub to load from the ZFS root, as
I mentioned in emails a month or so ago.  I have been watching for a newer
installer ISO, and was going to reinstall from scratch the non-ZFS installation
I have on sdd, then try to replicate your success with RAID1 and a ext /boot.

Adrian, or anyone else involved, let us know how getting an updated installer
ISO is going.  And if anyone can help Romain, I'll also be listening intently.

- Chris

ZFS root w/ debian sparc64 (was: Re: Installed kernel crash on T5120)

[Romain Dolbeau]

2018-07-20 23:52 GMT+02:00 Romain Dolbeau :
> I don't think I did anything special beyond
> slightly fixing the grub.cfg by adding the pool name...

Last week-end (25/26 august), I dist-upgraded my ZFS root install...
unfortunately, I haven't been able to boot it since :-(
I got an upgraded kernel (4.17.0-3), but even trying the previous
know-to-work 4.17.0-1 doesn't work. The kernel loads,
but nothing happens once the ZFS module is loaded:

#
(...)
[   32.208115]  sda: sda1 sda3
[   32.208622]  sdb: sdb1 sdb3
[   32.213559]  sdd: sdd1 sdd2 sdd3
[   32.214986] sd 1:0:0:0: [sda] Attached SCSI disk
[   32.215291] sd 1:0:1:0: [sdb] Attached SCSI disk
[   32.218789]  sdc: sdc1 sdc2 sdc3 sdc4
[   32.221383] sd 1:0:3:0: [sdd] Attached SCSI disk
[   32.226143] sd 1:0:2:0: [sdc] Attached SCSI disk
[   32.732787] spl: loading out-of-tree module taints kernel.
[   32.739636] SPL: Loaded module v0.7.9-3
[   32.740222] znvpair: module license 'CDDL' taints kernel.
[   32.740355] Disabling lock debugging due to kernel taint
[   34.986408] ZFS: Loaded module v0.7.9-3, ZFS pool version 5000, ZFS
filesystem version 5
#

ZFS is on sdd2.

The initrd were rebuilt at the time of upgrade, dunno if it matters. I
have tried
upgrading since then (I still can mount the ZFS root from a previous,
non-upgraded, non-ZFS install on sdc),
but it doesn't help.

Any suggestion or idea welcome...

BTW, did anyone else succeeded in having ZFS root on sparc64?

Cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Chris Ross]

On Fri, Jul 20, 2018 at 11:52:19PM +0200, Romain Dolbeau wrote:
> fdisk, force of habits...

lol.  Never would've guessed that was an option.  Well, that looks more like
yours:

Device  Start   End   Sectors   Size Id Type Flags
/dev/sda1   0979964979965 478.5M  1 Boot  
/dev/sda2  979965 286728119 285748155 136.3G 83 Linux native  
/dev/sda3   0 286728119 286728120 136.7G  5 Whole disk

I find it interesting that fdisk shows sda3, but parted does not.  Odd.  The
device does exist in /dev, though, so I guess I believe fdisk.

> I used fdisk and originally set the partition *ID* to unassigned as fdisk
> didn't suggest ZFS. ZFS doesn't seem to care.
> Parted shows a filesystem, not an id (I think).
> fdisk shows the id, not the filesystem.

Right.  As above, mine seems to be id 83.  *shrug*

> Oups sorry red herring - out of habits I always anonymize such files.
> In my installation, the UUID are real values, and I sed'ed them to all-9.

Ahh, great.  That makes sense, thanks for the explanation.

> As for grub - except for the fact my /boot is much smaller (I matched
> the size of the ext4 auto-created partition to the sector), I can't help.
> My first attempt failed - not valid. After trying again, it started working
> and I just had to fix the various issues in configuration and versions
> mentioned in a previous mail. I don't think I did anything special beyond
> slightly fixing the grub.cfg by adding the pool name...

Thanks.  So, I adjusted the UUID I had in my search lines of the menuentry
for booting with ZFS root, as it seemed to be pointing to sdb1 instead of sda1.
But, that just gives me a different problem I think I've also seen before:

error: unable to open
/pci@0/pci@0/pci@1/pci
@0/pci@1/pci@0/usb@0,2/hub@4/device@4/st.
error: unable to open
/pci@0/pci@0/pci@1/pci
@0/pci@1/pci@0/usb@0,2/hub@4/device@4/st.
ERROR: /pci@0: Last Trap: Fast Data Access MMU Miss

{0} ok 

I think I may just throw away what I have now and restart.  I can't immagine
I'll be any worse off, and it might be better starting with a newer base
image than I started with many months ago.  Unfortunately grub is much more
complicated than boot-loaders I've used in the past.  If someone builds a new
sparc64 ISO that I can be sure has the newer grub bits in the installer, I'll
just reload my "normal" image, then try to rebuild the ZFS disks again.

  - Chris

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-20 23:22 GMT+02:00 Chris Ross :
> Interesting.  What tool is showing that?

fdisk, force of habits...

> I have been using parted, which
> shows (for my first ZFS disk):
>
> Number  Start  EndSize   File system  Flags
>  1  0.00B  502MB  502MB  ext2 boot
>  2  502MB  147GB  146GB  zfs
>
> So, other than the different format, I notice:
> 1) I show ZFS where your sdd2 shows "Unassigned"

I used fdisk and originally set the partition *ID* to unassigned as fdisk
didn't suggest ZFS. ZFS doesn't seem to care.
Parted shows a filesystem, not an id (I think).
fdisk shows the id, not the filesystem.

> 2) You have a 'c' whole disk partition, and I don't.  I wonder if that's
>important?

Suns have wanted a full disk partition since the beginning.
Sun labels tend to always have them, just in case.
Not sure if they are used by anything in Linux (I doubt it,
it's probably just an artifact of SunOS behavior).

> 3) You have an "Id" field [in your tools output] that I don't.

partition Id used to be useful, not sure if anything in the kernel
cares anymore. fdisk still offers to set them and still display them -
as said above, I put unassigned by lack of choices. Don't think it
matters much.

> Thanks.  There are a few differences compared to mine, notably that the
> "search" lines in your menuentry have a UUID of all 9's,

Oups sorry red herring - out of habits I always anonymize such files.
In my installation, the UUID are real values, and I sed'ed them to all-9.

> And I have hd0/ahci0 vs your hd3/ahci3, but that is expected.  I
> also see that I'm due a kernel update (my grub.cfg still lists 4.16.0-2),
> but since I'm not getting a kernel loaded at all, that's not my problem.

I had to update the kernel as the 4.16 installed by the installer didn't
have any matching headers to compile ZFS that I could find. 4.17
worked just fine on ext4, and works just fine with ZFS as well, and it
had headers.

> Yeah.  This is about the same as what I've tried, but I'm not even able
> to have grub load from the disk in my case.  I've been thinking about
> booting back to "reinstall the whole thing from CD", since my original
> install was many months ago, but haven't done that yet.

Except for holding the klibc stuff to a working version, you should be able
to just dist-upgrade I suppose. I did in my case to make sure I would have
matching install between ext4 and ZFS during dbootstrap, so I could reuse
the same ZFS/SPL modules without any compatibility issue.

As for grub - except for the fact my /boot is much smaller (I matched
the size of the ext4 auto-created partition to the sector), I can't help.
My first attempt failed - not valid. After trying again, it started working
and I just had to fix the various issues in configuration and versions
mentioned in a previous mail. I don't think I did anything special beyond
slightly fixing the grub.cfg by adding the pool name...

Good luck & cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Chris Ross]

On Fri, Jul 20, 2018 at 08:47:05AM +0200, Romain Dolbeau wrote:
> t5120:~$ dpkg -l '*grub*' | grep ^ii
> ii  grub-common   2.02+dfsg1-4 sparc64  GRand Unified
> Bootloader (common files)
> ii  grub-ieee1275 2.02+dfsg1-4 sparc64  GRand Unified
> Bootloader, version 2 (Open Firmware version)
> ii  grub-ieee1275-bin 2.02+dfsg1-4 sparc64  GRand Unified
> Bootloader, version 2 (Open Firmware binaries)
> ii  grub2-common  2.02+dfsg1-4 sparc64  GRand Unified
> Bootloader (common files for version 2)

Okay, that matches mine.  Thanks.

> > and show me how your disk is labeled/partitioned?
> 
> Device  Start   End   Sectors   Size Id Type   Flags
> /dev/sdd1   0192779192780  94.1M  1 Boot
> /dev/sdd2  192780 286707979 286515200 136.6G  0 Unassigned
> /dev/sdd3   0 286728119 286728120 136.7G  5 Whole disk
> 
> Pool on sdd2, of course.

Interesting.  What tool is showing that?  I have been using parted, which
shows (for my first ZFS disk):

Number  Start  EndSize   File system  Flags
 1  0.00B  502MB  502MB  ext2 boot
 2  502MB  147GB  146GB  zfs

So, other than the different format, I notice:
1) I show ZFS where your sdd2 shows "Unassigned"
2) You have a 'c' whole disk partition, and I don't.  I wonder if that's
   important?
3) You have an "Id" field [in your tools output] that I don't.

> Available on 

Thanks.  There are a few differences compared to mine, notably that the
"search" lines in your menuentry have a UUID of all 9's, and mine has a
UUID.  And I have hd0/ahci0 vs your hd3/ahci3, but that is expected.  I
also see that I'm due a kernel update (my grub.cfg still lists 4.16.0-2),
but since I'm not getting a kernel loaded at all, that's not my problem.

> BTW, when I installed the system, I had the sdd1 /boot mounted on
> /mnt/boot (ZFS root on /mnt).
> 
> After doing "grub-mkconfig -o /boot/grub/grub.cfg" (in chroot) the
> pool name was missing in grub.cfg, only the dataset name was there. I
> added the pool name by hand.
> 
> Then "grub-install --force  --skip-fs-probe /dev/sdd1" (also in chroot).
> 
> Don't remember anything special beyond that ... and a bit of elbow
> grease :-) (several reboots to add the network interface
> configuration, the console, right klibc, ...).

Yeah.  This is about the same as what I've tried, but I'm not even able
to have grub load from the disk in my case.  I've been thinking about 
booting back to "reinstall the whole thing from CD", since my original
install was many months ago, but haven't done that yet.

Adrian, the ISOs I see still are dated mid-May.  Let me know if you may
have time to regenerate those at some point.

Thanks Romain.

 - Chris

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-19 23:51 GMT+02:00 Chris Ross :
> Can you confirm the version of grub that you've used to grub-install onto
> your disk,

t5120:~$ dpkg -l '*grub*' | grep ^ii
ii  grub-common   2.02+dfsg1-4 sparc64  GRand Unified
Bootloader (common files)
ii  grub-ieee1275 2.02+dfsg1-4 sparc64  GRand Unified
Bootloader, version 2 (Open Firmware version)
ii  grub-ieee1275-bin 2.02+dfsg1-4 sparc64  GRand Unified
Bootloader, version 2 (Open Firmware binaries)
ii  grub2-common  2.02+dfsg1-4 sparc64  GRand Unified
Bootloader (common files for version 2)

> and show me how your disk is labeled/partitioned?

Device  Start   End   Sectors   Size Id Type   Flags
/dev/sdd1   0192779192780  94.1M  1 Boot
/dev/sdd2  192780 286707979 286515200 136.6G  0 Unassigned
/dev/sdd3   0 286728119 286728120 136.7G  5 Whole disk

Pool on sdd2, of course.

>  Maybe mail me
> your grub.cfg off-list, so I can see how that compares to the one I'm trying
> to squeeze into the one on my ext disk.

Available on 

> (Side question, can it break things to boot grub and it's config off of one
> /boot, then load root and have it configured to load a different /boot?)

I don't think so but I'm not an expert.

BTW, when I installed the system, I had the sdd1 /boot mounted on
/mnt/boot (ZFS root on /mnt).

After doing "grub-mkconfig -o /boot/grub/grub.cfg" (in chroot) the
pool name was missing in grub.cfg, only the dataset name was there. I
added the pool name by hand.

Then "grub-install --force  --skip-fs-probe /dev/sdd1" (also in chroot).

Don't remember anything special beyond that ... and a bit of elbow
grease :-) (several reboots to add the network interface
configuration, the console, right klibc, ...).

Cordially & good luck,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Chris Ross]

On Wed, Jul 18, 2018 at 07:34:31AM +0200, Romain Dolbeau wrote:
> 2018-07-18 4:29 GMT+02:00 Chris Ross :
> > Interesting to note, thank you.
> 
> If you have a full build of zfs from source, you can try
> "zfs/cmd/raidz_test/raidz_test -B".
> 
> > I wonder why
> > my grub-install onto my sda1 isn't working, and yours onto your sdd1 is.
> 
> Barely so far. After a couple of trials (and adding the boot partition to 
> fstab,
> among other things), I got to the point where I get the grub menu & grub
> load the kernel... then it blows up because "/etc/zfs/zfs-functions" is 
> missing.
> That file is in the Debian packages (zfsutils-linux I think), but is
> not installed
> by the packages created by 'make deb' from git... so I tried rebuilding the
> Debian sources with "debuild', but that blows up with an error about missing
> "usr/lib/dracut" in "debian/tmp"...

Interesting.  I didn't go quite that far to the root, I took the suggetion
of James Clarke on this list [1], and downloaded the debian source packages
for zfs-linux and built those.  I think that may've saved me some of the
complexities that you came across.

I'm glad to see that you got it all running!  Unfortunately, I'm still stuck
with not being able to load grub from sda1 on my host.  It loads from sdd1,
and loads that disks ext4 installation.  But I'm not even getting it loaded
from sda1 where there is a grub.cfg that knows about the ZFS install.

I tried recently to add an entry to the grub.cfg on my ext layout that would
load the kernel and root from my ZFS volume.  But that only gives me:

  Booting a command list

error: unable to open
/pci@0/pci@0/pci@1/pci
@0/pci@1/pci@0/usb@0,2/hub@4/device@4/st.
error: unable to open
/pci@0/pci@0/pci@1/pci
@0/pci@1/pci@0/usb@0,2/hub@4/device@4/st.
ERROR: /pci@0: Last Trap: Fast Data Access MMU Miss

{0} ok 


so I fear I've configured it incorrectly.  Definately not well versed in
grub, and there may well be things outside of the menuentry I added that are
conflicting with what I put in borrowed from the other disks grub-mkconfig
(run when I was setting it all up in chroot)  The working entry run starts with
"Loading Linux 4.16.0-2-sparc64-smp ...", and this starts with "Booting a
command list".  So.  :-/

Can you confirm the version of grub that you've used to grub-install onto
your disk, and show me how your disk is labeled/partitioned?  Maybe mail me
your grub.cfg off-list, so I can see how that compares to the one I'm trying
to squeeze into the one on my ext disk.

(Side question, can it break things to boot grub and it's config off of one
/boot, then load root and have it configured to load a different /boot?)

- Chris





[1] https://lists.debian.org/debian-sparc/2018/05/msg5.html

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-18 16:57 GMT+02:00 John Paul Adrian Glaubitz
:
> Some essential packages like glibc will shortly disrupt the functionality
> of debootstrap. It resumes working once the FTP servers are in sync
> again.

What was weird is that debootstrap kept trying for a -9, while I could
see and download the -10... something must have been cached somewhere
I didn't find.

> I'm sorry, but sometimes things are out of my control. We just need
> more hands.

No proble-m just a warning to other to be careful and always
double-check that kind of stuff before upgrading.
Fortunately, I hadn't upgraded those packages on my ext4 install.

> Did you enable the console on the command line? Try adding "console=ttyS0"
> or whatever the name of the serial console on your SPARC machine is.

That hadn't been needed in ext4, and I had no network so I assumed it
was something else...
But assumption is the mother of all f*ck-ups :-) Turns out I had
forgotten to propagate the network config from the ext4 install this
time, and yes I needed the console parameter :-)

I have mutiuser on the ZFS Root install now :-)

Cordially & thanks for your help,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[John Paul Adrian Glaubitz]

On 07/18/2018 04:57 PM, John Paul Adrian Glaubitz wrote:
>> So I guess the kernel still alive ... (no ping though, and
>> non-responsive console).
> 
> Did you enable the console on the command line? Try adding "console=ttyS0"
> or whatever the name of the serial console on your SPARC machine is.

On the kernel command line, that is.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Installed kernel crash on T5120

[John Paul Adrian Glaubitz]

On 07/18/2018 04:50 PM, Romain Dolbeau wrote:
> debootstrap would then fails, trying to download some packages
> upgraded during the night... after a while and multiple attempts it
> worked. Dunno why.

Some essential packages like glibc will shortly disrupt the functionality
of debootstrap. It resumes working once the FTP servers are in sync
again.

> Still can't boot, as the klibc stuff has been updated from -12+sparc64
> to -13, getting me back to square one. Still had the -12+sparc64 in
> the ext4 install, so downgrade by hand and bypass that problem.

Well, yes, this was very unfortunate. Ben Hutchings updated the klibc
package again before I was able to open a pull request on SALSA to
include the patch to fix the package.

I'm sorry, but sometimes things are out of my control. We just need
more hands.

> At this stage (and probably some stuff I forgot), the new install will
> boot single user :-) But multi-user hangs during start-up after:
> #
> ()
> [  OK  ] Reached target Network is Online.
>  Starting LSB: exim Mail Transport Agent...
> [  OK  ] Started Permit User Sessions.
> [  OK  ] Started Getty on tty1.
> [  OK  ] Reached target Login Prompts.
> [  OK  ] Started LSB: exim Mail Transport Agent.
> [  OK  ] Reached target Multi-User System.
> [  OK  ] Reached target Graphical Interface.
>  Starting Update UTMP about System Runlevel Changes...
> [  OK  ] Started Update UTMP about System Runlevel Changes.
> #
> 
> A few minutes later, I also got:
> 
> #
> [  318.639989] random: crng init done
> [  318.640079] random: 7 urandom warning(s) missed due to ratelimiting
> #
> So I guess the kernel still alive ... (no ping though, and
> non-responsive console).

Did you enable the console on the command line? Try adding "console=ttyS0"
or whatever the name of the serial console on your SPARC machine is.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-18 7:34 GMT+02:00 Romain Dolbeau :
> That's where I am a right now. I'll try to rebuild Debian ZFS in the chroot
> instead of the installed Debian next...

Ended up doing 'mkdir' of the missing directory during build, solved
the problem.

Then the new ZFS, being older, didn't import the pool... so I
recreated the pool from scratch.

debootstrap would then fails, trying to download some packages
upgraded during the night... after a while and multiple attempts it
worked. Dunno why.

So redo everything, but for some reason grube-probe doesn't see ZFS
anymore. And the pool name is missing in grub.cfg, I can fix that by
hand.

Still can't boot, as the klibc stuff has been updated from -12+sparc64
to -13, getting me back to square one. Still had the -12+sparc64 in
the ext4 install, so downgrade by hand and bypass that problem.

At this stage (and probably some stuff I forgot), the new install will
boot single user :-) But multi-user hangs during start-up after:
#
()
[  OK  ] Reached target Network is Online.
 Starting LSB: exim Mail Transport Agent...
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: exim Mail Transport Agent.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
 Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.
#

A few minutes later, I also got:

#
[  318.639989] random: crng init done
[  318.640079] random: 7 urandom warning(s) missed due to ratelimiting
#
So I guess the kernel still alive ... (no ping though, and
non-responsive console).

Cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-18 4:29 GMT+02:00 Chris Ross :
> Interesting to note, thank you.

If you have a full build of zfs from source, you can try
"zfs/cmd/raidz_test/raidz_test -B".

> I wonder why
> my grub-install onto my sda1 isn't working, and yours onto your sdd1 is.

Barely so far. After a couple of trials (and adding the boot partition to fstab,
among other things), I got to the point where I get the grub menu & grub
load the kernel... then it blows up because "/etc/zfs/zfs-functions" is missing.
That file is in the Debian packages (zfsutils-linux I think), but is
not installed
by the packages created by 'make deb' from git... so I tried rebuilding the
Debian sources with "debuild', but that blows up with an error about missing
"usr/lib/dracut" in "debian/tmp"...

That's where I am a right now. I'll try to rebuild Debian ZFS in the chroot
instead of the installed Debian next...

Cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Chris Ross]

On Tue, Jul 17, 2018 at 03:04:18PM +0200, Romain Dolbeau wrote:
> Well I have ZFS up and running from Git - it has become surprisingly
> easy over the years.
> BTW, from the archive, I see you were intent on RAIDZ. I love RAIDZ,
> but after running the raidz benchmark, I strongly advise against
> anything but mirrors on a T5120 :-( The parity algorithms are really
> slow on that CPU. And looking at the VIS(1+2) instruction set, I doubt
> they can be significantly accelerated (VIS is old and lacks the
> required 8 bits operations, it doesn't even get any kind of shifts
> before VIS3). Unless we can somehow leverage the cryptographic stuff
> (the Modular Arithmetic Unit, MUA) ? But I don't see any documentation
> beyond "go through the Solaris driver" :-(

Interesting to note, thank you.  I had been expecting a 3-disk RAIDZ plus
a spare.  But, I'm sure I can readjust to a pair of mirrors instead.  Just
have to think more about which filesystems go on which volume than I had.

> Anyway for the new Debian I'm combining this page
> 
> and this ML with this:
> sudo debootstrap --no-check-gpg sid /mnt
> http://ftp.ports.debian.org/debian-ports
> /mnt is where the ZFS root is mounted (didn't do anywhere near as many
> FS as the wiki suggests).
> 
> ZFS is on /dev/sdd2, with /dev/sdd1 a "boot partition" similar to the
> one debian-installer added on /dev/sdc, as it is apparently required.

Thanks.  I tried to set up my sda that same way, with ZFS on sda2, and a boot
partition on sda1.  The one installed on my /dev/sdd by the installer looks
the same, just with two ext partitions and swap on sdd2, sdd4, and sdd5.  But,
as noted recently, that doesn't work.  Are you installing with the grub-install
that's in grub-common + grub-ieee1275 version 2.02+dfsg1-4 ?  I wonder why
my grub-install onto my sda1 isn't working, and yours onto your sdd1 is.
Can you show me the parted for your sdd?  My sda is:

Model: SEAGATE ST914603SSUN146G (scsi)
Disk /dev/sda: 147GB
Sector size (logical/physical): 512B/512B
Partition Table: sun
Disk Flags: 

Number  Start  EndSize   File system  Flags
 1  0.00B  502MB  502MB  ext2 boot
 2  502MB  147GB  146GB  zfs

Thanks.

- Chris

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-17 5:08 GMT+02:00 Chris Ross :
> I hope that you are able to make progress and that
> I can learn from it as well.  :-)

Well I have ZFS up and running from Git - it has become surprisingly
easy over the years.
BTW, from the archive, I see you were intent on RAIDZ. I love RAIDZ,
but after running the raidz benchmark, I strongly advise against
anything but mirrors on a T5120 :-( The parity algorithms are really
slow on that CPU. And looking at the VIS(1+2) instruction set, I doubt
they can be significantly accelerated (VIS is old and lacks the
required 8 bits operations, it doesn't even get any kind of shifts
before VIS3). Unless we can somehow leverage the cryptographic stuff
(the Modular Arithmetic Unit, MUA) ? But I don't see any documentation
beyond "go through the Solaris driver" :-(

Anyway for the new Debian I'm combining this page

and this ML with this:
sudo debootstrap --no-check-gpg sid /mnt
http://ftp.ports.debian.org/debian-ports
/mnt is where the ZFS root is mounted (didn't do anywhere near as many
FS as the wiki suggests).

ZFS is on /dev/sdd2, with /dev/sdd1 a "boot partition" similar to the
one debian-installer added on /dev/sdc, as it is apparently required.

Cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[Chris Ross]

On Mon, Jul 16, 2018 at 09:32:57PM +0200, Romain Dolbeau wrote:
> Next step - ZFS followed by trying to deboostrap a new install in a ZFS root 
> :-)

Thank you for your email, too.  I have a T5120 that I was able to get ZFS
on, with help from this list.  But I am having GRUB problems myself, as noted
in an email yesterday.  I hope that you are able to make progress and that
I can learn from it as well.  :-)

If you search the list archives for the last few months, you'll see some
of the threads where I was asking about getting ZFS downloaded, built,
installed.  I can't boot into it yet, but in theory have a ZFS system all
installed atm.

   - Chris

Re: Installed kernel crash on T5120

[Romain Dolbeau]

2018-07-16 20:50 GMT+02:00 John Paul Adrian Glaubitz
:
> If you have 2.0.4-12 and not 2.0.4-12+sparc64, your klibc is broken. You
> can either boot into rescue mode, then chroot into the installed system
> and dist-upgrade the machine and then run update-initramfs -k all -u or
> reinstall the machine.

That was it. I had upgraded the system, but not done the
"update-initramfs -k all -u" bit.
After doing that in rescue mode, it booted just fine. Thanks :-)

> I guess that would be possible if we switch the installation media to use
> GRUB instead of SILO as its bootloaders. But this is still an item on my
> evergrowing TODO list.

Not a critical item, but it's a lot easier to find a USB stick than a blank
CD media and a working reader nowadays.

Next step - ZFS followed by trying to deboostrap a new install in a ZFS root :-)

Thanks for your help & cordially,

-- 
Romain Dolbeau

Re: Installed kernel crash on T5120

[John Paul Adrian Glaubitz]

Hi Romain!

On 07/16/2018 08:33 PM, Romain Dolbeau wrote:
> Now grub loads fine, I see the grub menu, pick the default choice, and
> this happen:
> 
> #
> Loading Linux 4.16.0-1-sparc64-smp ...
> Segmentation fault
> /dev/sdc2: clean, 38180/6938624 files, 827057/27744254 blocks
> Segmentation fault
> [   32.916580] run-init[1]: segfault at 38 ip 800106cc (rpc
> 00100500) sp 07feffb02eb1 error 1 in
> klibc-gioU2Ql6Bpp06841ZXKfdH4dunE.so[8000+14000]
> [   32.917090] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x000b
> [   32.917090]
> [   32.917242] CPU: 7 PID: 1 Comm: run-init Not tainted
> 4.16.0-1-sparc64-smp #1 Debian 4.16.5-1
> [   32.917365] Call Trace:
> [   32.917443]  [0046b8a8] panic+0xe8/0x2a0
> [   32.917520]  [00471010] do_exit+0xb50/0xb60
> [   32.917594]  [004710cc] do_group_exit+0x2c/0xe0
> [   32.917651]  [0047d194] get_signal+0x3b4/0x660
> [   32.917710]  [0042dbbc] do_signal+0x3c/0x480
> [   32.917831]  [0042e850] do_notify_resume+0x50/0xa0
> [   32.918110]  [00404b44] __handle_signal+0xc/0x2c
> [   32.919181] Press Stop-A (L1-A) from sun keyboard or send break
> [   32.919181] twice on console to return to the boot prom
> [   32.919398] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x000b
> [   32.919398]
> #
> 
> I probably messed up somewhere, just can't figure out where... any
> help appreciated.
> Already tried upgrading, but no newer kernel is available.

You may have run into a broken klibc-utils/libklibc package. What is
the version of your klibc packages?

root@stadler:~# dpkg -l \*klibc\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version Architecture  
  Description
+++-=-===-===-===
ii  klibc-utils   2.0.4-12+sparc64sparc64   
  small utilities built with klibc for early boot
ii  libklibc  2.0.4-12+sparc64sparc64   
  minimal libc subset for use with initramfs
root@stadler:~#

If you have 2.0.4-12 and not 2.0.4-12+sparc64, your klibc is broken. You
can either boot into rescue mode, then chroot into the installed system
and dist-upgrade the machine and then run update-initramfs -k all -u or
reinstall the machine.

> Related question - Solaris installs fine from a USB stick on this
> beast, is there already support for an USB installer in Debian
> Sparc64? (I've run out of blank media - don't use them that much
> anymore...).

I guess that would be possible if we switch the installation media to use
GRUB instead of SILO as its bootloaders. But this is still an item on my
evergrowing TODO list.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913