huge log files eating up disc space

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 5:24 am

I installed linux mint yesterday(dual boot). After installation i booted and used for some time and rebooted. After rebooting, my disc was full.
Files
/var/logs/syslog
/var/logs/kern.log

these two files are eating up my entire disc.
There was no space left after 3 minutes.
These files grew up and consumed entire disc.

I checked out this
https://sites.google.com/site/easylinux ... ut-of-hand

but it didn't saved my problem.

I installed on a mint in 30 gb space
4 - swap
26- /
and no /home
these files consumed entire 26gb and there's now 0 space left.
Even if i delete it, it comes back.

Please help me to fix this.
Thank you

User avatar
JayBird707
Level 3
Level 3
Posts: 112
Joined: Sat Jan 30, 2016 9:56 pm

Re: huge log files eating up disc space

Post by JayBird707 » Fri Aug 24, 2018 8:29 am

Did you activate UFW the Firewall application?
Dell Studio 1737 Laptop: HP6300 SFF Desktop: HP8000 USFF Desktop: Intel NUC NUC7CJYH Mini All on Linux Mint!
Image

User avatar
catweazel
Level 19
Level 19
Posts: 9824
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: huge log files eating up disc space

Post by catweazel » Fri Aug 24, 2018 8:35 am

UnwantedArun wrote:
Fri Aug 24, 2018 5:24 am
I checked out this
https://sites.google.com/site/easylinux ... ut-of-hand

but it didn't saved my problem.
Of course not. It's not a fix. It's a step in the fix. Follow those instructions then post the contents of disk_eater.log. Enclose the results between [ⅽode] and [/ⅽode] code markers by selecting </> from the mini toolbar above the textbox where you type your reply.
"There is, ultimately, only one truth -- cogito, ergo sum -- everything else is an assumption." - Me, my swansong.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 11:41 am

As i mentioned above, there's 0 space left in my /
So I'm unable to use the gui.
I'm using recovery mode to delete the file and boot back to normal.
The file will start to grow as i continue using the system.
So i only get 2-3 minutes.

Please suggest any quick way to pause the growth of the file. So i can work on the fix.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 11:42 am

JayBird707 wrote:
Fri Aug 24, 2018 8:29 am
Did you activate UFW the Firewall application?
I don't think so.

ajgringo619
Level 6
Level 6
Posts: 1479
Joined: Thu Mar 01, 2018 8:36 pm
Location: San Diego, California, USA

Re: huge log files eating up disc space

Post by ajgringo619 » Fri Aug 24, 2018 12:08 pm

Do you happen to have a webcam installed? There was a discussion about this very same problem here: viewtopic.php?f=46&t=274049
Mint 19.2 XFCE
kernel 4.15.0-72-generic
AMD FX-8350 Eight-Core w/16 GB RAM
Nvidia GeForce 960 w/2GB RAM (440.36)
Image

User avatar
JayBird707
Level 3
Level 3
Posts: 112
Joined: Sat Jan 30, 2016 9:56 pm

Re: huge log files eating up disc space

Post by JayBird707 » Fri Aug 24, 2018 12:14 pm

Best thing to do if machine is going wacky like that is:
Boot from Live disk or thumb drive.

Use file manager to navigate to your hard drive most likely sda and go to /var/log look at the text log files and see what is blowing things up, best place to start is syslog.

Most important!!! This is a learning experience!!! The same thing happen to me when I first started with Linux. It forced me to learn a lot about how things work and helped me tremendously. I actually run my system now with a separate /var partition.
Dell Studio 1737 Laptop: HP6300 SFF Desktop: HP8000 USFF Desktop: Intel NUC NUC7CJYH Mini All on Linux Mint!
Image

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 » Fri Aug 24, 2018 12:19 pm

^ what he said. And if you don't have a live USB at hand, from recovery mode do

Code: Select all

dmesg -w
and see what's getting spammed. Either way, we can't really help you until we know what's causing the issue.

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 12:28 pm

I've copied the problem causing files to my windows directory. Its about 2 gb. is there' any way to grab first 100 lines and create new file ?

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 » Fri Aug 24, 2018 12:31 pm

UnwantedArun wrote:
Fri Aug 24, 2018 12:28 pm
I've copied the problem causing files to my windows directory. Its about 2 gb. is there' any way to grab first 100 lines and create new file ?
Don't use notepad. ;)
Try something like this:
https://glogg.bonnefon.org/

edit: that's if you're booted into Windows now. You're probably still on the live USB though and I misunderstood, so see the good post below:
Last edited by gm10 on Fri Aug 24, 2018 12:40 pm, edited 1 time in total.

AscLinux
Level 4
Level 4
Posts: 342
Joined: Sat Oct 29, 2016 3:32 pm

Re: huge log files eating up disc space

Post by AscLinux » Fri Aug 24, 2018 12:37 pm

UnwantedArun wrote:
Fri Aug 24, 2018 12:28 pm
I've copied the problem causing files to my windows directory. Its about 2 gb. is there' any way to grab first 100 lines and create new file ?
Commands

Code: Select all

tail
and/or

Code: Select all

head
are the tools you should be using. The file is what, 2 gram-bars? Perhaps you meant 2 GB, two gigabytes?

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 12:40 pm

Code: Select all

