June 19, 20179 yr I have been having issues with the web UI quite a bit after installing and the server seems to not shutdown as well when i give the "powerdown" command i will post my diagnostics as well but it is annoying though. coreserver-diagnostics-20170619-2122.zip
June 20, 20179 yr Hi, It appears you have a number of disk/controller errors in your log: Jun 19 21:12:31 CoreServer kernel: DMAR: DRHD: handling fault status reg 202 Jun 19 21:12:31 CoreServer kernel: DMAR: [DMA Read] Request device [02:00.0] fault addr e0000 [fault reason 06] PTE Read access is not set Jun 19 21:12:32 CoreServer kernel: mpt2sas_cm0: fault_state(0x2665)! Jun 19 21:12:32 CoreServer kernel: mpt2sas_cm0: sending diag reset !! Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: diag reset: SUCCESS Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: log_info(0x30030100): originator(IOP), code(0x03), sub_code(0x0100) Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: log_info(0x30030100): originator(IOP), code(0x03), sub_code(0x0100) Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: LSISAS2008: FWVersion(02.15.63.00), ChipRevision(0x02), BiosVersion(07.01.09.00) Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: Protocol=( Jun 19 21:12:33 CoreServer kernel: Initiator Jun 19 21:12:33 CoreServer kernel: ,Target Jun 19 21:12:33 CoreServer kernel: ), Jun 19 21:12:33 CoreServer kernel: Capabilities=( Jun 19 21:12:33 CoreServer kernel: Raid Jun 19 21:12:33 CoreServer kernel: ,TLR Jun 19 21:12:33 CoreServer kernel: ,EEDP Jun 19 21:12:33 CoreServer kernel: ,Snapshot Buffer Jun 19 21:12:33 CoreServer kernel: ,Diag Trace Buffer Jun 19 21:12:33 CoreServer kernel: ,Task Set Full Jun 19 21:12:33 CoreServer kernel: ,NCQ Jun 19 21:12:33 CoreServer kernel: ) Jun 19 21:12:33 CoreServer kernel: mpt2sas_cm0: sending port enable !! Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: port enable: SUCCESS Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for end-devices: start Jun 19 21:12:40 CoreServer kernel: scsi target1:0:0: handle(0x0009), sas_addr(0x4433221106000000) Jun 19 21:12:40 CoreServer kernel: scsi target1:0:0: enclosure logical id(0x5842b2b018707500), slot(1) Jun 19 21:12:40 CoreServer kernel: scsi target1:0:1: handle(0x000a), sas_addr(0x4433221107000000) Jun 19 21:12:40 CoreServer kernel: scsi target1:0:1: enclosure logical id(0x5842b2b018707500), slot(0) Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for end-devices: complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for raid volumes: start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for responding raid volumes: complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for expanders: start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: search for expanders: complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: _base_fault_reset_work: hard reset: success Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: removing unresponding devices: start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: removing unresponding devices: end-devices Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: removing unresponding devices: volumes Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: removing unresponding devices: expanders Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: removing unresponding devices: complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: expanders start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: break from expander scan: ioc_status(0x0022), loginfo(0x310f0400) Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: expanders complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: phys disk start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: break from phys disk scan: ioc_status(0x0022), loginfo(0x00000000) Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: phys disk complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: volumes start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: break from volume scan: ioc_status(0x0022), loginfo(0x00000000) Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: volumes complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: end devices start Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: break from end device scan: ioc_status(0x0022), loginfo(0x310f0400) Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: end devices complete Jun 19 21:12:40 CoreServer kernel: mpt2sas_cm0: scan devices: complete Jun 19 21:12:53 CoreServer kernel: sd 1:0:1:0: timing out command, waited 20s Jun 19 21:12:53 CoreServer kernel: sd 1:0:0:0: timing out command, waited 20s Jun 19 21:15:53 CoreServer kernel: sd 1:0:1:0: timing out command, waited 180s Jun 19 21:15:53 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:21:29 CoreServer kernel: br0: port 2(vnet0) entered blocking state Jun 19 21:21:29 CoreServer kernel: br0: port 2(vnet0) entered disabled state Jun 19 21:21:29 CoreServer kernel: device vnet0 entered promiscuous mode Jun 19 21:21:29 CoreServer kernel: br0: port 2(vnet0) entered blocking state Jun 19 21:21:29 CoreServer kernel: br0: port 2(vnet0) entered forwarding state Jun 19 21:21:30 CoreServer kernel: kvm: zapping shadow pages for mmio generation wraparound Jun 19 21:21:30 CoreServer kernel: kvm: zapping shadow pages for mmio generation wraparound Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 360s Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jun 19 21:27:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 0 Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:27:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 2b aa aa 60 00 00 10 00 Jun 19 21:27:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 732605024 Jun 19 21:27:10 CoreServer kernel: md: disk1 write error, sector=732604960 Jun 19 21:27:10 CoreServer kernel: md: disk1 write error, sector=732604968 Jun 19 21:27:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91575620, lost async page write Jun 19 21:27:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91575621, lost async page write Jun 19 21:30:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:30:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:30:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 1d 1c 34 58 00 00 08 00 Jun 19 21:30:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 488387672 Jun 19 21:30:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 488387672 Jun 19 21:30:10 CoreServer kernel: md: disk1 write error, sector=488387608 Jun 19 21:30:10 CoreServer kernel: XFS (md1): metadata I/O error: block 0x1d1c3419 ("xlog_iodone") error 5 numblks 64 Jun 19 21:30:10 CoreServer kernel: XFS (md1): xfs_do_force_shutdown(0x2) called from line 1200 of file fs/xfs/xfs_log.c. Return address = 0xffffffff812b4a91 Jun 19 21:30:10 CoreServer kernel: XFS (md1): Log I/O Error Detected. Shutting down filesystem Jun 19 21:30:10 CoreServer kernel: XFS (md1): Please umount the filesystem and rectify the problem(s) Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 360s Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jun 19 21:33:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 0 Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:33:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 2b ab 6c e0 00 00 40 00 Jun 19 21:33:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 732654816 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654752 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654760 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654768 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654776 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654784 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654792 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654800 Jun 19 21:33:10 CoreServer kernel: md: disk1 write error, sector=732654808 Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581844, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581845, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581846, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581847, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581848, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581849, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581850, lost async page write Jun 19 21:33:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91581851, lost async page write Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 2b ad 06 60 00 00 40 00 Jun 19 21:36:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 732759648 Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: timing out command, waited 180s Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Jun 19 21:36:10 CoreServer kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 1d 1c 34 60 00 00 08 00 Jun 19 21:36:10 CoreServer kernel: blk_update_request: I/O error, dev sdb, sector 488387680 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759584 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759592 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759600 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759608 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759616 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759624 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759632 Jun 19 21:36:10 CoreServer kernel: md: disk1 write error, sector=732759640 Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594948, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594949, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594950, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594951, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594952, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594953, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594954, lost async page write Jun 19 21:36:10 CoreServer kernel: Buffer I/O error on dev md1, logical block 91594955, lost async page write Jun 19 21:36:10 CoreServer kernel: md: disk1 read error, sector=488387616 Jun 19 21:36:10 CoreServer kernel: XFS (md1): metadata I/O error: block 0x1d1c341d ("xlog_iodone") error 5 numblks 64 Jun 19 21:36:10 CoreServer kernel: blk_update_request: I/O error, dev loop1, sector 0 Jun 19 21:36:10 CoreServer kernel: loop: Write error at byte offset 12787712, length 4096. Jun 19 21:36:10 CoreServer kernel: blk_update_request: I/O error, dev loop1, sector 24976 Jun 19 21:36:10 CoreServer kernel: loop: Write error at byte offset 12918272, length 512. Jun 19 21:36:10 CoreServer kernel: blk_update_request: I/O error, dev loop1, sector 25231 Jun 19 21:36:10 CoreServer kernel: BTRFS error (device loop1): bdev /dev/loop1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jun 19 21:36:10 CoreServer kernel: BTRFS error (device loop1): bdev /dev/loop1 errs: wr 1, rd 0, flush 1, corrupt 0, gen 0 Jun 19 21:36:10 CoreServer kernel: BTRFS: error (device loop1) in write_all_supers:3741: errno=-5 IO failure (errors while submitting device barriers.) Jun 19 21:36:10 CoreServer kernel: BTRFS info (device loop1): forced readonly Jun 19 21:36:10 CoreServer kernel: ------------[ cut here ]------------ Jun 19 21:36:10 CoreServer kernel: WARNING: CPU: 2 PID: 3327 at fs/btrfs/tree-log.c:2951 btrfs_sync_log+0x7b3/0x9a1 Jun 19 21:36:10 CoreServer kernel: BTRFS: Transaction aborted (error -5) Jun 19 21:36:10 CoreServer kernel: Modules linked in: coretemp xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables vhost_net tun vhost macvtap macvlan ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod bonding ipmi_devintf kvm_intel kvm ahci libahci mpt3sas tg3 raid_class ptp scsi_transport_sas pps_core ipmi_si acpi_cpufreq [last unloaded: coretemp] Jun 19 21:36:10 CoreServer kernel: CPU: 2 PID: 3327 Comm: libvirtd Not tainted 4.9.30-unRAID #1 Jun 19 21:36:10 CoreServer kernel: Hardware name: Dell Inc. PowerEdge T110/0X744K, BIOS 1.3.4 05/24/2010 Jun 19 21:36:10 CoreServer kernel: ffffc900059dbc98 ffffffff813a4a1b ffffc900059dbce8 ffffffff8196ce48 Jun 19 21:36:10 CoreServer kernel: ffffc900059dbcd8 ffffffff8104d0d9 00000b87059dbd50 ffff88040b935000 Jun 19 21:36:10 CoreServer kernel: 00000000fffffffb ffff88040b90c000 ffff88040b908000 ffff880410a54140 Jun 19 21:36:10 CoreServer kernel: Call Trace: Jun 19 21:36:10 CoreServer kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Jun 19 21:36:10 CoreServer kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3 Jun 19 21:36:10 CoreServer kernel: [<ffffffff8104d13a>] warn_slowpath_fmt+0x46/0x4e Jun 19 21:36:10 CoreServer kernel: [<ffffffff8132b3d2>] btrfs_sync_log+0x7b3/0x9a1 Jun 19 21:36:10 CoreServer kernel: [<ffffffff813048fa>] btrfs_sync_file+0x290/0x2f5 Jun 19 21:36:10 CoreServer kernel: [<ffffffff813048fa>] ? btrfs_sync_file+0x290/0x2f5 Jun 19 21:36:10 CoreServer kernel: [<ffffffff81146f6e>] vfs_fsync_range+0x87/0x99 Jun 19 21:36:10 CoreServer kernel: [<ffffffff81146f97>] vfs_fsync+0x17/0x19 Jun 19 21:36:10 CoreServer kernel: [<ffffffff81146fc5>] do_fsync+0x2c/0x45 Jun 19 21:36:10 CoreServer kernel: [<ffffffff811471c5>] SyS_fsync+0xb/0xf Jun 19 21:36:10 CoreServer kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 Jun 19 21:36:10 CoreServer kernel: ---[ end trace b17fa73cf28b0b52 ]--- Jun 19 21:36:10 CoreServer kernel: BTRFS: error (device loop1) in btrfs_sync_log:2951: errno=-5 IO failure Jun 19 21:36:10 CoreServer kernel: BTRFS warning (device loop1): Skipping commit of aborted transaction. Jun 19 21:36:10 CoreServer kernel: BTRFS: error (device loop1) in cleanup_transaction:1850: errno=-5 IO failure Jun 19 21:36:10 CoreServer kernel: BTRFS info (device loop1): delayed_refs has NO entry Jun 19 21:36:10 CoreServer kernel: XFS (md1): xfs_do_force_shutdown(0x2) called from line 1200 of file fs/xfs/xfs_log.c. Return address = 0xffffffff812b4a91 Is this a new server or one that you've had for a while? I would definitely recheck cable connections to your storage devices as well as your power supply.
June 20, 20179 yr Author Bought it second hand from a working environment the drives are plugged into a raid card atm, would you rather me plug them into the motherboard? Thank you
June 20, 20179 yr Author I have moved ports on the raid card to see if that helps, the raid card is also in HBA mode because I want UnRAID to do the work there
Archived
This topic is now archived and is closed to further replies.