cbr600ds2

I hate to jump in a bit late so I think I'm following. I just had a weird question related - if I delete an excluded/included and it starts writing to more than one disk (like it should eventually) when something accesses that share it will spin up both drive's correct?

Hello - Why does it read what it is but not able to work? I tried a few different bays. Sep 29 17:14:06 Skynet kernel: sd 11:0:23:0: [sdw] Spinning up disk... Sep 29 17:14:22 Skynet kernel: sd 11:0:23:0: [sdw] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Sep 29 17:14:22 Skynet kernel: sd 11:0:23:0: [sdw] Write Protect is off Sep 29 17:14:22 Skynet kernel: sd 11:0:23:0: [sdw] Mode Sense: db 00 10 08 Sep 29 17:14:22 Skynet kernel: sd 11:0:23:0: [sdw] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 29 17:14:22 Skynet kernel: sd 11:0:23:0: [sdw] Attached SCSI disk Sep 29 17:42:29 Skynet kernel: sd 11:0:23:0: [sdw] Synchronizing SCSI cache Sep 29 17:42:29 Skynet kernel: sd 11:0:23:0: [sdw] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Sep 29 17:42:34 Skynet kernel: sd 11:0:26:0: [sdw] Spinning up disk... Sep 29 17:42:45 Skynet kernel: sd 11:0:26:0: [sdw] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Sep 29 17:42:45 Skynet kernel: sd 11:0:26:0: [sdw] Write Protect is off Sep 29 17:42:45 Skynet kernel: sd 11:0:26:0: [sdw] Mode Sense: db 00 10 08 Sep 29 17:42:45 Skynet kernel: sd 11:0:26:0: [sdw] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 29 17:42:45 Skynet kernel: sd 11:0:26:0: [sdw] Attached SCSI disk Sep 29 17:43:28 Skynet emhttpd: ST4000NM0023_Z1Z86TQP0000C5320ZHJ_35000c50063783337 (sdw) 512 7814037168 Sep 29 17:43:28 Skynet emhttpd: read SMART /dev/sdw Sep 29 17:43:56 Skynet kernel: sd 11:0:26:0: [sdw] Synchronizing SCSI cache Sep 29 17:43:56 Skynet kernel: sd 11:0:26:0: [sdw] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Sep 29 17:44:18 Skynet kernel: sd 11:0:27:0: [sdw] Spinning up disk... Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Read Capacity(16) failed: Result: hostbyte=0x01 driverbyte=0x00 Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Sense not available. Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Read Capacity(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Sense not available. Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] 0 512-byte logical blocks: (0 B/0 B) Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] 0-byte physical blocks Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Write Protect is off Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Mode Sense: 00 00 00 00 Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Asking for cache data failed Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Assuming drive cache: write through Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00 Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Sense not available. Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00 Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Sense not available. Sep 29 17:45:13 Skynet kernel: sd 11:0:27:0: [sdw] Attached SCSI disk Sep 29 17:45:20 Skynet kernel: sd 11:0:28:0: [sdw] Spinning up disk... Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Sense Key : 0x2 [current] [descriptor] Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] ASC=0x4 ASCQ=0x1 Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Sense Key : 0x2 [current] [descriptor] Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] ASC=0x4 ASCQ=0x1 Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] 0 512-byte logical blocks: (0 B/0 B) Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] 0-byte physical blocks Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Test WP failed, assume Write Enabled Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Asking for cache data failed Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Assuming drive cache: write through Sep 29 17:47:01 Skynet kernel: sd 11:0:28:0: [sdw] Spinning up disk... Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08 Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] Sense Key : 0x2 [current] [descriptor] Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] ASC=0x4 ASCQ=0x0 Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08 Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] Sense Key : 0x2 [current] [descriptor] Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] ASC=0x4 ASCQ=0x0 Sep 29 17:48:41 Skynet kernel: sd 11:0:28:0: [sdw] Attached SCSI disk

Hello - I, too, wondered about this as well.. I also had a question about some of the settings. Should I just use all of the autodetected settings? I really shouldn't make any changes to it or...can I??

I have my embyserver appdata on a small 512MB NVME drive. If I get another NVME drive (say same drive just for explanation purposes) and move appdata to that exclusively do you think it will speed up embyserver performance or not really?

