date:20160214

Re: UEFI & ZFS

2016-02-14 Thread Thomas Laus

> I've observed the slowness only on the local console, I haven't tested
> the seriel console. Put the FreeBSD legcay installation usb stick into
> the box, select it as boot device and watch the cursor spinning for
> about 10 minutens until the kernel boots. Do the same with an UEFI
> installation stick and it's a matter of seconds... 
> 
> I've seen this on an Gigabyte GA-Z170XP-SLI with a Core i7 6700k and on
> two Supermicro X11SBA-LN4F based machines with Skylake Xeon CPUs. There
> are several other reports of slow boot on Skylake CPUs on the net. In
> the thread mentioned below some changes in the hardware, the firmware 
> or somewhere else were suspected. I didn't even try to debug it,instead
> I went with the UEFI loader.
>
Yamagi:

My experience is the same as yours, but only with the combination of Legacy 
BIOS and ZFS installation.  UEFI loading of a ZFS filesystem is also a matter 
of seconds.  So is a Legacy/GPT/UFS installation.  I only see this on my i5 
Skylake when I perform a non-UEFI instalation using the ZFS filesystem.  I 
get a rapid boot with both OpenBSD 5.8 and using a MSDOS 6.22 USB floppy.  I 
have seen some patches posted to this list for testing.  I'll report back 
with my results.  I can't use UEFI because this will be a XEN server and UEFI 
support is not in the XEN kernel yet.

Tom

-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF

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

Re: Is UEFI required for ZFS?

2016-02-14 Thread Mark Dixon

Konstantin Belousov  gmail.com> writes:

 
> On Sat, Feb 13, 2016 at 03:46:16PM +, Mark Dixon wrote:
> Might be, try the following (mostly debugging) change.
> 

Tried it, the only thing I saw different is after the menu I got:

rd eef611d6 

Hope that helps,

Mark







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

Re: UEFI & ZFS

2016-02-14 Thread Yamagi Burmeister

Hello,
I've observed the slowness only on the local console, I haven't tested
the seriel console. Put the FreeBSD legcay installation usb stick into
the box, select it as boot device and watch the cursor spinning for
about 10 minutens until the kernel boots. Do the same with an UEFI
installation stick and it's a matter of seconds... 

I've seen this on an Gigabyte GA-Z170XP-SLI with a Core i7 6700k and on
two Supermicro X11SBA-LN4F based machines with Skylake Xeon CPUs. There
are several other reports of slow boot on Skylake CPUs on the net. In
the thread mentioned below some changes in the hardware, the firmware 
or somewhere else were suspected. I didn't even try to debug it,instead
I went with the UEFI loader.

Regards,
Yamagi

On Sun, 14 Feb 2016 13:47:05 +0200
Daniel Braniss  wrote:

> > On 14 Feb 2016, at 11:52, Yamagi Burmeister  wrote:
> > 
> > https://lists.freebsd.org/pipermail/freebsd-current/2015-December/059037.html

> when saying ‘slow’, do you see slowness when printing output to the screen?
> I mention this, because in the past I saw something similar, and it was a
> misconfiguration with the serial console …
> 
> danny
> 
> > 
> > Regard,
> > 
> > 
> > On Fri, 12 Feb 2016 15:36:10 -0500
> > "Thomas Laus"  wrote:
> > 
> >>> I have a new Asus H170-Plus-D3 motherboard that will be used for a DOM0 
> >>> Xen
> >>> Server.  It uses an Intel i5-6300 processor and a Samsung 840 EVO SSD.  I
> >>> would like to use ZFS on this new installation.  The Xen Kernel does not
> >>> have UEFI support at this time, so I installed FreeBSD CURRENT r295345 in
> >>> 'legacy mode'.  It takes about 7 minutes to go from the first '|' 
> >>> character
> >>> to getting the 'beastie' menu.  I changed the BIOS to UEFI and did another
> >>> installation.  The boot process goes in an instant.
> >> 
> >> Several others have the same problem. See here on the freebsd forums:
> >> 
> >> http://tinyurl.com/z9oldkc
> >> 
> >> That is my exact problem.  It takes 4 minutes to get a complete 'beastie' 
> >> menu and 7 minutes 34 seconds to login.
> >> 
> >> Tom
> >> 
> >> -- 
> >> Public Keys:
> >> PGP KeyID = 0x5F22FDC1
> >> GnuPG KeyID = 0x620836CF
> >> 
> >> ___
> >> freebsd-stable@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> > 
> > 
> > -- 
> > Homepage:  www.yamagi.org
> > XMPP:  yam...@yamagi.org
> > GnuPG/GPG: 0xEFBCCBCB
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 


