Everytime I power-up the server I am getting an error...

Status
Not open for further replies.

TapRackPull

Dabbler
Joined
Jul 20, 2011
Messages
48
I have to admit, this freeNAS 8.x thing is getting frustrating. Without regard to how I powerdown the system, using the CLI, the option menu, SSH... WIHTOUT REGARD the system will occassionly hang on boot. This wouldn't be an issue except that when it hangs, it isn't once or twice but will be for hours on end. Then spontaneously self-resolve.

The most common hang-up point is after the initial FREENAS boot screen but before the system becomes stable at the options screen.

Today, the sweet spot seems to be after the following two lines
pcib2: <ACPI PCI-PCI bridge> at de vice 14.0 on pci0
pci2: <ACPI PCI BUS> on pci2

After that nothing... you could wait til the cows come home... I have, they didn't come home... the system is also inaccessible form the GUI.

I need to know how to fix this. My wife is dieing to watch some flicks, we did last night; it was working. Today, I powered down to alter some electrical wiring. When I was finished... well you can guess what I was met with.

Hopefully you gurus can point me in the right direction

Matt
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Matt

After you get a successful boot, go to the command line and do 'dmesg | more'
or, if you want 'dmesg > /mnt/your-pool-name/dmesg.txt'
and post that dmesg.txt file

If you do the first one, look for those 2 lines you posted, and the next 2 or 3 lines after those. That's where it's getting stuck. For me, what comes after those 2 lines is the video controller. Could it be a problem with your display card? is it built in to your motherboard?
 

TapRackPull

Dabbler
Joined
Jul 20, 2011
Messages
48
So, as it stands, I still haven't been able to get it up and running... I will post what you asked for when I get it up again.

Thanks,
Matt
 

TapRackPull

Dabbler
Joined
Jul 20, 2011
Messages
48
So, I attempted dozens of times over the past 24hrs to power up the system. Always arriving at the same hangpoint. You're suggestion that the following lines of code tended to pertain to the video card made me wonder if the PCI slot was dieing, or at least problematic. So I moved the video card and, poof, it came right up. Here is the dmesg.txt code pertaining to the time around the pcib'x' code. Please note that originally, it would hang immeadiatey after the first pci'x' reference just after 'ata...'

