Project

General

Profile

Bug #54231

Panic on fresh install during boot

Added by Tony Scicchitano about 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
No priority
Assignee:
Ryan Moeller
Category:
OS
Target version:
Seen in:
Severity:
Low
Reason for Closing:
User Configuration Error
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Decided to give RC1 a go after some issues with early betas. It seems the boot loader now works and I can install successfully. But on reboot I get this:

BTX loader 1.00 BTX version is 1.02
Consoles: internal video/keyboard
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS drive D: is disk2
BIOS drive E: is disk3
BIOS drive F: is disk4
BIOS drive G: is disk5
BIOS drive H: is disk6
BIOS drive I: is disk7
panic: free: guard1 fail @ 0xb85bbcce from unknown:0
—> Press a key on the console to reboot <—

2ED1758C-5872-415A-BB68-3CD95956CF92.jpeg (4.03 MB) 2ED1758C-5872-415A-BB68-3CD95956CF92.jpeg Tony Scicchitano, 11/05/2018 05:02 PM
Screen Shot 2018-11-28 at 9.35.29 AM.png (5.83 MB) Screen Shot 2018-11-28 at 9.35.29 AM.png BTX halted with a Seagate Expansion drive attached Ryan Moeller, 11/28/2018 09:36 AM
39222
42570

History

#1 Updated by Dru Lavigne about 1 year ago

  • Status changed from Unscreened to Blocked
  • Private changed from No to Yes
  • Reason for Blocked set to Need additional information from Author

Tony: to assist the dev in determining which piece of hardware is the issue, please install 11.1-U6, create a debug (System -> Advanced -> Save debug), and attach it to this ticket.

#2 Updated by Tony Scicchitano about 1 year ago

  • File debug-iserve-20181027174554.tgz added

Attached debug.

#3 Updated by Dru Lavigne about 1 year ago

  • Status changed from Blocked to Unscreened
  • Assignee changed from Release Council to Alexander Motin
  • Reason for Blocked deleted (Need additional information from Author)

#4 Updated by Alexander Motin about 1 year ago

  • Assignee changed from Alexander Motin to Ryan Moeller

#5 Updated by Ryan Moeller about 1 year ago

  • Status changed from Unscreened to Blocked
  • Severity changed from New to Low
  • Reason for Blocked set to Need additional information from Author

Hi again, Tony. :)
As you may remember, I have a similar system I use for testing (older Asus mobo, AMI legacy BIOS, FX processor). After fixing the installer bootloader issue, I have not encountered this problem booting an installed system, so I suspect this may be related to some specific hardware or configuration difference.

Please answer a few more questions about your configuration:
Is your SATA controller configured in AHCI mode (not RAID)? I would guess this is correctly in AHCI mode, since you appear to have an existing install of a previous version of FreeNAS working, but it doesn't hurt to be sure.
It looks like your motherboard has 6 SATA ports, but I see 8 disks enumerated. I see in dmesg you have all six SATA ports attached to disks for storage. One of the other disks must be the USB disk you are booting from. Is the last remaining disk the old FreeNAS install? Have you tried without that attached as well? If unplugging that turns out to help, it will give me something to look for so I can determine a fix.

I'm also curious if you have the same problem with a vanilla FreeBSD installation on a USB drive. If you can, try booting both FreeBSD 11.2 and one of the recent FreeBSD 12 memstick images. There have been various changes to the bootloader between 11 and 12, so it may be the case that a fix already exists but hasn't been backported.

Thanks!

#6 Updated by Tony Scicchitano about 1 year ago

Hi Ryan,

I have 6 internal SATA drives (non-raid), one of which is a small SSD with 11.1-U6 on it (which should ultimately be upgraded to 11.2). I also have an external USB drive (Seagate 4 TB - P/N 1TEAPF-500), and the USB thumb drive I have 11.2-RC1 installed on.

It seems if I disconnect the external USB drive (Seagate 4TB), I can boot into 11.2-RC1 without issues. I can try to install FreeBSD 11.2 or 12 on the weekend if you think it will help. I’m assuming I can install it on a spare USB thumb drive?

