Perhaps it was your Megaraid controller doing a patrol read or
consistency check?
-Taru
On Sat, Jan 1, 2022 at 12:13 PM Luke Small <lukensmall@gmail.com> wrote:
> 6 disk raid 10 15000 rpm array (2 mirroring x 3 striping) with a raid card
> which can handle a maximum of 8 disks. It didn't last forever.
>
> mfii0 at pci12 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05:
> msi
> mfii0: "LSI MegaRAID SAS 9271-8i", firmware 23.28.0-0010, 1024MB cache
> scsibus2 at mfii0: 64 targets
> sd0 at scsibus2 targ 0 lun 0: <LSI, MR9271-8i, 3.40>
> naa.600605b00902fb50217c572a11e3e137
> sd0: 418464MB, 512 bytes/sector, 857014272 sectors
> scsibus3 at mfii0: 256 targets
> ppb11 at pci7 dev 9 function 0 "Intel X58 PCIE" rev 0x22: msi
> pci13 at ppb11 bus 135
> "Intel X58 IOxAPIC" rev 0x22 at pci7 dev 19 function 0 not configured
> "Intel X58 Misc" rev 0x22 at pci7 dev 20 function 0 not configured
> "Intel X58 GPIO" rev 0x22 at pci7 dev 20 function 1 not configured
> "Intel X58 RAS" rev 0x22 at pci7 dev 20 function 2 not configured
> "Intel X58 Throttle" rev 0x22 at pci7 dev 20 function 3 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 0 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 1 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 2 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 3 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 4 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 5 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 6 not configured
> "Intel X58 QuickData" rev 0x22 at pci7 dev 22 function 7 not configured
> vmm0 at mainbus0: VMX/EPT
> dt: 445 probes
> vscsi0 at root
> scsibus4 at vscsi0: 256 targets
> softraid0 at root
> scsibus5 at softraid0: 256 targets
> sd1 at scsibus5 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006>
> sd1: 418458MB, 512 bytes/sector, 857002898 sectors
> sd2 at scsibus1 targ 5 lun 0: <ATA, 3E128-TS2-550B01, UI39>
> naa.5001173100147bc4
> sd2: 95367MB, 512 bytes/sector, 195312501 sectors
> sd3 at scsibus1 targ 6 lun 0: <ATA, 3E128-TS2-550B01, UI39>
> naa.5001173100146d54
> sd3: 95367MB, 512 bytes/sector, 195312501 sectors
> sd4 at scsibus1 targ 7 lun 0: <ATA, 3E128-TS2-550B01, UI39>
> naa.50011731001432cc
> sd4: 95367MB, 512 bytes/sector, 195312501 sectors
> sd5 at scsibus1 targ 8 lun 0: <ATA, 3E128-TS2-550B01, UI39>
> naa.500117310014346c
> sd5: 95367MB, 512 bytes/sector, 195312501 sectors
> disklabels not read:
> root on sd1a (7f4c2a49b672064f.a) swap on sd1b dump on sd1b
> radeondrm0: CAICOS
> radeondrm0: 1920x1080, 32bpp
> wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using
> wskbd0
> wsdisplay0: screen 1-5 added (std, vt100 emulation)
>
> On Sat, Jan 1, 2022 at 4:22 AM Crystal Kolipe <kolipe.c@exoticsilicon.com>
> wrote:
>
> > On Sat, Jan 01, 2022 at 12:01:28AM -0600, Luke Small wrote:
> > > The lights on my server which shows that the disks are busy were on and
> > not
> > > just flashing and I looked at top and usually it???s because security
> is
> > > running, but this time NOTHING! I even killed Firefox and by far the
> > > busiest thing on there was top! pftop didn???t seem especially busy
> > either!
> >
> > From the extremely limited information you've given, it's hard to
> diagnose
> > the problem.
> >
> > In future, please include the output of dmesg and the output of relevant
> > commands in problem reports. This answers questions such as: how many
> > disks are in this server? Are they part of an array?
> >
> > Did the output from top show a process with low or zero cpu usage, but
> > stuck in the biowait state?
> >
> > This can happen, for example, if you have a bad or failing data cable
> from
> > the disk to the motherboard. It can also happen with some SSDs, likely
> due
> > to the firmware doing some kind of internal management of the flash
> memory.
> >
> --
> -Luke
>
No comments:
Post a Comment