[Dynamic memory for virtual machines -- how is this actually designed to work?]

 

[tty1: input overrun]

On 1/5/2014 at 10:44 PM, zoggy said:

came back from the holidays and found my log was quite full with the same message.. turned out that something fell and landed on the keyboard that was attached...

the joys of not having email notices or any logic to say.. hey that line thats repeating a zillion times in the log.. maybe we should notify the user that something is up.

 

Dec 14 07:31:41 husky logger: mover finished
Dec 14 07:33:34 husky agetty[27087]: tty1: input overrun
Dec 14 07:39:13 husky agetty[27169]: tty1: input overrun
Dec 14 07:44:51 husky agetty[27170]: tty1: input overrun
Dec 14 07:50:30 husky agetty[27172]: tty1: input overrun
Dec 14 07:56:09 husky agetty[27351]: tty1: input overrun
...
Dec 17 01:41:46 husky agetty[5261]: tty1: input overrun
Dec 17 01:47:25 husky agetty[5262]: tty1: input overrun
Dec 17 01:53:04 husky agetty[5396]: tty1: input overrun
Dec 17 01:58:42 husky agetty[5397]: tty1: input overrun
Dec 17 02:04:21 husky agetty[5398]: tty1: input overrun
Dec 17 02:10:00 husky agetty[5400]: tty1: input overrun
Dec 17 02:15:39 husky agetty[5401]: tty1: input overrun
Dec 17 02:21:17 husky agetty[5402]: tty1: input overrun
Dec 17 02:26:56 husky agetty[5403]: tty1: input overrun
Dec 17 02:32:35 husky agetty[5404]: tty1: input overrun
Dec 17 02:38:13 husky agetty[5405]: tty1: input overrun
...
Dec 20 16:43:06 husky agetty[18333]: tty1: input overrun
Dec 20 16:48:45 husky agetty[18354]: tty1: input overrun
Dec 20 16:54:23 husky agetty[18473]: tty1: input overrun
Dec 20 17:00:02 husky agetty[18475]: tty1: input overrun
Dec 20 17:05:41 husky agetty[18476]: tty1: input overrun
Dec 20 17:11:19 husky agetty[18477]: tty1: input overrun
Dec 20 17:16:58 husky agetty[18478]: tty1: input overrun
Dec 20 17:22:37 husky agetty[18479]: tty1: input overrun
Dec 20 17:28:15 husky agetty[18481]: tty1: input overrun
Dec 20 17:30:59 husky shfs/user: cache disk full
Dec 20 17:33:54 husky agetty[18482]: tty1: input overrun
Dec 20 17:39:33 husky agetty[18486]: tty1: input overrun
Dec 20 17:45:11 husky agetty[18487]: tty1: input overrun
Dec 20 17:50:50 husky agetty[18488]: tty1: input overrun
Dec 20 17:56:29 husky agetty[18608]: tty1: input overrun
Dec 20 18:02:08 husky agetty[18609]: tty1: input overrun
Dec 20 18:07:46 husky agetty[18611]: tty1: input overrun
Dec 20 18:13:25 husky agetty[18612]: tty1: input overrun
Dec 20 18:19:04 husky agetty[18614]: tty1: input overrun
Dec 20 18:24:42 husky agetty[18616]: tty1: input overrun
Dec 20 18:30:21 husky agetty[18617]: tty1: input overrun
Dec 20 18:36:00 husky agetty[18619]: tty1: input overrun
Dec 20 18:41:38 husky agetty[18620]: tty1: input overrun
Dec 20 18:47:17 husky agetty[18622]: tty1: input overrun
Dec 20 18:52:56 husky agetty[18741]: tty1: input overrun
Dec 20 18:58:34 husky agetty[18743]: tty1: input overrun
Dec 20 19:03:00 husky shfs/user: cache disk full
...
Dec 31 23:22:50 husky agetty[27410]: tty1: input overrun
Dec 31 23:28:29 husky agetty[27412]: tty1: input overrun
Dec 31 23:34:07 husky agetty[27413]: tty1: input overrun
Dec 31 23:39:46 husky agetty[27415]: tty1: input overrun
Dec 31 23:45:25 husky agetty[27416]: tty1: input overrun
Dec 31 23:51:03 husky agetty[27417]: tty1: input overrun
Dec 31 23:56:42 husky agetty[27566]: tty1: input overrun
Jan  1 00:02:21 husky agetty[27567]: tty1: input overrun
Jan  1 00:07:59 husky agetty[27569]: tty1: input overrun
Jan  1 00:13:38 husky agetty[27570]: tty1: input overrun
Jan  1 00:19:17 husky agetty[27572]: tty1: input overrun

 

 

 

 

