panic: ram_attach on boot

[KeefTM]

Using FreeNAS 9.2.1.5

When I try to boot into FreeNAS from a USB drive I get the following kernel panic:

I've run Memtest86 a few times, no errors found. I've also tried turning off AHCI, safe mode and single user and nothing seems to work. Also, I've tried FreeNAS 8 with the same issue.

Windows 7 ran on this machine fine, so I'm not sure where to go from here.

Thanks

 

[gpsguy]

Please read the forum rules and provide the information in rule #3.

 

[KeefTM]

Sorry about that.

1. FreeNAS version and platform (32 or 64 bit).

FreeNAS 9.2.1.5 64 bit

1. General hardware information (CPU, RAM, Motherboard model, etc.).
2. Specific hardware information (Network card chipset, Raid controller chipset, etc.).

From Windows:
OS NameMicrosoft Windows 7 Professional
Version6.1.7601 Service Pack 1 Build 7601
Other OS DescriptionNot Available
OS ManufacturerMicrosoft Corporation
System NameHTPC-PC
System ManufacturerGigabyte Technology Co., Ltd.
System ModelGA-E7AUM-DS2H
System Typex64-based PC
ProcessorPentium(R) Dual-Core CPU E5200 @ 2.50GHz, 2500 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/DateAward Software International, Inc. F4, 8/26/2009
SMBIOS Version2.4
Installed Physical Memory (RAM)8.00 GB
Total Physical Memory7.75 GB
Available Physical Memory4.95 GB
Total Virtual Memory15.5 GB
Available Virtual Memory12.7 GB
NameNVIDIA GeForce 9400
PNP Device IDPCI\VEN_10DE&DEV_086A&SUBSYS_D0001458&REV_B1\4&2AE66CB3&0&0080
Adapter TypeGeForce 9400, NVIDIA compatible
Adapter DescriptionNVIDIA GeForce 9400
Adapter RAM256.00 MB (268,435,456 bytes)
Installed Driversnvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver Version9.18.13.3165
INF Fileoem25.inf (Section014 section)
Color PlanesNot Available
Color Table Entries4294967296
Resolution1920 x 1080 x 60 hertz
Bits/Pixel32
Memory Address0xED000000-0xEDFFFFFF
Memory Address0xC0000000-0xEFFFFFFF
Memory Address0xDE000000-0xDFFFFFFF
I/O Port0x0000DF00-0x0000DF7F
IRQ ChannelIRQ 23
I/O Port0x000003B0-0x000003BB
I/O Port0x000003C0-0x000003DF
Memory Address0xA0000-0xBFFFF
DescriptionDisk drive
Manufacturer(Standard disk drives)
ModelHitachi HDT721010SLA SCSI Disk Device
Bytes/Sector512
Media LoadedYes
Media TypeFixed hard disk
Partitions5
SCSI Bus0
SCSI Logical Unit0
SCSI Port2
SCSI Target ID0
Sectors/Track63
Size931.51 GB (1,000,202,273,280 bytes)
Total Cylinders121,601
Total Sectors1,953,520,065
Total Tracks31,008,255
Tracks/Cylinder255
PartitionDisk #0, Partition #0
Partition Size39.06 GB (41,940,670,464 bytes)
Partition Starting Offset32,256 bytes
PartitionDisk #0, Partition #1
Partition Size892.44 GB (958,253,345,280 bytes)
Partition Starting Offset41,940,702,720 bytes

