Recent content by Eschertias

Welp, just got my RMA processed, they're dropping a new one in the mail. I'll take some post-mortem pictures of the inside of mine when I crack it open in a bit. Edit: Looks like massive coolant boil off and some chunky crud that build up in the microchannels. Also the copper is pretty badly...

At some point I'm gonna just do a custom loop for it, possibly when TR 3 hits using the new CCX cores on the 7nm process. In the interim, I'll just put a Noctua on it and dial way back on the OC. Shame such a nice performing part has such a hilariously awful failure mode.

So I'm seeing the same issues. My problem was this was a virtualization box in a rack. So the only thing I noticed was the machine randomly shutting off. After an afternoon of memtest and two more mystery shutoffs, I cracked the thing open and started it up on my test bench, and the FLIR...

So I learned about an interesting error, if you manually make a COMSTAR LU and set the blocksize to 4096 using a zfs volume block device as the storage target, the backing storage takes about 1.5-2x as much as you'd expect. Which will run the pool to 0 bytes free and break all kinds of fun stuff.

I have an X520 in my OmniOS setup, and it works pretty well. No complaints whatsoever. I did run into a really fun bug setting up my new 8TB HDDs with napp-it. Running parted -lm to list the disks out would hang and never complete. Using the disk initialize step wouldn't work either...

NFS by default uses sync writes, there should be an option to disable them to test if that's the case. If you still want sync writes, get a flash based disk and use it as the pool's ZIL. But if I destroyed both pools and recreated them as one big pool with 2 vdevs, I would avoid the...

Question time! I have a series of questions regarding my home brew OmniOS Hobo-SAN that I'd like help with. Most helpful set of answers, or really in depth answers get an Amazon gift card. Background Info: My current setup is an OmniOS install on a whitebox supermicro storage chassis, LSI...

The fact that you void any warranty you may be able to get from the drive manufacturer? Having drives with a 5 year 'It broke, take it back' warranty makes it really easy to avoid dealing with issues when one of the drives takes a dump in year 3.

Well yeah, but a drive with SLC flash attached to a shitty ADATA controller from the very first consumer SSDs will probably fail a lot faster than a drive with TLC attached to a top of the line modern controller. There are a lot more moving parts on an SSD than just flash size and flash...

That would probably be the for the best. ZFS list -p gives raw byte values, so the volume creation stuff, silly regex issue aside, works fine. I think the bug may be someplace in the COMSTAR volume LU detection and size conversion code. It autodetects the volumes just fine, but doesn't...

I paid _Gea for a pro license, because the fancy monitoring applets are way easier on the eyes than iostat -xen 15. He did good work for a long assed time for free, and I figured the ease of use was worth the ~150 euros I paid him for his dev time. The fact that there are odd interactions...

I had those same issues, and it turned out to be a 5 year old flaky WD Green drive that was causing the issues. Moved the data to a new set of drives, removed the old ones and the system was just fine.

_Gea: I have a pretty obnoxious issue I've discovered in the Disk Volume/COMSTAR volume LU creation systems. When you create a disk volume and specify a size, it ignores "." in the input field. 13.6 TB turns into 136 TB. EDIT: The second issue is that the sizing of the zfs Volume and...

After looking to exactly how I had the iSCSI LU set up, I finally noticed that the ZFS file system that was housing the thin provisioned file had hit 0 bytes free. So yeah, that was what was causing the entire system to completely lose it's mind. I blew away the entire zpool it was stored on...

This is the kind of busy that causes the windows VM to disconnect the disk because IOs hung for over 30 seconds. A month ago this didn't happen, which makes me think that it may have been caused by my last update. I'm trying to sync files between the pool and the COMSTAR iscsi volume, and it...