Since updating to 15e I've been getting a lot of this in my logs:

Dec 13 07:17:55 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp
Dec 13 07:17:59 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp
Dec 13 07:18:03 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp
Dec 13 07:18:07 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp
Dec 13 07:18:10 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp
Dec 13 07:18:15 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 2122.out.tmp

Diags attached.

IS it anything sinister? 

namek-diagnostics-20171213-0801.zip

Can you start your system in safemode and check again?

 

Ok give me a bit. 

Just heading to work

Actually I'll need to do it tonight when I get home. Will report back

Is there a way to tell the server to reboot into safemode without being home?

I can access the gui or ssh, just cant access the box itself or reboot menu.

Go to the flash device on the main page, scroll down to the syslinux.cfg editor. 

Then move the default menu entry to the safe mode part and save (Don't remember if there is a save button though). 

When you reboot, you should be booting into safe mode. 

7 minutes ago, saarg said:

Go to the flash device on the main page, scroll down to the syslinux.cfg editor. 

Then move the default menu entry to the safe mode part and save (Don't remember if there is a save button though). 

When you reboot, you should be booting into safe mode. 

Thanks man,

Shall I change prompt to 3 or 4?

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

Or do I have to move the labels around?

As I said, move only menu default to the safe mode label. 

Edited December 13, 20178 yr by saarg

4 minutes ago, saarg said:

As I said, move only menu default to the safe mode label. 

Sorry didnt see that option.

 

Moved it now, and rebooting.

Looks like I might have had an issue with Dynamix System Temp

Found an error for it, so ive removed the plugin now and lets see.

 

I'll report back

Edited December 13, 20178 yr by SavellM

Ok looks like I got a bunch more this morning.

 

Rebooting back to safe mode, and will let it run a day or 2 and see.

Think its got something to do with the mover as it only appears around when the mover runs.

Will get logs tomorrow

I have the same, ppl said its bc of bad sata controller, did you find out what happend?

Running in safe mode I havent had this issue return... so not sure.

Gonna upgrade to 16b reboot to normal and try again

Still getting these when i reboot to normal and even upgraded to 16b

Still getting this and it seems to happen after mover runs:

Dec 23 03:40:01 Namek root: mover: started
Dec 23 03:40:01 Namek root: mover: finished
Dec 23 05:00:43 Namek root: /var/lib/docker: 33.4 GiB (35841597440 bytes) trimmed
Dec 23 05:00:43 Namek root: /mnt/cache: 808.5 GiB (868122525696 bytes) trimmed
Dec 23 07:57:34 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 744.out.tmp
Dec 23 07:57:39 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 744.out.tmp
Dec 23 07:57:44 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 744.out.tmp
Dec 23 08:13:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 781.out.tmp
Dec 23 08:13:34 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 781.out.tmp

Dec 24 03:40:01 Namek root: mover: started
Dec 24 03:40:01 Namek root: mover: finished
Dec 24 05:00:43 Namek root: /var/lib/docker: 33.4 GiB (35820986368 bytes) trimmed
Dec 24 05:00:43 Namek root: /mnt/cache: 861 GiB (924416434176 bytes) trimmed
Dec 24 06:43:29 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 1168.out.tmp
Dec 24 06:43:35 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 1168.out.tmp
Dec 24 06:43:41 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 1168.out.tmp
Dec 24 06:43:45 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 1168.out.tmp

Not sure if this is anything to go by?

But it only started happening from rc15 onwards.

 

All apps and dockers updated.

I'll report my safe mode in a few days.

 

Diags attached for now tho.

namek-diagnostics-20171224-1009.zip

Been running now for 1.3 days and so far so good on Safe Mode.

 

I'll leave it running in safe mode for a little bit longer and see if it returns.

Still getting it even in Safe Mode, just less frequently:

Dec 27 03:40:01 Namek root: mover: started
Dec 27 03:40:01 Namek root: mover: finished
Dec 27 05:00:44 Namek root: /var/lib/docker: 33.3 GiB (35780632576 bytes) trimmed
Dec 27 05:00:44 Namek root: /mnt/cache: 858.1 GiB (921423069184 bytes) trimmed
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:31 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:32 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:32 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp
Dec 27 07:57:32 Namek shfs: error: shfs_readdir, 1270: No such file or directory (2): fstatat: 4405.out.tmp

Fresh Diags attached.

Anyone know what it could be?

namek-diagnostics-20171227-2203.zip

u have sonarr running? Check logs of sonarr...

17 hours ago, nuhll said:

u have sonarr running? Check logs of sonarr...

I have Sonarr and Radarr, but neither show much in the logs.

 

Unless there are some specific logs you want me to look at in appdata or something?

Oh geez just noticed this:

Dec 28 00:56:45 Namek kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Dec 28 00:56:45 Namek kernel: ata1.00: failed command: READ DMA EXT
Dec 28 00:56:45 Namek kernel: ata1.00: cmd 25/00:78:a0:82:47/00:03:08:00:00/e0 tag 22 dma 454656 in
Dec 28 00:56:45 Namek kernel:         res 50/00:00:9f:82:47/00:00:08:00:00/e0 Emask 0x10 (ATA bus error)
Dec 28 00:56:45 Namek kernel: ata1.00: status: { DRDY }
Dec 28 00:56:45 Namek kernel: ata1: hard resetting link
Dec 28 00:56:45 Namek kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 28 00:56:45 Namek kernel: ata1.00: configured for UDMA/133
Dec 28 00:56:45 Namek kernel: ata1: EH complete
Dec 28 00:56:56 Namek kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Dec 28 00:56:56 Namek kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Dec 28 00:56:56 Namek kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Dec 28 00:56:56 Namek kernel: ata1.00: failed command: READ DMA EXT
Dec 28 00:56:56 Namek kernel: ata1.00: cmd 25/00:40:e8:e4:4b/00:05:08:00:00/e0 tag 11 dma 688128 in
Dec 28 00:56:56 Namek kernel:         res 50/00:00:e7:e4:4b/00:00:08:00:00/e0 Emask 0x10 (ATA bus error)
Dec 28 00:56:56 Namek kernel: ata1.00: status: { DRDY }
Dec 28 00:56:56 Namek kernel: ata1: hard resetting link
Dec 28 00:56:56 Namek kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 28 00:56:56 Namek kernel: ata1.00: configured for UDMA/133
Dec 28 00:56:56 Namek kernel: ata1: EH complete
Dec 28 01:05:46 Namek kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Dec 28 01:05:46 Namek kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Dec 28 01:05:46 Namek kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Dec 28 01:05:46 Namek kernel: ata1.00: failed command: READ DMA EXT
Dec 28 01:05:46 Namek kernel: ata1.00: cmd 25/00:40:c0:c4:02/00:05:09:00:00/e0 tag 17 dma 688128 in
Dec 28 01:05:46 Namek kernel:         res 50/00:00:b7:b3:02/00:00:09:00:00/e0 Emask 0x10 (ATA bus error)
Dec 28 01:05:46 Namek kernel: ata1.00: status: { DRDY }
Dec 28 01:05:46 Namek kernel: ata1: hard resetting link
Dec 28 01:05:46 Namek kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Dec 28 01:05:46 Namek kernel: ata1.00: configured for UDMA/133
Dec 28 01:05:46 Namek kernel: ata1: EH complete
Dec 28 01:06:45 Namek kernel: ata1: limiting SATA link speed to 3.0 Gbps
Dec 28 01:06:45 Namek kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Dec 28 01:06:45 Namek kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Dec 28 01:06:45 Namek kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Dec 28 01:06:45 Namek kernel: ata1.00: failed command: READ DMA EXT
Dec 28 01:06:45 Namek kernel: ata1.00: cmd 25/00:40:08:cb:3d/00:05:09:00:00/e0 tag 5 dma 688128 in
Dec 28 01:06:45 Namek kernel:         res 50/00:00:d7:bc:f4/00:00:3e:00:00/e0 Emask 0x10 (ATA bus error)
Dec 28 01:06:45 Namek kernel: ata1.00: status: { DRDY }
Dec 28 01:06:45 Namek kernel: ata1: hard resetting link
Dec 28 01:06:45 Namek kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Dec 28 01:06:45 Namek kernel: ata1.00: configured for UDMA/133
Dec 28 01:06:45 Namek kernel: ata1: EH complete

namek-diagnostics-20171228-1749.zip

Edited December 28, 20178 yr by SavellM

That's a bad SATA cable (or backplane).

7 hours ago, johnnie.black said:

That's a bad SATA cable (or backplane).

Great!

 

Reset all sata cables. 

But think it's my mobo, will start an RMA. 

 

Alternatively can you recommend a good JBOD PCI SATA card?

For maybe 8 drives?

Any LSI SAS2008/2308/3008 based controller, e.g. 9201-8i, 9211-8i, 9207-8i, 9300-8i etc

Cheers bud