Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

syslog errors while booting

loadme
in unRAID Server 4.5 [No new topics]

Featured Replies

hello everyone.

 

 

i have noticed some warnings and errors on sys-startup.

here is what my log tells me. can anyone translate it for me please?

 

...

...

 

Sep 25 14:31:07 Tower kernel: Mount-cache hash table entries: 512

Sep 25 14:31:07 Tower kernel: CPU: L1 I cache: 32K, L1 D cache: 32K

Sep 25 14:31:07 Tower kernel: CPU: L2 cache: 4096K

Sep 25 14:31:07 Tower kernel: CPU: Physical Processor ID: 0

Sep 25 14:31:07 Tower kernel: CPU: Processor Core ID: 0

Sep 25 14:31:07 Tower kernel: mce: CPU supports 6 MCE banks

Sep 25 14:31:07 Tower kernel: CPU0: Thermal monitoring enabled (TM2)

Sep 25 14:31:07 Tower kernel: using mwait in idle threads.

Sep 25 14:31:07 Tower kernel: Checking 'hlt' instruction... OK.

Sep 25 14:31:07 Tower kernel: ACPI: Core revision 20090903

Sep 25 14:31:07 Tower kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1

Sep 25 14:31:07 Tower kernel: CPU0: Intel® Core2 CPU T7200 @ 2.00GHz stepping 06

Sep 25 14:31:07 Tower kernel: Booting processor 1 APIC 0x1 ip 0x6000

Sep 25 14:31:07 Tower kernel: Initializing CPU#1

Sep 25 14:31:07 Tower kernel: CPU: L1 I cache: 32K, L1 D cache: 32K

Sep 25 14:31:07 Tower kernel: CPU: L2 cache: 4096K

Sep 25 14:31:07 Tower kernel: CPU: Physical Processor ID: 0

Sep 25 14:31:07 Tower kernel: CPU: Processor Core ID: 1

Sep 25 14:31:07 Tower kernel: CPU1: Thermal monitoring enabled (TM2)

Sep 25 14:31:07 Tower kernel: CPU1: Intel® Core2 CPU T7200 @ 2.00GHz stepping 06

Sep 25 14:31:07 Tower kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed.

Sep 25 14:31:07 Tower kernel: Brought up 2 CPUs

Sep 25 14:31:07 Tower kernel: Total of 2 processors activated (7999.80 BogoMIPS).

Sep 25 14:31:07 Tower kernel: NET: Registered protocol family 16

Sep 25 14:31:07 Tower kernel: ACPI: bus type pci registered

Sep 25 14:31:07 Tower kernel: PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255

Sep 25 14:31:07 Tower kernel: PCI: Not using MMCONFIG.

Sep 25 14:31:07 Tower kernel: PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=4

Sep 25 14:31:07 Tower kernel: PCI: Using configuration type 1 for base access

Sep 25 14:31:07 Tower kernel: bio: create slab at 0

Sep 25 14:31:07 Tower kernel: ACPI: EC: Look up EC in DSDT

Sep 25 14:31:07 Tower kernel: ACPI: Executed 1 blocks of module-level executable AML code

Sep 25 14:31:07 Tower kernel: ACPI: Interpreter enabled

Sep 25 14:31:07 Tower kernel: ACPI: (supports S0 S1 S3 S5)

Sep 25 14:31:07 Tower kernel: ACPI: Using IOAPIC for interrupt routing

Sep 25 14:31:07 Tower kernel: PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255

Sep 25 14:31:07 Tower kernel: PCI: MCFG area at e0000000 reserved in ACPI motherboard resources

Sep 25 14:31:07 Tower kernel: PCI: Using MMCONFIG for extended config space

Sep 25 14:31:07 Tower kernel: ACPI Warning: Incorrect checksum in table [OEMB] - A9, should be A4 (20090903/tbutils-314)

Sep 25 14:31:07 Tower kernel: ACPI: No dock devices found.

Sep 25 14:31:07 Tower kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)

 

and some lines later..

..

...

