similar to: systutils/arcconf errors on 9.x versions

Hey folks, I have a Sun J4400 SAS1 disk array with 24 x 1T drives in it connected to a Sunfire x2250 running 5.8 ( 64 bit ) I used 'arcconf' to create a big RAID60 out of (see below). But then I mount it and it is way too small This should be about 20TB : [root at solexa1 StorMan]# df -h /dev/sdb1 Filesystem Size Used Avail Use% Mounted on /dev/sdb1 186G 60M

I don't think this is off topic since I want to use JBOD mode so that Linux can do the RAID. I'm going to hopefully run this in CentOS 5 and Ubuntu 12.04 on a Sunfire x2250 Hard to get answers I can trust out of vendors :-) I have a Sun RAID card which I am pretty sure is LSI OEM. It is a 3G/s SAS1 with 2 external connectors like the one on the right here :

On 3/14/19 2:31 PM, isdtor wrote: > >> I'd like to monitor the disks connected to a ServeRaid-8k controller in a >> server running Centos 7 such that I can know when one fails. >> >> What's the best way to do that? > > It's been a long time since I worked with ServeRaid, and things may have changed in the meantime. > > IBM used to have a an iso

Hi, I've installed a FreeBSD (stable 9.2) as a guest on ESXi 5.5. I've added Adaptec Controller via passthrough. Unfortunately FreeBSD does not show hard drives. Any clue? aac0: <Adaptec RAID 5805> mem 0xfd200000-0xfd3fffff irq 18 at device 0.0 on pci3 aac0: Enabling 64-bit address support aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0:

> I'd like to monitor the disks connected to a ServeRaid-8k controller in a > server running Centos 7 such that I can know when one fails. > > What's the best way to do that? It's been a long time since I worked with ServeRaid, and things may have changed in the meantime. IBM used to have a an iso with ServeRaid related tools (ibm_sw_srapp_.....) that included Linux

I have just built a new SunFire X4100 server with an Adaptec 2230SLP RAID card using FreeBSD 6.2-PRE kernel (from September 20). Everything is working extremely well except I cannot run the aaccli utility on this controller. When I try to open the controller, it gives this error: Command Error: <The current AFAAPI.DLL is too old to work with the current controller software.> On

Hi, I'd like to monitor the disks connected to a ServeRaid-8k controller in a server running Centos 7 such that I can know when one fails. What's the best way to do that?

We have Sun STK RAID cards in our x4170 servers. These are battery backed with 256mb cache. What is the recommended ZFS configuration for these cards? Right now, I have created a one-to-one logical volume to disk mapping on the RAID card (one disk == one volume on RAID card). Then, I mirror them using ZFS. No hardware mirror. What I am a little confused with is if it is better to not do any

Hi. Since this revision (appeared in 6.3) I think ipfw violates POLA. I mean "ipfw table N list" shows values of table in Internet '.' notation. A friend of mine was surprised to found Internet representation of this "optional 32-bit unsigned value". For example security/bruteblock stores unix timestamps here and AFAICS there is no possibility to come back to the

Hi. Sometimes I see much contention in smp_tlb_shootdown while running sysbench: sysbench --test=fileio --num-threads=8 --file-test-mode=rndrd --file-total-size=3G run kern.smp.cpus: 8 FreeBSD 7.1-R CPU: 0.8% user, 0.0% nice, 93.8% system, 0.0% interrupt, 5.4% idle Mem: 11M Active, 2873M Inact, 282M Wired, 8K Cache, 214M Buf, 765M Free Swap: 4096M Total, 4096M Free PID USERNAME PRI NICE

Hi, Does anyone know how I can find out if an ibm serveraid 8k sas storage controller (zero channel RAID) is a real hardware RAID controller and supported in the standard CentOs kernel or is it a fake raid controller. I am trying to decide if I should get the serveraid controller or go get a 3ware controller. Regards, -- Tom Diehl tdiehl at rogueind.com Spamtrap address mtd123 at

Does Centos include any runtime monitor/control software for raid arrays on AACRAID devices as on IBM 3650's? -- Les Mikesell lesmikesell at gmail.com

> hwilmer wrote: >> >> I'd like to monitor the disks connected to a ServeRaid-8k controller in >> a server running Centos 7 such that I can know when one fails. >> >> What's the best way to do that? > > From a *really* short search, see it has a controller card If you do an > lspci, what does that tell you - is it yet another rebranded LSI card? If

Hi. I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach:

Изменения в nginx 1.27.0 29.05.2024 *) Безопасность: при использовании HTTP/3 обработка специально созданной QUIC-сессии могла приводить к падению рабочего процесса, отправке клиенту содержимого памяти рабочего процесса на системах с MTU больше 4096 байт, а также потенциально могла иметь другие последствия (CVE-2024-32760,

Changes with nginx 1.27.0 29 May 2024 *) Security: when using HTTP/3, processing of a specially crafted QUIC session might cause a worker process crash, worker process memory disclosure on systems with MTU larger than 4096 bytes, or might have potential other impact (CVE-2024-32760, CVE-2024-31079, CVE-2024-35200, CVE-2024-34161).

Changes with nginx 1.26.1 29 May 2024 *) Security: when using HTTP/3, processing of a specially crafted QUIC session might cause a worker process crash, worker process memory disclosure on systems with MTU larger than 4096 bytes, or might have potential other impact (CVE-2024-32760, CVE-2024-31079, CVE-2024-35200, CVE-2024-34161).

Hello! Four security issues were identified in nginx HTTP/3 implementation, which might allow an attacker that uses a specially crafted QUIC session to cause a worker process crash (CVE-2024-31079, CVE-2024-32760, CVE-2024-35200), worker process memory disclosure on systems with MTU larger than 4096 bytes (CVE-2024-34161), or might have potential other impact (CVE-2024-31079, CVE-2024-32760).

Изменения в nginx 1.26.1 29.05.2024 *) Безопасность: при использовании HTTP/3 обработка специально созданной QUIC-сессии могла приводить к падению рабочего процесса, отправке клиенту содержимого памяти рабочего процесса на системах с MTU больше 4096 байт, а также потенциально могла иметь другие последствия (CVE-2024-32760,

Hello! В реализации HTTP/3 в nginx были обнаружены четыре проблемы, которые позволяют атакующему с помощью специально созданной QUIC-сессии вызвать падение рабочего процесса (CVE-2024-31079, CVE-2024-32760, CVE-2024-35200), отправку клиенту части содержимого памяти рабочего процесса на системах с MTU больше 4096 байт (CVE-2024-34161), а также потенциально могут иметь другие последствия