syslogd exits with fatal error [Was Re: newsyslog does not find...]

2019-03-12 Thread Mayuresh
On Tue, Feb 19, 2019 at 08:08:42AM +0530, Mayuresh wrote:
> This is on 8.0_RC1 amd64.
> 
> newsyslog: /var/run/syslogd.pid: No such file or directory
> 

syslogd is sometimes exiting, not sure why, there is no disk space issue,
nothing with heavy use of memory/swap is running.

Last log says:

 localhost syslogd[293]: Fatal error, exiting

I could enable syslogd verbose option as a last resort; but not sure about
when it would trigger next, hence would preferably like to avoid keeping
verbose enabled.

Are there any other known issues why syslogd would exit?

Mayuresh


Re: The state of SAS

2019-03-12 Thread Mike Pumford




On 11/03/2019 15:11, Staffan Thomén wrote:
Flashing sounds dangerous, and I expect I'd need at least a second card 
to get the existing data off my RAID sets unless there are firmwares 
that do both RAID and passthru.


Yes you would lose access to the raid sets managed by the card and would 
have to use raidframe and software raid to get the raid behaviour back 
which would involve reconstructing the filesystems from scratch. If you 
are getting a second card it might be easier to just use that for the 
tape drive and leave the existing working card alone. I also seem to 
recall that there was a way to unbrick a card if something goes wrong 
but my memory could be faulty. Its easy to be blase about this sort of 
thing when the cards you are potentially bricking can be fixed by your 
client if something goes wrong.


Does LSI provide official images or is it a question of someone grabbing 
firmware images of another card that just happens to work?


Last time I looked (which was about 12 months ago) LSI did offer firmwre 
downloads from their website. Its entirely possible that a newer raid 
firmware might allow passthrough of the tape drive so that's also worth 
considering as well. Ultimately with the LSI cards device discovery is 
entirely in the hands of the card firmware (which it then passes to the OS).


Mike


Re: playing with bootxx_ext2fs

2019-03-12 Thread Hauke Fath

On 3/12/19 9:21 AM, pierre-philipp braun wrote:

Please help me understand how installboot is doing its job.  I can try
to take bits from bootxx_ext2fs and push it on the right places onto the
ext2 file-system with dd if/skip of/seek.


I am going out on a limb here, but what installboot does is (1) install 
bootxx_*fs as PBR (mbr partition boot record), and (2) patch the 
location (sector offset, presumably?) of /boot into the PBR code.


I would think this is fs agnostic?

Cheerio,
hauke

--
 The ASCII Ribbon CampaignHauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
 Respect for open standards  Ruf +49-6151-16-21344


Re: MULTIBOOT fails w/ GRUB2 and SYS/EXTLINUX

2019-03-12 Thread Benny Siegert
Correct. But does that matter? IIRC, only the Xen Dom0 kernel is
multiboot-compliant, and even then, it is a multiboot _module_ to be
loaded after the Xen kernel. But I could be wrong.

On Tue, Mar 12, 2019 at 10:58 AM pierre-philipp braun
 wrote:
>
> > knetbsd /netbsd root=/dev/wd0e
>
> Hello Benny.  Yes I've tested it and it works both against netbsd and
> netbsd.gz.  But I believe this is NOT multiboot.



-- 
Benny


Re: MULTIBOOT fails w/ GRUB2 and SYS/EXTLINUX

2019-03-12 Thread pierre-philipp braun
> knetbsd /netbsd root=/dev/wd0e

Hello Benny.  Yes I've tested it and it works both against netbsd and
netbsd.gz.  But I believe this is NOT multiboot.


Re: MULTIBOOT fails w/ GRUB2 and SYS/EXTLINUX

2019-03-12 Thread Benny Siegert
I think that GRUB2 has a special module and command to load NetBSD kernels:

knetbsd /netbsd root=/dev/wd0e


On Tue, Mar 12, 2019 at 10:37 AM pierre-philipp braun
 wrote:
>
> Yolo again
>
> this message closely relates to my two previous ones -- on bootstrapping 
> netbsd from an ext2fs manually -- and I am now  and finally considering 
> MULTIBOOT.
>
> Although I have seen some success reports with GRUB2 *1, all I get is 
> failures.  With GRUB2/multiboot and multiboot2 I get
>
> error: no multiboot header found.
>
> The GRUB2 configurations I tried:
>
> menuentry 'multiboot netbsd' {
> insmod ext2
> set root='(hd0,msdos1)'
> multiboot /netbsd root=/dev/wd0e
> }
>
> menuentry 'multiboot2 netbsd' {
> insmod ext2
> insmod multiboot2
> set root='(hd0,msdos1)'
> multiboot2 /netbsd root=/dev/wd0e
> }
>
> Although it is supposedly the default now, I even tried with a custom kernel 
> (`options MULTIBOOT`).
>
> Note GRUB2 offers some tweaks to workaround things *1.  No change there 
> either.
>
> Now with SYS/EXTLINUX, I get something similar
>
> Invalid Multiboot image: neither ELF header nor a.out kludge found
>
> How get the boot strapping process to load the netbsd kernel fine using 
> multiboot?
>
> I remember I was able to load XEN+NetBSD with the GRUB `kernel` and `module` 
> parameters before, and I believe this was doing MULTIBOOT already.  But maybe 
> that was GRUB legacy.
>
> Thanks
> *1 https://mail-index.netbsd.org/tech-kern/2011/09/13/msg011481.html
> *2 https://www.gnu.org/software/grub/manual/grub/grub.html#multiboot
> --
> Pierre-Philipp Braun
> SNE Russia https://os3.su/



-- 
Benny


MULTIBOOT fails w/ GRUB2 and SYS/EXTLINUX

2019-03-12 Thread pierre-philipp braun
Yolo again

this message closely relates to my two previous ones -- on bootstrapping netbsd 
from an ext2fs manually -- and I am now  and finally considering MULTIBOOT.

Although I have seen some success reports with GRUB2 *1, all I get is failures. 
 With GRUB2/multiboot and multiboot2 I get

error: no multiboot header found.

The GRUB2 configurations I tried:

menuentry 'multiboot netbsd' {
insmod ext2
set root='(hd0,msdos1)'
multiboot /netbsd root=/dev/wd0e
}

menuentry 'multiboot2 netbsd' {
insmod ext2
insmod multiboot2
set root='(hd0,msdos1)'
multiboot2 /netbsd root=/dev/wd0e
}

Although it is supposedly the default now, I even tried with a custom kernel 
(`options MULTIBOOT`).

Note GRUB2 offers some tweaks to workaround things *1.  No change there either.

Now with SYS/EXTLINUX, I get something similar

Invalid Multiboot image: neither ELF header nor a.out kludge found

How get the boot strapping process to load the netbsd kernel fine using 
multiboot?

I remember I was able to load XEN+NetBSD with the GRUB `kernel` and `module` 
parameters before, and I believe this was doing MULTIBOOT already.  But maybe 
that was GRUB legacy.

Thanks
*1 https://mail-index.netbsd.org/tech-kern/2011/09/13/msg011481.html
*2 https://www.gnu.org/software/grub/manual/grub/grub.html#multiboot
-- 
Pierre-Philipp Braun
SNE Russia https://os3.su/