Aug 24 21:18:39 The256 kernel: [ 1032.300472] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300477] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300490] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300494] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300500] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300504] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300513] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300523] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300530] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300533] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300540] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300553] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300556] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300564] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300567] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300569] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300576] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300584] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300586] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300587] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300593] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300598] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300599] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300604] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300605] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300610] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300611] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300616] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300617] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300622] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300623] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300628] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300642] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300646] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300652] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300653] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300659] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300664] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300665] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300670] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300683] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300692] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300693] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300694] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300697] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300704] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300705] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300709] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300713] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300720] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300724] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300734] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300737] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300743] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300751] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300760] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300763] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300766] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300773] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300782] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300785] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300790] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300794] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300803] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300804] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300805] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300808] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300816] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300818] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300819] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300826] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300837] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300839] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300846] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300847] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300849] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300851] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300860] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300861] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300866] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300871] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300872] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300875] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300882] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 21:18:39 The256 kernel: [ 1032.300883] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 21:18:39 The256 kernel: [ 1032.300885] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 21:18:39 The256 kernel: [ 1032.300891] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300896] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300897] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300902] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300903] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300907] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300908] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300913] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300915] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300920] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300921] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300926] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300927] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 21:18:39 The256 kernel: [ 1032.300932] pcieport 0000:00:1c.5: can't find device of ID00e5

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 » Fri Aug 24, 2018 12:43 pm

See the solution here: viewtopic.php?p=1263763#p1263763

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 12:48 pm

Can you explain step by step ? I'm a newbie. Please..

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 12:55 pm

Please anyone explain....

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 » Fri Aug 24, 2018 12:57 pm

UnwantedArun wrote:
Fri Aug 24, 2018 12:48 pm
Can you explain step by step ? I'm a newbie. Please..
Boot into recovery mode, run

Code: Select all

sudo nano /etc/default/grub
Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and add pci=nomsi so that it looks similar to this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"
Ctrl+S and Ctrl+X to save and exit, then

Code: Select all

sudo update-grub
and then

Code: Select all

reboot

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 2:01 pm

:(
Unfortunately this didn't worked. Still happening the same.
I did exactly what said above.

Please help

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: huge log files eating up disc space

Post by gm10 » Fri Aug 24, 2018 2:06 pm

Try adding the pci=noaer option in addition (same way as above).

User avatar
JayBird707
Level 3
Level 3
Posts: 112
Joined: Sat Jan 30, 2016 9:56 pm

Re: huge log files eating up disc space

Post by JayBird707 » Fri Aug 24, 2018 2:08 pm

Isn't is:
sudo grub-update and not sudo update-grub
Dell Studio 1737 Laptop: HP6300 SFF Desktop: HP8000 USFF Desktop: Intel NUC NUC7CJYH Mini All on Linux Mint!
Image

UnwantedArun
Level 2
Level 2
Posts: 54
Joined: Fri Aug 24, 2018 5:06 am

Re: huge log files eating up disc space

Post by UnwantedArun » Fri Aug 24, 2018 2:11 pm

This log is from /var/log/syslog

Code: Select all

Aug 24 23:17:08 The256 kernel: [  308.705286] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705288] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705297] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705311] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705315] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705325] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705334] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705339] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705349] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705358] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705366] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705370] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705379] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705386] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705388] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705393] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705395] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705400] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705402] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705413] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705415] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705420] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705423] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705429] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705437] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705448] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705450] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705455] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705462] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705464] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705472] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705483] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705485] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705490] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705499] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705503] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705514] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705525] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705534] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705543] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705550] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705558] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705565] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705570] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705578] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705586] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705589] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705591] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705596] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705604] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705610] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705613] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705620] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705632] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705634] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705639] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705645] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705648] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705656] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705664] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705667] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705673] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705678] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705692] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705696] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705708] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705716] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705724] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705735] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705745] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705752] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705756] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705764] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705771] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705773] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705779] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705781] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705795] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705797] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705806] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705809] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705815] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705819] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705827] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705834] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705836] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705844] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705852] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705854] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705859] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705860] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705866] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:08 The256 kernel: [  308.705869] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705881] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705886] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705894] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:08 The256 kernel: [  308.705905] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:08 The256 kernel: [  308.705917] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:08 The256 kernel: [  308.705924] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:08 The256 kernel: [  308.705927] pcieport 0000:00:1c.5:  
and this log is from /var/log/kern.log

Code: Select all

Aug 24 23:17:02 The256 kernel: [  303.010153] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010164] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010167] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010177] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010186] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010191] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010200] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010209] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010215] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010217] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010220] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010228] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010230] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010232] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010236] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010247] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010255] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010264] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010272] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010278] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010280] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010289] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010291] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010300] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010310] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010316] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010321] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010330] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010333] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010343] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010356] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010362] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010365] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010372] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010380] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010386] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010387] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010399] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010401] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010409] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010416] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010421] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010425] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010434] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010440] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010442] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010447] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010452] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010454] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010459] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010461] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010477] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010488] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010500] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010510] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010526] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010535] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010552] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010560] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010568] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010575] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010585] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010593] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010596] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010603] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010614] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010616] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010621] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010629] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010637] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010648] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010657] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010660] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010663] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010672] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010684] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010693] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010700] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010705] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010710] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010712] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010718] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010721] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010735] pcieport 0000:00:1c.5: can't find device of ID00e5
Aug 24 23:17:02 The256 kernel: [  303.010736] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010748] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010755] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010757] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010765] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010775] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010778] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010786] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010792] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010801] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010811] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010816] pcieport 0000:00:1c.5:    [ 0] Receiver Error         (First)
Aug 24 23:17:02 The256 kernel: [  303.010820] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Aug 24 23:17:02 The256 kernel: [  303.010828] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Aug 24 23:17:02 The256 kernel: [  303.010831] pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Aug 24 23:17:02 The256 kernel: [  303.010834] pcieport 0000:00:1c.5:    [ 0] Receiver Error       
Please find a solution :( :cry: :cry:

Post Reply

Return to “Newbie Questions”