Overload? Frequent kernel panic with new, bigger array

16 views
Skip to first unread message

Anders Wallén

unread,
Oct 13, 2014, 12:27:01 PM10/13/14
to zfs-...@googlegroups.com
Greetings, everybody!

Last year, I built a RAIDZ2-array using a Probox 8-bay cabinet (8*2 TB) and a Mac Mini (8 GB Ram). It worked well, but I found that I needed more space, so I tried to scale it up.

So, identical cabinet, but with the newer, bigger 3 TB disks. Should work, right?

Unfortunately not. The Mac gets at least one kernel panic per day. After the automatic reboot, the arrays do not auto-mount; the cabinets themselves have to be powered-cycled, and the Mac then issued a "sudo zpool import -f [array-names]".

Any tips? Suggestions? Ideas?

BelecMartin

unread,
Oct 13, 2014, 1:05:46 PM10/13/14
to zfs-...@googlegroups.com
This has almost always been bad cable, controller, and a drive or two in that order, at least with all the systems/pools I have under my thumbs. 

Jason Belec
Sent from my "It's an iPod, a Phone, and an Internet Device..."
--

---
You received this message because you are subscribed to the Google Groups "zfs-macos" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-macos+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Anders Wallén

unread,
Oct 14, 2014, 2:10:20 PM10/14/14
to zfs-...@googlegroups.com
Interesting. I will try to examine the parts.


I was sure it was a software problem, since it only happens when the new, bigger pool has been mounted for a few hours.

Simon Casady

unread,
Oct 14, 2014, 2:38:33 PM10/14/14
to zfs-...@googlegroups.com
Did the sector size change ? 

On Tue, Oct 14, 2014 at 1:10 PM, Anders Wallén <anders...@mac.com> wrote:
Interesting. I will try to examine the parts.


I was sure it was a software problem, since it only happens when the new, bigger pool has been mounted for a few hours.

--

Jason Belec

unread,
Oct 14, 2014, 3:00:08 PM10/14/14
to zfs-...@googlegroups.com
Nope, betcha it is not software. Come on, daddy needs a new sportscar! 

Went through something similar about a month ago, 2 bad sata cables, 2 bad esata cables and that led to 2 bad drives. An honestly, pretty much every single issue I encounter is due to hardware. This is not the first time something so simple has had me scratching me head raw. Had cables split in half at connection, even power cables, only apparent when everything heats up and stuff sags a bit. PITA. Then I had 2 esata cables I just bought drop scrub speed down to Kb/s rather than 2G/s which really frustrated me until I dug out a couple old ones and zoom back to full speed. I really don't understand how C3PO and R2D2 can run amok with so few issues!

The good news is your data is there! If your using the latest stable ZFS (new stuff) you can really work through issues without as many headaches. Recovered a couple old pools recently, took some work, but I was pleasantly surprised. Yes, I keep such things around for just these kinds of tests. ;)


--
Jason Belec
Sent from my iPad

On Oct 14, 2014, at 2:10 PM, Anders Wallén <anders...@mac.com> wrote:

Interesting. I will try to examine the parts.


I was sure it was a software problem, since it only happens when the new, bigger pool has been mounted for a few hours.

--

Jason Belec

unread,
Oct 14, 2014, 3:00:30 PM10/14/14
to zfs-...@googlegroups.com
That is also a good question....


--
Jason Belec
Sent from my iPad
Reply all
Reply to author
Forward
0 new messages