Second run worked but for some reason even though every thing said preclear completed successfully it still acted on the main page like it was running. Log and viewer all said completed. Thanks @trurl !

Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdw Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Preclear Disk Version: 1.0.22 Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: S.M.A.R.T. info type: default Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: S.M.A.R.T. attrs type: default Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Disk size: 8001563222016 Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Disk blocks: 1953506646 Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Blocks (512 bytes): 15628053168Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Block size: 4096 Aug 31 14:11:57 preclear_disk_ZA12PD7W_13451: Start sector: 0Aug 31 14:11:59 preclear_disk_ZA12PD7W_13451: Pre-read: pre-read verification started (1/5).... Aug 31 14:11:59 preclear_disk_ZA12PD7W_13451: Pre-Read: dd if=/dev/sdw of=/dev/null bs=2097152 skip=0 count=8001563222016 conv=noerror iflag=nocache,count_bytes,skip_bytes This is the log from the restart but I guess I didn't. The report showed smart passed and just said zeroing failed. I guess I'll have to see what the second try does. Sorry for not providing the correct information.

umm.... Anyone get this notification? Long story short - Zeroing failed using GFjardim. I've never had it happen to me. Thoughts? I'm running it again just to see maybe it was a weird one time thing.

Yeah - I have a downloads share and it's the only share with access to actual disk number 18. All of the shares have disk 18 as excluded. The downloads share included disk is 18. It's filling up so I'm trying to figure out how to be able to increase the actual usage. *shrug*

Any thoughts on moving data within the array to a different disk? Krusader would work or use unbalance to move....

I haven't done it yet. I wanted to get some more info before... screwing it up. hahaha Thanks.

Hello- so one of my shares is writing to a specific drive and that drive only - I have a question. 1. if I change the share setting in the include a new disk section will it automatically write the files over to that disk? Any other sort of tips/tricks any would like to share?

I'm trying to figure that out myself but i'm curious how cool an actual water block really gets and whether that would make sense or fit. If I thnk of something I'll def. let you know!

So it seems like its just the CPU that's water cooled and the HDD's are still air cooled, correct? Have you thought of routing something to cool the HDD's?

