akia

Members
  • Posts

    12
  • Joined

  • Last visited

akia's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. is this just a problem with one of my dockers? Apr 9 10:48:48 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-abd05162caec: link becomes ready Apr 9 10:48:49 Tower rc.docker: nextcloud: started succesfully! Apr 9 10:48:49 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg Apr 9 10:48:49 Tower emhttpd: Starting services... Apr 9 10:48:49 Tower avahi-daemon[12063]: Joining mDNS multicast group on interface vethc2628ed.IPv6 with address fe80::bcc8:deff:fea7:1cb4. Apr 9 10:48:49 Tower avahi-daemon[12063]: New relevant interface vethc2628ed.IPv6 for mDNS. Apr 9 10:48:49 Tower avahi-daemon[12063]: Registering new address record for fe80::bcc8:deff:fea7:1cb4 on vethc2628ed.*. Apr 9 10:48:50 Tower avahi-daemon[12063]: Joining mDNS multicast group on interface br-abd05162caec.IPv6 with address fe80::42:e7ff:fede:72b2. Apr 9 10:48:50 Tower avahi-daemon[12063]: New relevant interface br-abd05162caec.IPv6 for mDNS. Apr 9 10:48:50 Tower avahi-daemon[12063]: Registering new address record for fe80::42:e7ff:fede:72b2 on br-abd05162caec.*. Apr 9 10:48:50 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg Apr 9 10:48:50 Tower emhttpd: Starting services... Apr 9 10:48:51 Tower avahi-daemon[12063]: Interface vnet0.IPv6 no longer relevant for mDNS. Apr 9 10:48:51 Tower avahi-daemon[12063]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fef8:a2ea. Apr 9 10:48:51 Tower kernel: virbr0: port 2(vnet0) entered disabled state Apr 9 10:48:51 Tower kernel: device vnet0 left promiscuous mode Apr 9 10:48:51 Tower kernel: virbr0: port 2(vnet0) entered disabled state Apr 9 10:48:51 Tower avahi-daemon[12063]: Withdrawing address record for fe80::fc54:ff:fef8:a2ea on vnet0. Apr 9 10:48:52 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg Apr 9 10:48:52 Tower emhttpd: Starting services... Apr 9 10:48:52 Tower rc.docker: SteamCacheBundle: started succesfully! Apr 9 10:48:53 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg Apr 9 10:48:53 Tower emhttpd: Starting services... Apr 9 10:48:54 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg
  2. rebooted and attached new diags. for the flash drive would i just plug it into a windows pc to fix it? I have had to do that in the past. tower-diagnostics-20190409-1105.zip
  3. Hello, Im getting this error all the time and my server always says starting services. Also getting buffer I/O error. Please advise if you need more info or what i can also provide. thank you in advance. Apr 9 10:31:49 Tower ntfs-3g[18008]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Apr 9 10:31:49 Tower ntfs-3g[18008]: Failed to read index block: Input/output error Apr 9 10:31:49 Tower kernel: Buffer I/O error on dev sda1, logical block 211252, async page read Apr 9 10:31:49 Tower ntfs-3g[18648]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Apr 9 10:31:49 Tower ntfs-3g[18648]: Failed to read index block: Input/output error Apr 9 10:31:49 Tower kernel: Buffer I/O error on dev sdb2, logical block 44, async page read Apr 9 10:31:50 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfgtower-diagnostics-20190409-0850.zip Apr 8 08:17:59 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg Apr 8 08:17:59 Tower emhttpd: Starting services... Apr 8 08:18:00 Tower emhttpd: error: put_config_idx, 609: Invalid argument (22): fopen: /boot/config/shares/?.cfg unRAID server Pro, version 6.6.7 M/B: Gigabyte Technology Co., Ltd. - Z97X-Gaming 5 CPU: Intel® Core™ i5-4590 CPU @ 3.30GHz HVM: Enabled IOMMU: Enabled Cache: 256 kB, 1024 kB, 6144 kB Memory: 16 GB (max. installable capacity 32 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a Uptime: 26 days
  4. ok so i have replaced every piece of hardware and stil getting errors. could my xfs system be corrupted?
  5. replacing the cable didn't change i still get write errors.... Can i move the drives to a new pc will the shares move over? here are some new errors im getting. Apr 6 19:21:33 Tower kernel: print_req_error: I/O error, dev sdh, sector 4505524312 Apr 6 19:21:33 Tower kernel: md: disk3 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: md: disk4 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: md: disk5 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: md: disk6 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: md: disk7 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: md: disk0 read error, sector=4505524248 Apr 6 19:21:33 Tower kernel: XFS (md2): metadata I/O error: block 0x10c8cd818 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:38 Tower shfs: error: shfs_rmdir, 1537: Input/output error (5): lookup: Games/pc games/Wolfenstein II [FitGirl Repack] Apr 6 19:21:40 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:40 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:40 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:50 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:50 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:21:50 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:00 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:00 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:00 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:10 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:10 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:10 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:20 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:20 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:20 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:30 Tower kernel: XFS (md5): metadata I/O error: block 0xc4a10 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:30 Tower kernel: XFS (md5): metadata I/O error: block 0x5837d9a0 ("xfs_trans_read_buf_map") error 5 numblks 8 Apr 6 19:22:30 Tower kernel: XFS (md5): metadata I/O error: block 0xaf912568 ("xfs_trans_read_buf_map") error 5 numblks 8 tower-diagnostics-20180406-1924.zip
  6. The one attached was after replacing most of the hardware to try and isolate the problem. Here is one after the cable replacement. tower-diagnostics-20180405-2009.zip
  7. i replaced the qsfp sas cable now the parity check is going. but i can't see any of the shares now. Any way to recover them? thank you
  8. thank you for the quick response. I wonder if the transposers convert sata to sas is causing the smart to not be passed through.
  9. Hello first of all thank you so much for making this great software so far i been loving it. But im running into a major issue with getting lots of errors. I have the server running off a HBA card to a disk shelf ds4243. The only error i see is that drive 10 isn't spinning down properly. I have replaced 90% of the hardware and the only things getting carried over is the sas cable, raid card and drives. please please need some help!!! tower-diagnostics-20180404-2228.zip
  10. Hello I'm having some issues with unraid docker doesn't work. I'm sure it's related to my cache drive being full. But can't move any files off the cache disk since can't get into Krusader. I tried turning off all the cache shares and adding it back on. I have attached diags. I would appreciate any help. Thank you tower-diagnostics-20180311-2345.zip