-- 
Homepage:  www.yamagi.org
XMPP:  yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 10.3 BETA1&2 does not boot on Mac Pro 2008

2016-02-14 Thread claudiu vasadi

Hi,

FreeBSD-11.0-CURRENT-amd64-20160206-r295345-disc1.iso works.

Any chance for the missing bits to be MFC'ed?

On Sun, Feb 14, 2016 at 12:12 PM, Steven Hartland 
wrote:

> On 14/02/2016 00:47, claudiu vasadi wrote:
>
>> Hello all,
>>
>> While trying to boot 10.3 amd64 uefi disk1 BETA1 and BETA2 iso on a Mac
>> Pro
>> 2008, I get the following message:
>>
>> BETA1 -
>>
>> http://s76.photobucket.com/user/da1_27/media/10.3-BETA1_zpswjatgfg2.jpg.html
>>
>> BETA2 -
>>
>> http://s76.photobucket.com/user/da1_27/media/10.3-BETA2_zpsfiedhsks.jpg.html
>>
>> Right after displaying the message I see the Num Lock going off and on and
>> I can hear the optical unit moving the head a couple of times; after that,
>> complete silence.
>>
>> When booting verbose, I get the exact same behavior and message.
>>
>> Ideas?
>>
>
> The next step after that is to display the framebuffer information and
> there is some additional support added in head, 10 only supports graphics
> output protocol but head also supports UGA draw, which from the commit
> message for r287538 seems to indicate this may be required for MAC's.
>
> So if you can you try the latest HEAD snapshot and see if there are any
> difference?
>
> If that fixes it should look to try and MFC those changes too.
>
> Regards
> Steve
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>



-- 
Best regards,
Claudiu Vasadi
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

2016-02-14 Thread Tinker


(Will send any followup from now only to freebsd-scsi@ .)



Did some additional research and found that the disk failure indeed is 
reported in MRSAS' "event log".


So my final question then is, how do you extract it into userland (in 
the absence of an "mfiutil" as the MFI driver has)?




Details below. Thanks.

On 2016-02-14 19:59, Tinker wrote:
[...]

http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/3rd-party/lsi/mrsas/userguide/LSI_MR_SAS_SW_UG.pdf
on page 305, that is section "A.2 Event Messages" - I don't know for
what LGI chip this document is, but, it does not list particular event
message very clearly for when an individual underlying disk would have
broken, I don't even see any event for when a hot spare would be taken
in use!



Wait - this page:

https://www.schirmacher.de/display/Linux/Replace+failed+disk+in+MegaRAID+array

(and also 
http://serverfault.com/questions/485147/drive-is-failing-but-lsi-megaraid-controller-does-not-detect-it 
)


gives an example of how the host system learns about broken disks:


Code: 0x0051 .. Event Description: State change on VD 00/1 from 
OPTIMAL(3) to DEGRADED(2)



Code: 0x0072 .. Event Description: State change on PD 05(e0xfc/s0) 
from ONLINE(18) to FAILED(11)


(unclean disk broken seems to be shown as:)

Code: 0x0071 .. Event Description: Unexpected sense: PD 05(e0xfc/s0) 
Path 443322110300, CDB: 2e 00 3a 38 1b c7 00 00 01 00, Sense: 
b/00/00



And this version of the LSI documentation

http://hwraid.le-vert.net/raw-attachment/wiki/LSIMegaRAIDSAS/megacli_user_guide.pdf

gives a clearer definition of the physical and virtual drive states in 
"1.4.16 Physical Drive States"

and "1.4.17 Virtual Disk States" on pages 1-11 to 1-12.

So as we see, a physical drive breaking would

 * "FAILED" the physical drive

 * "DEGRADED" the Virtual Drive (that is the logical exported drive) 
(from "OPTIMAL")



So then, it was indeed the card's "event log" that contains this info.