I just got this, any resolution?

[Unraid server going unresponsive]

There was a dead RAM stick.  Still crashing, but started a new post.

[New issues after old issues. Dying NVME?]

Hi all.

 

I recently posted about having weird crashes/freezes on my system.  I was able to finally find out I had a bad stick of RAM

 

However, I'm still having crashes, although less frequently.

Previously I've seen like 6 different looking crash logs... and now I'm seeing a whole new one.  Can you take a look and help me find out what i need to do.

 

Is this a dying NVME drive?

 

Dump0.txt shadowraid-diagnostics-20221013-1932.zip

[Unraid server going unresponsive]

Ok, it crashed again.  BUT overclocking the RAM made it last longer (for whatever reason).  The variablility of the crash dumps (especially including the address ones) should also have been a tip off.

 

Swapped the 4x16GB ram sticks to my wife's computer and did MEMTest and one of them is rapidly giving error messages.  Woohoo

[Unraid server going unresponsive]

On 10/3/2022 at 1:02 PM, JorgeB said:

Difficult to say, you can first try a different Unraid version, like v6.10.3, if you see the same issues with the very different kernel it's likely hardware.

 

 

Oct  2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32)
Oct  2 17:51:37 ShadowRaid kernel: device offline error, dev sda, sector 2080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Oct  2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32)
Oct  2 17:51:37 ShadowRaid kernel: device offline error, dev sda, sector 2080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Oct  2 17:51:37 ShadowRaid kernel: FAT-fs (sda1): FAT read failed (blocknr 32)

 

 

Silly as it sounds, I turned on XMP to overclock RAM and turned Disk SpinDown to Never.

Haven't had a lock-up yet.  Fingers crossed, but this is the longest in a good while I've had no freeze.

 

Edit: Still alive!  Hope I dont' Jinx it.

[Unraid server going unresponsive]

7 hours ago, JorgeB said:

Look more like a hardware issue, you are also having flash drive problems.

Can you detail this out more?

 

Dump 1 and 4 having identical dereference addresses makes me think that the hardware isn't failing due to "dying" but an invalid configuration maybe.  What kind of hardware issue are you thinking, how can I isolate and fix this?

 

What kind of flash drive problems?  What part of the diagnostics/dump makes you think so?  (I didn't see anything there, but I'm also clueless)

 

 

Thank you for your time 

[Unraid server going unresponsive]

Hello any/all.

 

For the longest time I've had this problem where my server would become completely unresponsive. For some unknown reason.  I did what the guide said and disabled C state and made sure no overclocking was done to the RAM, but the issue persists.

 

This freezing would only happen about once a couple times a month (lots of variation) so my "solution" was to connect a smart plug to it and it it it couldn't connect to the server, it would turn off and on rebooting the server.   Bad solution, but the only thing that worked.

 

Now the frequency has increased so much its hitting up to 4 times a day which is more than i can take, hence me begging for help here.

 

I've attached the diagnostics and 4 most recent crash logs.  

Dump 1 and Dump 4 look very similar.

Dump2.txt Dump3.txt Dump4.txt shadowraid-diagnostics-20221002-2201.zip Dump1.txt

[Virtualize a Rasberry Pi?]

+1