Sep 25 14:31:07 Tower kernel: NET: Registered protocol family 2

Sep 25 14:31:07 Tower kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)

Sep 25 14:31:07 Tower kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)

Sep 25 14:31:07 Tower kernel: TCP bind hash table entries: 65536 (order: 7, 524288 bytes)

Sep 25 14:31:07 Tower kernel: TCP: Hash tables configured (established 131072 bind 65536)

Sep 25 14:31:07 Tower kernel: TCP reno registered

Sep 25 14:31:07 Tower kernel: NET: Registered protocol family 1

Sep 25 14:31:07 Tower kernel: RPC: Registered udp transport module.

Sep 25 14:31:07 Tower kernel: RPC: Registered tcp transport module.

Sep 25 14:31:07 Tower kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.

Sep 25 14:31:07 Tower kernel: pci 0000:00:02.0: Boot video device

Sep 25 14:31:07 Tower kernel: Unpacking initramfs...

Sep 25 14:31:07 Tower kernel: Freeing initrd memory: 53456k freed

Sep 25 14:31:07 Tower kernel: highmem bounce pool size: 64 pages

Sep 25 14:31:07 Tower kernel: Installing knfsd (copyright © 1996 [email protected]).

Sep 25 14:31:07 Tower kernel: Slow work thread pool: Starting up

Sep 25 14:31:07 Tower kernel: Slow work thread pool: Ready

Sep 25 14:31:07 Tower kernel: fuse init (API version 7.13)

Sep 25 14:31:07 Tower kernel: msgmni has been set to 1736

Sep 25 14:31:07 Tower kernel: io scheduler noop registered (default)

Sep 25 14:31:07 Tower kernel: io scheduler anticipatory registered

Sep 25 14:31:07 Tower kernel: io scheduler deadline registered

Sep 25 14:31:07 Tower kernel: io scheduler cfq registered

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.0: setting latency timer to 64

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.2: irq 25 for MSI/MSI-X

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.2: setting latency timer to 64

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.3: irq 26 for MSI/MSI-X

Sep 25 14:31:07 Tower kernel: pcieport 0000:00:1c.3: setting latency timer to 64

Sep 25 14:31:07 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0

Sep 25 14:31:07 Tower kernel: ACPI: Power Button [PWRB]

Sep 25 14:31:07 Tower kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1

Sep 25 14:31:07 Tower kernel: ACPI: Power Button [PWRF]

Sep 25 14:31:07 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU1._OSC] (Node f740e198), AE_ALREADY_EXISTS

Sep 25 14:31:07 Tower kernel: ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error

Sep 25 14:31:07 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU1._PDC] (Node f740e180), AE_ALREADY_EXISTS

Sep 25 14:31:07 Tower kernel: ACPI: Marking method _PDC as Serialized because of AE_ALREADY_EXISTS error

Sep 25 14:31:07 Tower kernel: processor LNXCPU:00: registered as cooling_device0

Sep 25 14:31:07 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU2._OSC] (Node f740e270), AE_ALREADY_EXISTS

Sep 25 14:31:07 Tower kernel: ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error

Sep 25 14:31:07 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU2._PDC] (Node f740e258), AE_ALREADY_EXISTS

Sep 25 14:31:07 Tower kernel: ACPI: Marking method _PDC as Serialized because of AE_ALREADY_EXISTS error

 

 

and later again..

...

...

Sep 25 14:31:09 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.

Sep 25 14:31:10 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Sep 25 14:31:10 Tower ifplugd(eth0)[1260]: Link beat detected.

Sep 25 14:31:11 Tower ifplugd(eth0)[1260]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

Sep 25 14:31:11 Tower ifplugd(eth0)[1260]: client: Polling for DHCP server on interface eth0:

Sep 25 14:31:12 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 30 -h Tower eth0

Sep 25 14:31:12 Tower kernel: e1000e 0000:01:00.0: irq 28 for MSI/MSI-X

Sep 25 14:31:12 Tower kernel: e1000e 0000:01:00.0: irq 28 for MSI/MSI-X