Tony

#7 Updated by Ryan Moeller about 1 year ago

OK I had a hunch that the USB enclosure might be the problem. I saw some revamped disk detection code just land in FreeBSD, so if you can try 11.2 versus a development snapshot of 13-current, with the USB enclosure attached, we will see if the fix is in the new code already. You can write a FreeBSD memstick IMG to a USB stick without needing to install, and I think it will test the code in question.

#8 Updated by Tony Scicchitano about 1 year ago

Hi Ryan,

FreeBSD 11.2 has no problems booting with the USB external attached. FreeBSD 13-current does not boot (panic error).

Looks like new code isn’t as robust?

Thanks,
Tony

#9 Updated by Dru Lavigne about 1 year ago

  • Status changed from Blocked to Unscreened
  • Reason for Blocked deleted (Need additional information from Author)

#10 Updated by Ryan Moeller about 1 year ago

  • Status changed from Unscreened to Screened

Wow that is exactly the opposite of what I expected. Very strange. I will have to take a closer look at how our installed system might differ from the FreeBSD 11.2 memstick image. Thanks.

#11 Updated by Tony Scicchitano about 1 year ago

39222

As a sanity check (and in case I mixed up the USB drives), I repeated the attempts and got the same results. I’ve attached a snapshot of the successful FreeBSD 11.2 screen showing version. For what it’s worth, 13-current boots up fine only if I disconnect the external USB drive prior to booting.

#12 Updated by Tony Scicchitano 12 months ago

Any luck? I’m really eager to get on the 11.2 train.

Would a debug be useful if I install the RC with the external disconnected, then reconnect it when it’s up?

#13 Updated by Ryan Moeller 12 months ago

  • Status changed from Screened to Blocked
  • Reason for Blocked set to On hold

This is a difficult problem because the problem seems to be a quirk of this external drive, and I haven't had one to play with to figure out what exactly the quirk is and how to deal with it. There's nothing I was able to spot by just looking at the code.

There seem to be other cases of Seagate external USB enclosures hanging up the boot, so I do recognize that this is still an issue, but for now you should be able to boot without the drive attached and just plug it in once you hit the loader menu as a workaround. I do want to revisit this soon because I have a few ideas I would like to try, and I just got my hands on a broken Seagate external drive that I will attempt to repair and see if the same issue presents.

I hope you will understand that I have higher severity issues to work on and easier problems to solve in the meantime, as well. I'm marking this issue as "on hold" until I am able to work with the hardware I obtained.

#14 Updated by Tony Scicchitano 12 months ago

No worries. I’ll make due. I might even have an alternate external drive.

#15 Updated by Ryan Moeller 12 months ago

  • File IMG_1240.HEIC added

I tested booting FreeNAS 11.2-RC2 with the drive I obtained attached, and indeed I got BTX to halt. This doesn't exactly match the error you described, but it gives me a starting point to investigate from.

#16 Updated by Ryan Moeller 12 months ago

  • File deleted (IMG_1240.HEIC)

#18 Updated by Tony Scicchitano 12 months ago

Upgraded to 11.2 release and it appears grub is still the default boot loader? I’m confused, but happily running 11.2 with the external USB installed with no (obviously apparent) issues.

#19 Updated by Tony Scicchitano 12 months ago

On second boot it seemed to switch to BTX and the problem reappeared.

The good news is that I disabled legacy USB support in the motherboard BIOS and my boot failures disappeared.

#20 Updated by Ryan Moeller 10 months ago

  • Status changed from Blocked to Closed
  • Reason for Closing set to User Configuration Error
  • Reason for Blocked deleted (On hold)

The upgrade process installs the new bootloader after the first reboot. That is why it booted once with grub.

Thank you for letting us know the configuration change that helped!

#21 Updated by Dru Lavigne 10 months ago

  • File deleted (debug-iserve-20181027174554.tgz)

#22 Updated by Dru Lavigne 10 months ago

  • Target version changed from Backlog to N/A
  • Private changed from Yes to No

Also available in: Atom PDF