What chips are on those NiCs? Sent from my iPhone
> On 17 Sep 2014, at 15:18, "Robert Mustacchi via smartos-discuss" > <[email protected]> wrote: > >> On 09/17/2014 05:25 AM, Matthew McKennirey via smartos-discuss wrote: >> I would like to log the USB boot process, in a way that will survive >> the boot failure, to try and figure out why the USB boot is failing. >> >> Suggestions how to best do this will be very welcome. >> >> GRUB displays the boot menu, I select 'no install' (or install, result >> is the same) the SmartOS banner briefly displays, followed by a screen >> of output which goes by too fast to read, then the server reboots, and >> this cycle repeats. About the only thing I can see is 'Warning stack >> not written to the dump buffer' , a number of lines starting acpica, >> then some starting unix. >> >> Before asking for more specific help, how could I capture the output >> of the boot process to a log file on the USB drive which would survive >> the the boot failure, so I could see what is going wrong? >> >> I have tried the USB on a laptop, and while the boot process reports a >> number of various issues related to the laptop hardware, it does >> eventually load SmartOS. I have tried creating the USB twice, I don't >> think there is anything wrong with the USB image, or at least it is a >> faithful representation of what is available for download. It is the >> 20140904 image. >> >> HP DL380 G6, Dual Intel X5550, 48GB RAM, 2 SAS, 6 SATA drives (I have >> tried pulling out all the drives out and running 'no install', same >> result) , >> LSI 9211-8i 6Gb/S PCI-Express 2.0 Controller, no RAID, running as >> JBOD (HP on board controller disabled in BIOS) >> 4 on board NICs, 8 additional NICs on HP PCIe cards >> USB 2 >> >> The machine boots to Linux fine, all hardware recognized by Linux, no issues. >> >> Thanks so much for any advice on capturing the boot process to a log file. > > It sounds like the system is panicking for some reason. There isn't a > great way to capture a log of the boot process, instead you're better > off booting such that when the panic occurs you will trap into the > kernel debugger and you can find out what went wrong. To do that, when > you select your boot option, edit the command line and add a '-k' to it. > > Then you'll end up in the kernel debugger when the panic occurs and > should be able to see what's happened. I'd suggest that instead of > booting to VGA on the DL380, you boot to its serial over lan console so > that way you can actually copy and paste and get a record of what's > happened. > > Is that a useful starting point? > > Robert > > > ------------------------------------------- > smartos-discuss > Archives: https://www.listbox.com/member/archive/184463/=now > RSS Feed: https://www.listbox.com/member/archive/rss/184463/25681568-6afa236a > Modify Your Subscription: https://www.listbox.com/member/?&; > Powered by Listbox: http://www.listbox.com ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
