comet424 Posted April 16, 2020 Share Posted April 16, 2020 so I been trying to fix errors I noticed I had like vnstat issues etc but I still cant figure out what XFERED is... what the errors it shows... and also the SysLogs parity check.. the mem size etc.. what are some of these warnings and how I fix them? Apr 15 22:33:36 Tower kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA Apr 15 22:33:36 Tower kernel: tsc: Fast TSC calibration failed Apr 15 22:33:36 Tower kernel: ACPI: Early table checksum verification disabled Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:01:00.0: BAR 14: failed to assign [mem size 0x00b00000] Apr 15 22:33:36 Tower kernel: pci 0000:02:02.0: BAR 14: failed to assign [mem size 0x00600000] Apr 15 22:33:36 Tower kernel: pci 0000:02:05.0: BAR 14: failed to assign [mem size 0x00100000] Apr 15 22:33:36 Tower kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00200000] Apr 15 22:33:36 Tower kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00100000] Apr 15 22:33:36 Tower kernel: pci 0000:02:0a.0: BAR 14: failed to assign [mem size 0x00100000] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:04:00.0: BAR 4: failed to assign [mem size 0x00004000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:04:00.0: BAR 2: failed to assign [mem size 0x00001000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:05:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:05:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit] Apr 15 22:33:36 Tower kernel: pci 0000:06:00.0: BAR 5: failed to assign [mem size 0x00000800] Apr 15 22:33:36 Tower kernel: pci 0000:07:00.0: BAR 5: failed to assign [mem size 0x00000800] Apr 15 22:33:36 Tower kernel: floppy0: no floppy controllers found Apr 15 22:33:36 Tower kernel: random: 6 urandom warning(s) missed due to ratelimiting Apr 15 22:33:36 Tower kernel: ccp 0000:0a:00.1: psp initialization failed Apr 15 22:33:38 Tower rpc.statd[1890]: Failed to read /var/lib/nfs/state: Success Apr 15 22:33:50 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20180810/utaddress-204) Apr 15 22:33:50 Tower root: Warning: parse_ini_file(/var/local/emhttp/var.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 56 Apr 15 22:33:50 Tower root: Warning: Division by zero in /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php on line 62 tower-diagnostics-20200415-2241.zip Quote Link to comment
Squid Posted April 16, 2020 Share Posted April 16, 2020 The errors are all normal kernel start up stuff and nothing to worry about. The screenshot shows the rclone plugin updating itself at boot time and is normal for it Quote Link to comment
comet424 Posted April 16, 2020 Author Share Posted April 16, 2020 ah ok thank you as I didn't know if the preclear or mem was serious or not and I remember Unraid when it used to boot up guess now 2 years ago.. when rebooting the GUI would should up right away... and you would see the Array starting but youd be able to access unraid as its mounting now it will not show up anymore unless the array is fully started... is that normal? as even if I tried to to do tower\ I get page cant be found.. so just curious if that's normal now that web interface is non accessible till array is fully started.. Quote Link to comment
itimpi Posted April 16, 2020 Share Posted April 16, 2020 2 hours ago, comet424 said: ah ok thank you as I didn't know if the preclear or mem was serious or not and I remember Unraid when it used to boot up guess now 2 years ago.. when rebooting the GUI would should up right away... and you would see the Array starting but youd be able to access unraid as its mounting now it will not show up anymore unless the array is fully started... is that normal? as even if I tried to to do tower\ I get page cant be found.. so just curious if that's normal now that web interface is non accessible till array is fully started.. No, it should not be necessary to have the array started to access the GUI. Quote Link to comment
comet424 Posted April 16, 2020 Author Share Posted April 16, 2020 (edited) oh so then as I can access the console login and about 1 min to 2 min roughly then the gui is accessible the gui isn't accessible till the array or the services started... least that's what I noticed is there another check I need to check? can you guys see my go file from the diagnostics I posted.. the modprobe doesn't work anyways in it as seems x570 temp sensors are broken for x570... but I had that in there for forcing... but maybe you guys can see my go file or somewhere else why is the gui unaccessible till its fully loaded Edited April 16, 2020 by comet424 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.