similar to: Spectacularly disappointing disk throughput

Hello all. I have a supermicro 16 bay box with a LSI 9211-8i card. We use it for temp data storage, and we wanted to try the l4z compression. After updating the source tree to r247839: and doing a make buildworld cycle all works fine. But at boot time we get some warnings. make_dev_physpath_alias: WARNING - Unable to alias gptid/281951f4-a996-11e1-83eb-00259061b51a to enc at

Hi all, Trying to upgrade a system from 9.0-RELEASE to 9.1-PRE from yesterday on my machine (GEOM+ZFS mirror setup on ada[01]p3), the new kernel becomes unable to mount root... The only way to recover is to boot from 9.0 kernel. The disks were already named ada[01] in 9.0, so I suspect nothing there... I tried - disabling AHCI in bios (no change seen) - change cables, check PSU, test disks

Hi, I was trying to rebuild world on a FreeBSD 10 test system, that I had just installed. ZFS root was setup. I let the installation program do all the ZFS setup and configuration. I put root on a 5 disk encrypted raidz array. Besides the installer configuring 5 times the amount of swap space I asked for (asked for 8gb, installer put 8gb on each drive, for 40gb in total.) everything was working

On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have to stop and restart NUT, that is a different story. What

On Mar 31, 2015, at 9:07 AM, Jason Gould <jgould at cddiagnostics.com> wrote: > I missed that snmp-ups set pollfreq to 30 by default. I?d hope that it would set deadtime to an appropriate value as well than, no? Is there a way to query what the settings are or what the defaults are? There is a TODO comment in snmp-ups that mentions doing something similar to usbhid-ups: just poll the

I am running NUT as part of FreeNAS 9.2.0. I have looked through the manuals, but I don't see how to address my issue. The box has 4 NIC's in a LACP LAGG group. It takes a while for LACP to finish, and NUT tries to start before packets are flowing. NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS. If I stop NUT and restart

I have 2 APC UPS systems, one is connected to my ESXi host and the other to my FreeNAS. The battery for the FreeNAS will run out before the battery for the ESXi, so I need ESXi to shutdown first. If I wait until BatteryLow on ESXI, it will be too late as FreeNAS will have already shutdown. How can I change the configuration on ESXI to shutdown after a small delay so that it is done before

I'm trying to create a 500GB lv volume on a 500GB physical volume, but can't: [root at francois-pc ~]# pvscan PV /dev/sdd VG freenas lvm2 [500.00 GB / 500.00 GB free] PV /dev/sdc VG thecus lvm2 [1010.00 GB / 910.00 GB free] PV /dev/mapper/ddf1_RAIDp2 VG VolGroup00 lvm2 [931.25 GB / 0 free] Total: 3 [2.38 TB] / in use: 3 [2.38 TB]

On Sat, 11 Mar 2017 08:18:26 +0100 "Niels Dettenbach \(Syndicat IT & Internet\) via samba" <samba at lists.samba.org> wrote: > Am 11. März 2017 00:04:13 MEZ schrieb Andrew Walker via samba > <samba at lists.samba.org>: > >I don't believe that ZFS on FreeBSD supports acltype=posixacl and > >sa-based > > If you want to see a working samba / zfs

Gabor: note, these HCL reports go to the nut-upsdev list. Begin forwarded message: > From: Gabor Tjong A Hung > Subject: Re: Network UPS Tools - Compatibility List > Date: September 3, 2013 2:18:31 PM EDT > > Sorry, > I just noticed the "If your device isn?t listed" part: > > [HCL] Forza FX-1500LCD supported by blazer_usb > > > [root at freenas] ~#

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root at localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1

Hey guys, :) recently, I installed Cyberpower PR2200ELCDRT2U, however, I have not managed to get this UPS working with FreeNAS 11, yet. According to compatibility list, PR2200 should work fine, when using powerpanel driver: http://networkupstools.org/ddl/Cyber_Power_Systems/ http://networkupstools.org/ddl/Cyber_Power_Systems/PR2200.html However, when trying to establish a connection between

https://bugzilla.mindrot.org/show_bug.cgi?id=3226 Bug ID: 3226 Summary: Feature request: Prempt fingerprint prompt when connecting to new server Product: Portable OpenSSH Version: 8.4p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component:

RPvs> On Tue, 1 Jan 2019 10:35:17 -0800 RPvs> Gregory Sloop via samba <samba at lists.samba.org> wrote: >> I'm working to put up a production FeeeNAS box tied to Samba/AD for >> authentication for users connecting to the FreeNAS share(s). In >> joining FreeNAS to the AD domain, one immediately runs into >> "problems" with TLS/encryption. RPvs>

I am currently NOT using SSL on my Samba domain. While reading "Configuring_LDAP_over_SSL_(LDAPS)_on_a_Samba_AD_DC" and thinking about implementing. I'm having trouble "getting my head" around what certificates go where. Simply put, I am not clear as to generating certificates on the clients and then copy which files to to the server or vice versa? What happens when

I'm working to put up a production FeeeNAS box tied to Samba/AD for authentication for users connecting to the FreeNAS share(s). In joining FreeNAS to the AD domain, one immediately runs into "problems" with TLS/encryption. Samba, in the defaults requires TLS. I could disable TLS security in Samba, but that's probably not a great idea. So, I'll need a key/cert for the

I'm using FreeNAS 9.1, and I've just got an APC Back-UPS CS 500. In theory it's supported by NUT, but the latest released version (2.6.5) doesn't have support for it (the driver reports an error, which is apparently due to an overflow). According to a thread on the mailing list, Back-UPS ES series requires a fix that's in source control, and CS series requires an additional

Hello all, OS name: FreeNAS 9.3 NUT version: 2.7.2 NUT installed method: Bundled with FreenNAS 9.3 Device: EATON 5SC 1000 (http://powerquality.eaton.com/Products-services/Backup-Power-UPS/5SC.aspx?cx=5&wtredirect=www.eaton.com/5SC&GUID=B81251A4-F34E-4373-94B3-B4FB3D0CBCA8) Problem description: This was originally reported as bug to FreeNAS

On Wed, Dec 18, 2019 at 9:52 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 18/12/2019 14:34, Jonathon Reinhart wrote: > > On Wed, Dec 18, 2019 at 9:13 AM Rowland penny via samba > > <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > > > > Problem is, and as I said, Samba 4.3.x is EOL as far as Samba is >

Hello;I just came across NUT, testing FreeNAS/FreeBSD. I?m running at home a APC UPS connected to another computer, running apcupsd. I found out that NUT didn't talk by default to apcupsd, and there was a driver created relatively recently (apcupsd-ups), which filled in that gap. The version I found on my FreeBSD/FreeNAS system seems to imply that there is more to come to that driver (0.04)