Sep 25 14:31:12 Tower dhcpcd[2161]: broadcasting DHCP_DISCOVER

Sep 25 14:31:15 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

Sep 25 14:31:17 Tower dhcpcd[2161]: dhcpIPaddrLeaseTime=1123200 in DHCP server response.

Sep 25 14:31:17 Tower dhcpcd[2161]: DHCP_OFFER received from (192.168.178.1)

Sep 25 14:31:17 Tower dhcpcd[2161]: broadcasting DHCP_REQUEST for 192.168.178.24

Sep 25 14:31:17 Tower dhcpcd[2161]: dhcpIPaddrLeaseTime=1123200 in DHCP server response.

Sep 25 14:31:17 Tower dhcpcd[2161]: DHCP_ACK received from (192.168.178.1)

Sep 25 14:31:17 Tower ifplugd(eth0)[1260]: client: dhcpcd: MAC address = 00:18:f3:c6:56:c3

Sep 25 14:31:17 Tower ifplugd(eth0)[1260]: client: dhcpcd: your IP address = 192.168.178.24

Sep 25 14:31:17 Tower ifplugd(eth0)[1260]: client: dhcpcd: MAC address = 00:18:f3:c6:56:c3

Sep 25 14:31:17 Tower ifplugd(eth0)[1260]: client: dhcpcd: your IP address = 192.168.178.24

Sep 25 14:31:18 Tower ifplugd(eth0)[1260]: Program executed successfully.

Sep 25 14:32:00 Tower cache_dirs: ==============================================

Sep 25 14:32:00 Tower cache_dirs: command-args=-w -m 3 -M 5 -d 4 -a -noleaf

Sep 25 14:32:00 Tower cache_dirs: vfs_cache_pressure=10

Sep 25 14:32:00 Tower cache_dirs: max_seconds=5, min_seconds=3

Sep 25 14:32:00 Tower cache_dirs: max_depth=4

Sep 25 14:32:00 Tower cache_dirs: command=find -noleaf

Sep 25 14:32:00 Tower cache_dirs: version=1.6.5

Sep 25 14:32:00 Tower cache_dirs: ---------- caching directories ---------------

Sep 25 14:32:00 Tower cache_dirs: Filme

Sep 25 14:32:00 Tower cache_dirs: Programme

Sep 25 14:32:00 Tower cache_dirs: Serien

Sep 25 14:32:00 Tower cache_dirs: ----------------------------------------------

Sep 25 14:32:00 Tower cache_dirs: cache_dirs process ID 2214 started, To terminate it, type: cache_dirs -q

Sep 25 14:32:22 Tower kernel: REISERFS (device md2): replayed 252 transactions in 74 seconds

Sep 25 14:32:22 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

 

 

any help is appreciated!

thank you

  • Author

could anyone explain those errors to me?

i have marked them in bold for better reading.

 

 

they are occuring after every reboot / boot

 

 

i dont know how this could effect my system or how urgent it is.

besides everything else runs smooth

could anyone explain those errors to me?

i have marked them in bold for better reading.

 

 

they are occuring after every reboot / boot

 

 

i dont know how this could effect my system or how urgent it is.

besides everything else runs smooth

First error.  Your motherboard BIOS has an incorrect checksum in one of its table.  This fairly common.  Only solution is to see if a BIOS update is available.  It is an error message you can ignore.

 

The second set of message seem to be registering the power button and cpu clock for CPU1 and CPU2 and they've already been registered.  (You probably have a multi-core CPU)  These too can be ignored.

 

The third message is also very normal.  It indicates that some of the joutnal transactions on the file-system were not commited before you last shut down and they were re-played before the file-system could be mounted. 

 

During those 74 seconds your display on the management console probably said "mounting" if on a current version of unRAID or "unformatted" if on an older version.  I've seen that same process of re-playing journal transactions take as long as 15 minutes on one of my servers when re-booted after a hard-crash on a power failure.  During that time you can't get to your files, since the file-system is not yet mounted, but don't panic, it is just doing its job of protecting your data. 

 

Joe L.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.