similar to: Using NUT to signal an appliance

> I have a disk box from ACNC (Jetstor 416is) that has an UPS port. The manual describes an UPS port: “2. Uninterrupted Power Supply (UPS) Port (APC Smart UPS only) The subsystem may come with an optional UPS port allowing you to connect APC Smart UPS device. Connect the cable from the UPS device to the UPS port located at the rear of the subsystem. This will automatically allow the subsystem

Charles, thank you for the thoughtful and helpful reply! The ACNC box uses an RS232 serial interface for UPS connection. From: Charles Lepple [mailto:clepple at gmail.com] Sent: Friday, May 11, 2018 6:47 PM To: Koundakjian, Matthew @ Engility <Matthew.Koundakjian at Engility.com> Cc: nut-upsuser at alioth-lists.debian.net Subject: Re: Using NUT to signal an appliance EXTERNAL EMAIL --

Gordon Messmer wrote: > On 10/26/2015 08:23 AM, m.roth at 5-cent.us wrote: >> We've got a new RAID (a JetStor), and are trying to >> plug it in. > > When you asked about this three weeks ago, you didn't answer questions > about the model of JetStor product, and the conversation died there. > Could you provide that? I thought I had (unless it bounced, thanks to

Jack Bailey wrote: > On 10/07/15 10:06, John R Pierce wrote: >> On 10/7/2015 8:42 AM, m.roth at 5-cent.us wrote: >>> Got an old HP box with a P800 Smart Array controller. The HP RAID box >>> plugged into it's failing, and we got a new JetStor. Anyone know if we >>> can just plug the JetStor in and set it to passthrough, or if we have >>> to use the

On 10/07/15 10:06, John R Pierce wrote: > On 10/7/2015 8:42 AM, m.roth at 5-cent.us wrote: >> Got an old HP box with a P800 Smart Array controller. The HP RAID >> box >> plugged into it's failing, and we got a new JetStor. Anyone know if we >> can just plug the JetStor in and set it to passthrough, or if we have >> to use the P800's firmware to set up

Hi, folks, Got an old HP box with a P800 Smart Array controller. The HP RAID box plugged into it's failing, and we got a new JetStor. Anyone know if we can just plug the JetStor in and set it to passthrough, or if we have to use the P800's firmware to set up the RAID, or other gotchas? I *think* we could use the RAID boxes firmware to build the RAID, but last resort would be

On 10/7/2015 8:42 AM, m.roth at 5-cent.us wrote: > Got an old HP box with a P800 Smart Array controller. The HP RAID box > plugged into it's failing, and we got a new JetStor. Anyone know if we > can just plug the JetStor in and set it to passthrough, or if we have > to use the P800's firmware to set up the RAID, or other gotchas? > > I*think* we could use the RAID

On 10/7/2015 11:47 AM, Jack Bailey wrote: > On 10/07/15 11:13, m.roth at 5-cent.us wrote: >> Jack Bailey wrote: >> >>>> controller that expects to talk to individual SAS or SATA drives. you >>>> can manage it with hpssacli from centos. >>> I have the P822. It has no JBOD or RAID 0. hpacucli works with CentOS >>> 7.0, but is broken on 7.1

On 10/7/2015 8:42 AM, m.roth at 5-cent.us wrote: > Got an old HP box with a P800 Smart Array controller. The HP RAID box > plugged into it's failing, and we got a new JetStor... I think the FIRST thing you need to determine, WHAT JetStor do you have, and what is its host connection ? All the JetStor boxes I saw in a quick look were Ethernet connected NAS/SAN boxes. -- john

John R Pierce wrote: > On 10/7/2015 8:42 AM, m.roth at 5-cent.us wrote: >> Got an old HP box with a P800 Smart Array controller. The HP RAID >> box >> plugged into it's failing, and we got a new JetStor... > > I think the FIRST thing you need to determine, WHAT JetStor do you have, > and what is its host connection ? All the JetStor boxes I saw in a >

I am in the process of completely overhauling the storage setup here and plan to go to glusterfs. The storage involved is 8x Coraid units, 2x JetStor and a Dell MD3000. The Coraid and JetStor are network connected via ATA over Ethernet & iSCSI. The disks are also being upgraded to 1TB in the process. I do plan to use unify to bring most if not all the storage together. My first

Running CentOS 6.7, on an older HP DL580 G5. We've got a Dell 12-bay RAID box plugged into a PERC H800 (aka LSI Liberator) that we put in the HP, and that works fine. We've got a new RAID (a JetStor), and are trying to plug it in. The layout is that the Dell RAID is dual-pathed DAS. Each PERC has two DAS ports. We've got the Dell RAID in the top port of each PERC. I *thought* I could

Every now and then I get an alert like this one. I have no clue what this "rear" subsystem is, or why madam would be trying to write to its log file. Can anyone enlighten me? thanks in advance! ------------------------- SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (93.9 confidence) suggests

On 10/26/2015 08:23 AM, m.roth at 5-cent.us wrote: > We've got a new RAID (a JetStor), and are trying to > plug it in. When you asked about this three weeks ago, you didn't answer questions about the model of JetStor product, and the conversation died there. Could you provide that?

Hi all! I don't religiously follow everything that pops up in the selinux alerts, but now and then I go back and look at some of them. (I'm on an up to date Centos-7). Today I noted an error that seems to occur during a weekly raid check, from /etc/cron.d. the selinux alert is: SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless.

Hi! I'm getting these frequently. several times I've done the steps listed there to suppress the messages, but I keep getting them. Anyone got a good idea how to deal with this? Thanks in advance! ---------------------------- SELinux is preventing mdadm from 'read, open' accesses on the file /var/log/rear/rear-fcshome.log.lockless. ***** Plugin restorecon (99.5 confidence)

I don't understand what this means, I found it in root's email this morning: To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD WARNING: /usr/lib/grub/x86_64-efi/moddep.lst not found, grub2-mkimage will likely fail. Please install the grub2-efi-x64-modules package to fix this. ERROR: Error occurred during grub2-mkimage of BOOTX64.efi

On 04. mars 2018 03:03, Fred Smith wrote: > Every now and then I get an alert like this one. I have no clue what this > "rear" subsystem is, or why madam would be trying to write to its log > file. ReaR is Relax-and-Recover tool: http://relax-and-recover.org/ It creates a bootable CD/DVD with all backup content to restore your system. > If you want to fix the label. >

Note to admins: Please, read through my whole post this time before deleting it. You will be surprised to find out that I have already tried all solutions detailed in the stickies. If you still think that this topic should be deleted, please be kind enough to notify me why, so that I would know how to proceed about getting help with my problem. Thank you. I have 64-bit OpenSUSE 12.1 and I have

I've got an idea for joint multichannel coding. Here is my idea: My idea is a process for coding 2,3,4 or 5 combined channels, in a compatible way for decoders unable to deal with combined channels. part1: All channels to be coded are summed, each one effected by a coefficient related to its sound power importance for the listener. The sum of all channels is devided by the square root of the