Error during installation.

Status
Not open for further replies.

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9
Hello guys. I am in the process of setting up my first build and for the life of me cannot proceed pass the message below. when booting from the FreeNAS disc.
So far I have performed the following:
- I have updated bios to latest version.
- Toggled disabling/enabling AHCI.
- Tried legacy and EFI boot from the FreeNAS CD
Both times I get the below errors

specs are:
Intel S3420GP
16gb ddr3
4x 1tb drives


Any thoughts?
 

Attachments

  • Image1.jpg
    Image1.jpg
    224.3 KB · Views: 349
  • Image.jpg
    Image.jpg
    133.9 KB · Views: 343
Last edited by a moderator:

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
Please provide the following info...

What version of FreeNAS are you trying to install?
Are you trying to use a RAID controller?
Post the output of dmesg (file can be found at /var/log/dmesg.today and dmesg.yesterday)
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Hello guys. I am in the process of setting up my first build and for the life of me cannot proceed pass the message below. when booting from the Freenas disc.
So far I have performed the following:
- I have updated bios to latest version.
- Toggled disabling/enabling ACHI.
- Tried legacy and efi boot from the Freenas CD
Both times I get the below errors

specs are:
Intel S3420GP
16gb ddr3
4x 1tb drives


Any thoughts?
This is basically the same as your first post: "new build Intel S3420GP"

A friendly reminder from the forum rules:
Do not Post The Same Thing Multiple Times

Do not post the same question or comment in more than one place. Duplicate posts will be deleted by moderators.

That said... Your problem may simply be that your hardware is too old to support FreeBSD 11, the operating system upon which FreeNAS is based. See this thread for details:

https://forums.freenas.org/index.php?threads/acpi-gub2-problems.44834/
 

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
I locked the first thread and pointed here. Just being kind today.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
My apologies. I realized this morning that my original post was in the wrong thread.
Simply ask one of the moderators to move the thread and we will do it if it makes sense.
 

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9
Please provide the following info...

What version of FreeNAS are you trying to install?
Are you trying to use a RAID controller?
Post the output of dmesg (file can be found at /var/log/dmesg.today and dmesg.yesterday)
Trying to install the newest.
No raid controller, onboard SATA
how can I post the output of this if I cant fully load the installer?
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
The first one is a panic while trying to mount an old graid device. That would be due to old motherboard RAID metadata on those disks. Is there data on those disks you want to keep?

The second one makes me think either very old hardware (unlikely with DDR3), or a RAM or power supply problem. But the other thread suggests that was an earlier problem because you had AHCI disabled.
 

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9
The first one is a panic while trying to mount an old graid device. That would be due to old motherboard RAID metadata on those disks. Is there data on those disks you want to keep?

The second one makes me think either very old hardware (unlikely with DDR3), or a RAM or power supply problem. But the other thread suggests that was an earlier problem because you had AHCI disabled.
Thank you for your response.
There is no data on the disks. They were originally from a raid set. I will proceed with wiping tonight before attempting install again
The hardware is an Intel server board manufactured in 2011, so yes, quite old in the PC era.
I ran memtest for 4 iterations, a little over a full day, no errors.
I originally tried the installer with ACHI enabled. I also tried with disabled and yielded similar results. I Really appreciate the input!
Any other suggestions?
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
The first one is a panic while trying to mount an old graid device. That would be due to old motherboard RAID metadata on those disks. Is there data on those disks you want to keep?
You need to teach me how you diagnosed this. I'm sure it's from your years of experience.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
You need to teach me how you diagnosed this. I'm sure it's from your years of experience.
Heh. Experience accumulated while writing this: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-graid.html.