Handbrake has been working great but with the new OS upgrade (I haven't upgraded and still at 6.9.1) it seems like it shuts off every night. Is anyone experiencing this? Seems like something is causing it to end. 11/08/2021 20:53:11 passing arg to libvncserver: -rfbport 11/08/2021 20:53:11 passing arg to libvncserver: 5900 11/08/2021 20:53:11 passing arg to libvncserver: -rfbportv6 11/08/2021 20:53:11 passing arg to libvncserver: -1 11/08/2021 20:53:11 passing arg to libvncserver: -httpportv6 11/08/2021 20:53:11 passing arg to libvncserver: -1 11/08/2021 20:53:11 passing arg to libvncserver: -desktop 11/08/2021 20:53:11 passing arg to libvncserver: HandBrake 11/08/2021 20:53:11 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 1068 11/08/2021 20:53:11 Using X display :0 11/08/2021 20:53:11 rootwin: 0x43 reswin: 0x400001 dpy: 0xf9db0b40 11/08/2021 20:53:11 11/08/2021 20:53:11 ------------------ USEFUL INFORMATION ------------------ 11/08/2021 20:53:11 X DAMAGE available on display, using it for polling hints. 11/08/2021 20:53:11 To disable this behavior use: '-noxdamage' 11/08/2021 20:53:11 11/08/2021 20:53:11 Most compositing window managers like 'compiz' or 'beryl' 11/08/2021 20:53:11 cause X DAMAGE to fail, and so you may not see any screen 11/08/2021 20:53:11 updates via VNC. Either disable 'compiz' (recommended) or 11/08/2021 20:53:11 supply the x11vnc '-noxdamage' command line option. 11/08/2021 20:53:11 X COMPOSITE available on display, using it for window polling. 11/08/2021 20:53:11 To disable this behavior use: '-noxcomposite' 11/08/2021 20:53:11 11/08/2021 20:53:11 Wireframing: -wireframe mode is in effect for window moves. 11/08/2021 20:53:11 If this yields undesired behavior (poor response, painting 11/08/2021 20:53:11 errors, etc) it may be disabled: 11/08/2021 20:53:11 - use '-nowf' to disable wireframing completely. 11/08/2021 20:53:11 - use '-nowcr' to disable the Copy Rectangle after the 11/08/2021 20:53:11 moved window is released in the new position. 11/08/2021 20:53:11 Also see the -help entry for tuning parameters. 11/08/2021 20:53:11 You can press 3 Alt_L's (Left "Alt" key) in a row to 11/08/2021 20:53:11 repaint the screen, also see the -fixscreen option for 11/08/2021 20:53:11 periodic repaints. 11/08/2021 20:53:11 GrabServer control via XTEST. 11/08/2021 20:53:11 11/08/2021 20:53:11 Scroll Detection: -scrollcopyrect mode is in effect to 11/08/2021 20:53:11 use RECORD extension to try to detect scrolling windows 11/08/2021 20:53:11 (induced by either user keystroke or mouse input). 11/08/2021 20:53:11 If this yields undesired behavior (poor response, painting 11/08/2021 20:53:11 errors, etc) it may be disabled via: '-noscr' 11/08/2021 20:53:11 Also see the -help entry for tuning parameters. 11/08/2021 20:53:11 You can press 3 Alt_L's (Left "Alt" key) in a row to 11/08/2021 20:53:11 repaint the screen, also see the -fixscreen option for 11/08/2021 20:53:11 periodic repaints. 11/08/2021 20:53:11 11/08/2021 20:53:11 XKEYBOARD: number of keysyms per keycode 7 is greater 11/08/2021 20:53:11 than 4 and 51 keysyms are mapped above 4. 11/08/2021 20:53:11 Automatically switching to -xkb mode. 11/08/2021 20:53:11 If this makes the key mapping worse you can 11/08/2021 20:53:11 disable it with the "-noxkb" option. 11/08/2021 20:53:11 Also, remember "-remap DEAD" for accenting characters. 11/08/2021 20:53:11 11/08/2021 20:53:11 X FBPM extension not supported. Xlib: extension "DPMS" missing on display ":0". 11/08/2021 20:53:11 X display is not capable of DPMS. 11/08/2021 20:53:11 -------------------------------------------------------- 11/08/2021 20:53:11 11/08/2021 20:53:11 Default visual ID: 0x21 11/08/2021 20:53:11 Read initial data from X display into framebuffer. 11/08/2021 20:53:11 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 11/08/2021 20:53:11 11/08/2021 20:53:11 X display :0 is 32bpp depth=24 true color 11/08/2021 20:53:11 11/08/2021 20:53:11 Listening for VNC connections on TCP port 5900 11/08/2021 20:53:11 11/08/2021 20:53:11 Xinerama is present and active (e.g. multi-head). 11/08/2021 20:53:11 Xinerama: number of sub-screens: 1 11/08/2021 20:53:11 Xinerama: no blackouts needed (only one sub-screen) 11/08/2021 20:53:11 11/08/2021 20:53:11 fb read rate: 1875 MB/sec 11/08/2021 20:53:11 fast read: reset -wait ms to: 10 11/08/2021 20:53:11 fast read: reset -defer ms to: 10 11/08/2021 20:53:11 The X server says there are 10 mouse buttons. 11/08/2021 20:53:11 screen setup finished. 11/08/2021 20:53:11 The VNC desktop is: 2d9342fbf381:0 0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 11/08/2021 20:53:17 Got connection from client 127.0.0.1 11/08/2021 20:53:17 other clients: 11/08/2021 20:53:17 Got 'ws' WebSockets handshake 11/08/2021 20:53:17 Got protocol: binary 11/08/2021 20:53:17 - webSocketsHandshake: using binary/raw encoding 11/08/2021 20:53:17 - WebSockets client version hybi-13 11/08/2021 20:53:17 Disabled X server key autorepeat. 11/08/2021 20:53:17 to force back on run: 'xset r on' (3 times) 11/08/2021 20:53:17 incr accepted_client=1 for 127.0.0.1:49334 sock=10 11/08/2021 20:53:17 Client Protocol Version 3.8 11/08/2021 20:53:17 Protocol version sent 3.8, using 3.8 11/08/2021 20:53:17 rfbProcessClientSecurityType: executing handler for type 1 11/08/2021 20:53:17 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 11/08/2021 20:53:17 Pixel format for client 127.0.0.1: 11/08/2021 20:53:17 32 bpp, depth 24, little endian 11/08/2021 20:53:17 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 11/08/2021 20:53:17 no translation needed 11/08/2021 20:53:17 Enabling NewFBSize protocol extension for client 127.0.0.1 11/08/2021 20:53:17 Enabling full-color cursor updates for client 127.0.0.1 11/08/2021 20:53:17 Using image quality level 6 for client 127.0.0.1 11/08/2021 20:53:17 Using JPEG subsampling 0, Q79 for client 127.0.0.1 11/08/2021 20:53:17 Using compression level 9 for client 127.0.0.1 11/08/2021 20:53:17 Enabling LastRect protocol extension for client 127.0.0.1 11/08/2021 20:53:17 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC) 11/08/2021 20:53:17 Using tight encoding for client 127.0.0.1 11/08/2021 20:53:17 client_set_net: 127.0.0.1 0.0000 11/08/2021 20:53:17 created xdamage object: 0x40002c 11/08/2021 20:53:18 copy_tiles: allocating first_line at size 41 11/08/2021 20:53:25 client 1 network rate 1865.3 KB/sec (131281.5 eff KB/sec) 11/08/2021 20:53:25 client 1 latency: 2.6 ms 11/08/2021 20:53:25 dt1: 0.0037, dt2: 0.0131 dt3: 0.0026 bytes: 28773 11/08/2021 20:53:25 link_rate: LR_LAN - 2 ms, 1865 KB/s 11/08/2021 20:53:27 created selwin: 0x40002d 11/08/2021 20:53:27 called initialize_xfixes() libdvdread: Can't open file VIDEO_TS.IFO. 11/08/2021 20:58:05 got closure, reason 1001 11/08/2021 20:58:05 rfbProcessClientNormalMessage: read: Connection reset by peer 11/08/2021 20:58:05 client_count: 0 11/08/2021 20:58:05 Restored X server key autorepeat to: 1 11/08/2021 20:58:05 Client 127.0.0.1 gone 11/08/2021 20:58:05 Statistics events Transmit/ RawEquiv ( saved) 11/08/2021 20:58:05 ServerCutText : 1 | 8/ 8 ( 0.0%) 11/08/2021 20:58:05 FramebufferUpdate : 1444 | 0/ 0 ( 0.0%) 11/08/2021 20:58:05 LastRect : 700 | 8400/ 8400 ( 0.0%) 11/08/2021 20:58:05 tight : 4928 | 4152232/115574784 ( 96.4%) 11/08/2021 20:58:05 RichCursor : 1 | 1374/ 1374 ( 0.0%) 11/08/2021 20:58:05 TOTALS : 7074 | 4162014/115584566 ( 96.4%) 11/08/2021 20:58:05 Statistics events Received/ RawEquiv ( saved) 11/08/2021 20:58:05 PointerEvent : 1529 | 9174/ 9174 ( 0.0%) 11/08/2021 20:58:05 FramebufferUpdate : 1445 | 14450/ 14450 ( 0.0%) 11/08/2021 20:58:05 SetEncodings : 1 | 56/ 56 ( 0.0%) 11/08/2021 20:58:05 SetPixelFormat : 1 | 20/ 20 ( 0.0%) 11/08/2021 20:58:05 TOTALS : 2976 | 23700/ 23700 ( 0.0%) 11/08/2021 20:58:05 destroyed xdamage object: 0x40002c [services.d] stopping services [services.d] stopping app... [services.d] stopping x11vnc... caught signal: 15 11/08/2021 22:11:14 deleted 40 tile_row polling images. [services.d] stopping openbox... [services.d] stopping statusmonitor... [services.d] stopping logmonitor... [services.d] stopping xvfb... [services.d] stopping autovideoconverter... [services.d] stopping certsmonitor... [services.d] stopping nginx... [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

Yeah I've never hit my seed max and I get "credit" for it being "available" to download. I thought about the above as well as I was typing and may give it a shot. I'm already seeding close to 3TB of files. I was just thinking about cache pools since it can be added to but it may be better going back to the array. Thanks Tristankin