Code:
Code:
atapci0: <nVidia nForce MCP55 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 12.0 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
atapci1: <nVidia nForce MCP55 SATA300 controller> port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 23 at device 13.0 on pci0
atapci1: [ITHREAD]
ata2: <ATA channel 0> on atapci1
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci1
ata3: [ITHREAD]
atapci2: <nVidia nForce MCP55 SATA300 controller> port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 20 at device 13.1 on pci0
atapci2: [ITHREAD]
ata4: <ATA channel 0> on atapci2
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci2
ata5: [ITHREAD]
atapci3: <nVidia nForce MCP55 SATA300 controller> port 0xf200-0xf207,0xf100-0xf103,0xf000-0xf007,0xef00-0xef03,0xee00-0xee0f mem 0xfe02b000-0xfe02bfff irq 21 at device 13.2 on pci0
atapci3: [ITHREAD]
ata6: <ATA channel 0> on atapci3
ata6: [ITHREAD]
ata7: <ATA channel 1> on atapci3
ata7: [ITHREAD]
pcib1: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci1: <ACPI PCI bus> on pcib1
re0: <Linksys EG1032 (RTL8169S) Gigabit Ethernet> port 0xdc00-0xdcff mem 0xfdfff000-0xfdfff0ff irq 17 at device 7.0 on pci1
re0: Chip rev. 0x04000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0:  10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Ethernet address: 00:1a:70:13:c9:50
re0: [FILTER]
pci1: <serial bus, FireWire> at device 11.0 (no driver attached)
pci0: <multimedia, HDA> at device 14.1 (no driver attached)
nfe0: <NVIDIA nForce MCP55 Networking Adapter> port 0xed00-0xed07 mem 0xfe02a000-0xfe02afff,0xfe029000-0xfe0290ff,0xfe028000-0xfe02800f irq 23 at device 16.0 on pci0
miibus1: <MII bus> on nfe0
e1000phy0: <Marvell 88E1116 Gigabit PHY> PHY 1 on miibus1
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
nfe0: Ethernet address: 00:1f:c6:3c:49:e1
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe0: [FILTER]
nfe1: <NVIDIA nForce MCP55 Networking Adapter> port 0xec00-0xec07 mem 0xfe027000-0xfe027fff,0xfe026000-0xfe0260ff,0xfe025000-0xfe02500f irq 20 at device 17.0 on pci0
miibus2: <MII bus> on nfe1
e1000phy1: <Marvell 88E1116 Gigabit PHY> PHY 1 on miibus2
e1000phy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
nfe1: Ethernet address: 00:1f:c6:3c:4c:0f
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
nfe1: [FILTER]
pcib2: <ACPI PCI-PCI bridge> at device 22.0 on pci0
pci2: <ACPI PCI bus> on pcib2
siis0: <SiI3132 SATA controller> port 0xcc00-0xcc7f mem 0xfdeff000-0xfdeff07f,0xfdef8000-0xfdefbfff irq 16 at device 0.0 on pci2
siis0: [ITHREAD]
siisch0: <SIIS channel> at channel 0 on siis0
siisch0: [ITHREAD]
siisch1: <SIIS channel> at channel 1 on siis0
siisch1: [ITHREAD]
pcib3: <ACPI PCI-PCI bridge> at device 23.0 on pci0
pci3: <ACPI PCI bus> on pcib3
vgapci0: <VGA-compatible display> port 0xbc00-0xbc7f mem 0xfa000000-0xfaffffff,0xe0000000-0xefffffff,0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci3
amdtemp0: <AMD K8 Thermal Sensors> on hostb3
acpi_tz0: <Thermal Zone> on acpi0
ACPI Warning: For \\_TZ_.THRM._PSL: Return Package type mismatch at index 0 - found [NULL Object Descriptor], expected Reference (20101013/nspredef-1197)
acpi_hpet0: <High Precision Event Timer> iomem 0xfefff000-0xfefff3ff irq 0,8 on acpi0
Timecounter "HPET" frequency 25000000 Hz quality 900
atrtc0: <AT realtime clock> port 0x70-0x73 on acpi0
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FILTER]
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppc0: [ITHREAD]
ppbus0: <Parallel port bus> on ppc0


Any thoughts? Do you think it is the card or PCI slot - or just my misfortune?

For what its worth, I think I am going to create a second boot disk and install .7 on it just to see if I have any of the same issues.
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I'm glad my tip lead you to getting your system back up. It could be several things, the card could have just not been seated correctly, the contacts had some type of 'dirt' on them, a bad solder joint on that connector to the motherboard, problems with the video card. The reason it doesn't hang after the first pci'x' reference anymore is because that can change depending on which slot you use. I would just keep running with 8.x and see if you have anymore problems. My guess is that everything should be ok now.
 

TapRackPull

Dabbler
Joined
Jul 20, 2011
Messages
48
OK, so now that the system is functional, let's move on to another issue I keep banging into. Daily, the system will hang while at random moments, random intervals. The most recent was during a file transfer, the one previous was overnight when there was nothing going on; all client systems were shutdown. Everytime this happens, my router will lock up as well, I loose internet access but retain network access. I tend to believe this is freeNAS and not the router, because:
1- The situation does not occur when the freeNAS system is powered down.
2- Rebooting the router does not work (gain internet access) until I power-off fN and then reboot the router.
3- I previously used a Linksys WRT54GL with tomato firmware that also had the same issue. I was so convinced it was the router finally dieing that I bought a Linksys e4200. Obviously the problem has not resolved.

I have yet to manage to get fN to stay up for a 12hour period.

If there are log files somewhere, I would be happy to post them. I have intentionally left the server down after this most recent bout of issues (last nights file transfer) so that I could preserve any log files that might exist.

Thanks.
 
Status
Not open for further replies.
Top