The various forms of motherboard RAID put metadata on each disk. It varies in size and location, but the FreeBSD graid(8) driver recognizes and deals with most of them. When that graid kernel module is loaded, disks with valid motherboard RAID metadata are automatically recognized. That becomes a problem when the RAID is no longer needed. It can even be a problem wiping those disks, because the motherboard BIOS will probably pretend the metadata space does not exist. So... wipe the disk, but the metadata will remain. The right way to do this is to use the motherboard BIOS RAID menus to destroy the RAID. Another method is to connect the disks to something that either does not understand the motherboard RAID, or isn't smart about it. When using FreeBSD, just using a different motherboard is not enough because the graid module recognizes motherboard RAID metadata regardless. Using FreeBSD, unload the graid module before trying to erase these disks.

The GEOM_RAID and g_raid_done messages are what indicated graid was in use.
 
Last edited:

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Thank you for your response.
There is no data on the disks. They were originally from a raid set. I will proceed with wiping tonight before attempting install again
The hardware is an Intel server board manufactured in 2011, so yes, quite old in the PC era.
I ran memtest for 4 iterations, a little over a full day, no errors.
I originally tried the installer with ACHI enabled. I also tried with disabled and yielded similar results. I Really appreciate the input!
Any other suggestions?
Use the motherboard BIOS menus to destroy the old RAID volume, if it was created on that motherboard.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Use the motherboard BIOS menus to destroy the old RAID volume, if it was created on that motherboard.
Alternatively, couldn't he boot Linux/FreeBSD and use dd or badblocks to wipe the disks?
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Linux... don't know. Maybe. FreeBSD, yes, but only if the graid module is not loaded. And wiping the whole disk is excessive. The motherboard BIOS menus are the easiest and put the least wear on the drives. Otherwise, if the motherboard is not protecting the metdata, erasing a megabyte at both the start and end of the drive should be enough.
 

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9
Use the motherboard BIOS menus to destroy the old RAID volume, if it was created on that motherboard.
You sir! most certainly are the man of the day!
So when I get home tonight ill try to format all disks from the motherboard raid utility. Question.
Will fdisk them via a USB - Sata adapter on a windows machine work?
What method do you recomend ?
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
fdisk is pointless, this is not a partitioning thing. Just go into the the motherboard RAID menus and destroy the volume. I would do this with other hard drives disconnected. And of course this must be on the motherboard with that "motherboard RAID" they were created on, or a compatible one.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
If it was Intel fakeRAID, any Intel board with a vaguely non-bottom of the barrel chipset will support it. Anything using an ICH10R Southbridge or a PCH should do.
 

jamatlien

Cadet
Joined
Jul 17, 2017
Messages
9
fdisk is pointless, this is not a partitioning thing. Just go into the the motherboard RAID menus and destroy the volume. I would do this with other hard drives disconnected. And of course this must be on the motherboard with that "motherboard RAID" they were created on, or a compatible one.
Thanks for your help so far!
Update guys, So it turns out I no longer have the board that created the array on these drives. Any other tips as to how I can erase this information?
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Thanks for your help so far!
Update guys, So it turns out I no longer have the board that created the array on these drives. Any other tips as to how I can erase this information?
As I said, try any Intel board from the last 8 years.
 

Spearfoot

He of the long foot
Moderator
Joined
May 13, 2015
Messages
2,478
Thanks for your help so far!
Update guys, So it turns out I no longer have the board that created the array on these drives. Any other tips as to how I can erase this information?
By hook or by crook, you need to wipe the old RAID data from these disks. There are several ways to do this:
  • Ideally (as suggested by @wblock) -- install them on the motherboard you originally used to create the RAID array, then delete the RAID array (and wipe the disks if that is available as an option). You've indicated you no longer have this board...
  • Install them on a motherboard similar to the one you used to create the RAID array, then delete the RAID array, wiping the disks if possible.
  • Use some other means of deleting the RAID data from the disks:
  • 1> Boot FreeBSD or Linux and use either the dd or badblocks command to wipe the disks.
  • 2> Boot the Ultimate Boot CD and use one of the included HDD Disk Wiping tools to wipe the disks.
 
Status
Not open for further replies.
Top