Last question then would only be then, *where* FreeBSD's MRSAS driver 
sends its event log?




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

MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

2016-02-14 Thread Tinker

( ** Extremely sorry for crossposting! Was unclear where this RAID 
adapter question belongs, please clarify and I'll keep to one single 
list!

 Posted to all of stable@, scsi@ and fs@ .)


Hi,

When you run one of the MRSAS drives such as a Avatogech LSI MegaRaid 
9361 or 9266, and then eventually one of the physical RaidDrives or a 
CacheCade drives breaks, how is this reported to the FreeBSD host's 
dmesg or syslog?



I don't have the hardware in place so that I would be able to check. On 
the other hand someone among you may have extremely deep experience, in 
particular because this card is so common, so this is why I ask you 
here.


I understand that if at least one underlying copy of the data is 
accessible, the RAID card will optimize all access to that one, so when 
it comes to keeping IO working without interruption, the LSI card does a 
great job.



At some point, an SSD or HDD will break down, either completely (it 
won't connect and its SMART interface says the drive is consumed) or 
more discretely, through taking tons of time for its operations.


My best understanding is that the Raid card automatically will take 
those drives out of use, transparently. Now to the main point:



As admin, it's great to be informed when this happens i.e. an underlying 
physical Raid disk or a CacheCade disk is taken out of use or otherwise 
malfunctions.



Does the MrSas driver output this into the dmesg or syslog somehow?


Reading 
https://svnweb.freebsd.org/base/stable/10/sys/dev/mrsas/mrsas.c?revision=284267=markup 
, the card seems to have an "event log" that the driver downloads from 
the card in plaintext (??), but I don't understand from the sourcecode 
where that information is channeled. And also of course I can't see what 
that event log would contain in those cases.


(The "mfiutil" has a "show events" argument, though mfiutil is only for 
the related "mfi" driver which does not work for both 92XX and 93XX 
cards. Also in this case still I'd be interested to know how it reports 
a broken drive)


http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/3rd-party/lsi/mrsas/userguide/LSI_MR_SAS_SW_UG.pdf 
on page 305, that is section "A.2 Event Messages" - I don't know for 
what LGI chip this document is, but, it does not list particular event 
message very clearly for when an individual underlying disk would have 
broken, I don't even see any event for when a hot spare would be taken 
in use!


You who have the experience, can you clarify please? Thanks :D

Tinker

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

Re: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

2016-02-14 Thread Kurt Jaeger

Hi!

> So my final question then is, how do you extract it into userland (in 
> the absence of an "mfiutil" as the MFI driver has)?

They renamed the util to StorCLI, it looks very similar to the old tw_cli,
and can be downloaded from

http://www.avagotech.com/products/server-storage/raid-controllers/megaraid-sas-9266-8i#downloads

as MR_SAS_StorCLI_1-16-06.zip, unpacking it yields storcli_all_os.zip,
unpacking that yields storcli_all_os/FreeBSD/storcli64.tar,
and finally unpacking that gives

$ file storcli64
storcli64: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically 
linked, for FreeBSD 7.4, stripped

which at least looks like it might work with the MRSAS controller.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 10.3 BETA1&2 does not boot on Mac Pro 2008

2016-02-14 Thread Steven Hartland


On 14/02/2016 00:47, claudiu vasadi wrote:

Hello all,

While trying to boot 10.3 amd64 uefi disk1 BETA1 and BETA2 iso on a Mac Pro
2008, I get the following message:

BETA1 -
http://s76.photobucket.com/user/da1_27/media/10.3-BETA1_zpswjatgfg2.jpg.html

BETA2 -
http://s76.photobucket.com/user/da1_27/media/10.3-BETA2_zpsfiedhsks.jpg.html

Right after displaying the message I see the Num Lock going off and on and
I can hear the optical unit moving the head a couple of times; after that,
complete silence.

When booting verbose, I get the exact same behavior and message.

Ideas?


The next step after that is to display the framebuffer information and 
there is some additional support added in head, 10 only supports 
graphics output protocol but head also supports UGA draw, which from the 
commit message for r287538 seems to indicate this may be required for MAC's.


So if you can you try the latest HEAD snapshot and see if there are any 
difference?


If that fixes it should look to try and MFC those changes too.

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

Re: UEFI & ZFS

2016-02-14 Thread Yamagi Burmeister

Hello,
this is a known problem with Intel Skylake CPUs. Legacy boot os dead
slow, UEFI boot is blazing fast. Have a look at this thread, it contains
some more informations:

https://lists.freebsd.org/pipermail/freebsd-current/2015-December/059037.html

As far as I know now one has found / analyzed the root cause of this
until now.

Regard,


On Fri, 12 Feb 2016 15:36:10 -0500
"Thomas Laus"  wrote:

> > I have a new Asus H170-Plus-D3 motherboard that will be used for a DOM0 Xen
> > Server.  It uses an Intel i5-6300 processor and a Samsung 840 EVO SSD.  I
> > would like to use ZFS on this new installation.  The Xen Kernel does not
> > have UEFI support at this time, so I installed FreeBSD CURRENT r295345 in
> > 'legacy mode'.  It takes about 7 minutes to go from the first '|' character
> > to getting the 'beastie' menu.  I changed the BIOS to UEFI and did another
> > installation.  The boot process goes in an instant.
> 
> Several others have the same problem. See here on the freebsd forums:
> 
> http://tinyurl.com/z9oldkc
> 
> That is my exact problem.  It takes 4 minutes to get a complete 'beastie' 
> menu and 7 minutes 34 seconds to login.
> 
> Tom
> 
> -- 
> Public Keys:
> PGP KeyID = 0x5F22FDC1
> GnuPG KeyID = 0x620836CF
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


-- 
Homepage:  www.yamagi.org
XMPP:  yam...@yamagi.org
GnuPG/GPG: 0xEFBCCBCB
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: UEFI & ZFS

2016-02-14 Thread Daniel Braniss


> On 14 Feb 2016, at 11:52, Yamagi Burmeister  wrote:
> 
> Hello,
> this is a known problem with Intel Skylake CPUs. Legacy boot os dead
> slow, UEFI boot is blazing fast. Have a look at this thread, it contains
> some more informations:
> 
> https://lists.freebsd.org/pipermail/freebsd-current/2015-December/059037.html
> 
> As far as I know now one has found / analyzed the root cause of this
> until now.

when saying ‘slow’, do you see slowness when printing output to the screen?
I mention this, because in the past I saw something similar, and it was a
misconfiguration with the serial console …

danny

> 
> Regard,
> 
> 
> On Fri, 12 Feb 2016 15:36:10 -0500
> "Thomas Laus"  wrote:
> 
>>> I have a new Asus H170-Plus-D3 motherboard that will be used for a DOM0 Xen
>>> Server.  It uses an Intel i5-6300 processor and a Samsung 840 EVO SSD.  I
>>> would like to use ZFS on this new installation.  The Xen Kernel does not
>>> have UEFI support at this time, so I installed FreeBSD CURRENT r295345 in
>>> 'legacy mode'.  It takes about 7 minutes to go from the first '|' character
>>> to getting the 'beastie' menu.  I changed the BIOS to UEFI and did another
>>> installation.  The boot process goes in an instant.
>> 
>> Several others have the same problem. See here on the freebsd forums:
>> 
>> http://tinyurl.com/z9oldkc
>> 
>> That is my exact problem.  It takes 4 minutes to get a complete 'beastie' 
>> menu and 7 minutes 34 seconds to login.
>> 
>> Tom
>> 
>> -- 
>> Public Keys:
>> PGP KeyID = 0x5F22FDC1
>> GnuPG KeyID = 0x620836CF
>> 
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 
> 
> -- 
> Homepage:  www.yamagi.org
> XMPP:  yam...@yamagi.org
> GnuPG/GPG: 0xEFBCCBCB
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

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

Re: UEFI & ZFS

Re: Is UEFI required for ZFS?

Re: UEFI & ZFS

Re: FreeBSD 10.3 BETA1&2 does not boot on Mac Pro 2008

Re: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

Re: MRSAS driver/LSI MegaRaid 92XX-93XX admin question: When one of the Raid's physical drives break, how is it reported in the logs?

Re: FreeBSD 10.3 BETA1&2 does not boot on Mac Pro 2008

Re: UEFI & ZFS

Re: UEFI & ZFS

10 matches

Site Navigation

Mail list logo

Footer information