Hey guys,

 

I was wondering why my parity-check is freezing at 50+%? Ive already dont this 3 times already and it just freezes there. The ETA just doesnt update anymore as well. So im stuck.

 

 

sobnology-diagnostics-20220606-1942.zip

This disk apparently not used is spamming the log with constant errors:

 

Jun  5 21:44:29 sobnology emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N1SVT0RH (sdl) 512 5860533168

 

Disconnect it then please post new diags after a re-start.

4 hours ago, JorgeB said:

This disk apparently not used is spamming the log with constant errors:

 

Jun  5 21:44:29 sobnology emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N1SVT0RH (sdl) 512 5860533168

 

Disconnect it then please post new diags after a re-start.

The spam stopped lol thanks!

sobnology-diagnostics-20220607-0038.zip

Good, now start a check and post new diags after it freezes, I assume only the check freezes, not the server?

yeah just the parity-check freezes everything is fine. also the docker apps doesnt work. even made a new docker image.

sobnology-diagnostics-20220607-0950.zip

just noticed 2 of my shares went missing. thats actually where this all started. shares missing.

It could be because one drive was dropped and reconnected with another ID ?

 

Jun  7 09:12:39 sobnology emhttpd: error: hotplug_devices, 1719: No such file or directory (2): Error: tagged device WDC_WD40EFAX-68JH4N0_WD-WX42D10HZ4Y5 was (sdl) is now (sdo)
Jun  7 09:12:39 sobnology emhttpd: read SMART /dev/sdo
Jun  7 09:12:39 sobnology kernel: emhttpd[9123]: segfault at 618 ip 0000000000413e00 sp 00007ffc61d1f590 error 4 in emhttpd[403000+1d000]
Jun  7 09:12:39 sobnology kernel: Code: c0 75 15 48 c7 45 f8 84 41 42 00 48 c7 45 f0 73 41 42 00 e9 50 01 00 00 8b 45 ec 89 c7 e8 42 ba ff ff 48 89 45 d8 48 8b 45 d8 <8b> 80 18 06 00 00 85 c0 74 17 48 8b 45 d8 48 8b 80 68 06 00 00 48

 

1 hour ago, ChatNoir said:

It could be because one drive was dropped and reconnected with another ID ?

 

Jun  7 09:12:39 sobnology emhttpd: error: hotplug_devices, 1719: No such file or directory (2): Error: tagged device WDC_WD40EFAX-68JH4N0_WD-WX42D10HZ4Y5 was (sdl) is now (sdo)
Jun  7 09:12:39 sobnology emhttpd: read SMART /dev/sdo
Jun  7 09:12:39 sobnology kernel: emhttpd[9123]: segfault at 618 ip 0000000000413e00 sp 00007ffc61d1f590 error 4 in emhttpd[403000+1d000]
Jun  7 09:12:39 sobnology kernel: Code: c0 75 15 48 c7 45 f8 84 41 42 00 48 c7 45 f0 73 41 42 00 e9 50 01 00 00 8b 45 ec 89 c7 e8 42 ba ff ff 48 89 45 d8 48 8b 45 d8 <8b> 80 18 06 00 00 85 c0 74 17 48 8b 45 d8 48 8b 80 68 06 00 00 48

 

this is actually a 4tb cache drive (not ssd). and the 2 shares that are missing are supposed to use the said drive for cache.

Edited June 7, 20224 yr by karlpox

Jun  7 09:44:11 sobnology smbd[2595]: [2022/06/07 09:44:11.445928,  0] ../../source3/smbd/service.c:787(make_connection_snum)
Jun  7 09:44:11 sobnology smbd[2595]:   make_connection_snum: canonicalize_connect_path failed for service Backup, path /mnt/user/Backup
Jun  7 09:44:11 sobnology smbd[2595]: [2022/06/07 09:44:11.446657,  0] ../../source3/smbd/service.c:787(make_connection_snum)
Jun  7 09:44:11 sobnology smbd[2595]:   make_connection_snum: canonicalize_connect_path failed for service Downloads, path /mnt/user/Downloads

 

I assume these are the two shares you lost access? I see the errors but not the reason for them.

 

There's also still a lot of docker related log spam, you might want to try and find which docker is constantly doing this:

 

Jun  7 09:49:43 sobnology kernel: docker0: port 1(veth85c9d7c) entered blocking state
Jun  7 09:49:43 sobnology kernel: docker0: port 1(veth85c9d7c) entered disabled state
Jun  7 09:49:43 sobnology kernel: device veth85c9d7c entered promiscuous mode
Jun  7 09:49:43 sobnology kernel: docker0: port 1(veth85c9d7c) entered blocking state
Jun  7 09:49:43 sobnology kernel: docker0: port 1(veth85c9d7c) entered forwarding state
Jun  7 09:49:43 sobnology kernel: docker0: port 1(veth85c9d7c) entered disabled state
Jun  7 09:49:44 sobnology kernel: eth0: renamed from veth84f21e4