DescriptionDisk drive
Manufacturer(Standard disk drives)
ModelWDC WD30 EZRX-00DC0B0 SCSI Disk Device
Bytes/Sector512
Media LoadedYes
Media TypeFixed hard disk
Partitions3
SCSI Bus2
SCSI Logical Unit0
SCSI Port2
SCSI Target ID2
Sectors/Track63
Size2.73 TB (3,000,590,369,280 bytes)
Total Cylinders364,801
Total Sectors5,860,528,065
Total Tracks93,024,255
Tracks/Cylinder255
PartitionDisk #1, Partition #0
Partition Size976.56 GB (1,048,576,000,000 bytes)
Partition Starting Offset135,266,304 bytes
PartitionDisk #1, Partition #1
Partition Size976.56 GB (1,048,576,000,000 bytes)
Partition Starting Offset1,048,711,266,304 bytes
PartitionDisk #1, Partition #2
Partition Size841.27 GB (903,304,183,808 bytes)
Partition Starting Offset2,097,287,266,304 bytes

1. DMESG output or copy of specific error message.
2. IFCONFIG output if you are asking about a NIC or networking problem.
3. PCICONF -lv output if you are asking about MotherBoard and / or PCI card problems.

Can't get that far to print these out. Let me know what more info you need. Thanks!

 

[KeefTM]

Looks like an issue with FreeBSD. I can't get any version of FreeBSD to boot going back to 7. I guess I should bring it up to them as well.

 

[KeefTM]

Gave up on FreeBSD, jumped over to OpenMediaVault, which uses Debian and everything has been fine. Never got FreeBSD to work on a computer that most operating systems have no problem with.

EDIT: I meant this post as disappointment, sorry if it offends

 

[Idiotzoo]

Looks like you have an incompatible system. I've found that Freenas generally works very well without everything being on the approved list, but there's no way to be sure. Sometimes hardware that isn't officially compatible with the underlying version of FreeBSD can work fine, or ok but with some issues but other times you'll get something like this.

You don't mention what the network interface is. I'd wager that's where the problem lies.

That said, I've got a PC sitting on my desk right now that passes every diagnostic test I can throw at it, but won't reliably boot windows. Ubuntu seems to work just fine but I'm not blaming Microsoft. There's definitely something wrong with it.

 

[KeefTM]

I just wish I could figure out what the issue was. I hate not knowing :)

The network card is on the motherboard, Realtek 8211CL chip (10/100/1000 Mbit).

 

[DrKK]

If you look at this:

http://www.gigabyte.com/products/product-page.aspx?pid=2946#sp

It suggests, down there at the notes at the bottom, that there is kind of a wonky chipset on this board. Who ever heard of a board that won't work if you put something in one of the SATA ports but turn off AHCI? Further research turns up:

This looks like it has an Nvidia MCP7A controlling the LAN and SATA. I suspect that this (extremely odd) controller is not supported in FreeBSD, and this is your problem.

 

[Ericloewe]

Well, there's your problem, KeefTM...

This looks like it has an Nvidia MCP7A controlling the LAN and SATA. I suspect that this (extremely odd) controller is not supported in FreeBSD, and this is your problem.

Not only is it extremely old, it never was very good. Hell, I'm amazed a Core 2 Duo will even work with an Nvidia chipset.

 

[Idiotzoo]

Definitely a rare one. I've come across the pairing of Atom CPUs with nvidia chipsets. There was an attempt to use the atom 330 to make a half decent set top box using the nvidia graphics... Actually wasn't too bad to be honest, but I suspect sufficiently rare and consumer for freebsd developers to consider making drivers work.

 

[Ericloewe]

Definitely a rare one. I've come across the pairing of Atom CPUs with nvidia chipsets. There was an attempt to use the atom 330 to make a half decent set top box using the nvidia graphics... Actually wasn't too bad to be honest, but I suspect sufficiently rare and consumer for freebsd developers to consider making drivers work.

Ah, yes, Nvidia Ion (terrible pun...). I can't remember how they did it exactly, but I believe early Atoms simply used an old chipset interface (to keep costs down. Said old chipset had Intel's craptastic GMA950 graphics and consumed more power than the processor...), which Nvidia still had the rights to use.

Well, this here isn't Ion, it's just a regular old Nvidia chipset for Intel LGA775 processors. I don't think I'd ever seen anything as recent as a Core 2 Duo work with an Nvidia chipset...