romanodog

Thank you!

I just wanted to pop in and say I noticed similar behavior on my system as well. Not sure if it was always like that or if it was related to a recent update. My cpu hovers aroune 20-30% but stopping the crashplan docker brings it down to 1-2%. I only noticed because the fans on my server in the basement have been louder than usual.

After some consideration, the server shut down at about the same time my 7 year old went into the basement to look for something... I have a feeling he pressed the power button. I can't get him to admit it! lol

Thank you, good to know.

Thanks I will do that! I did look through my docker logs and they were shut down cleanly so it wasn't a sudden power down. Makes me feel a little better.

Woke up this morning and my server was off. I started it back up and there doesn't appear to be any issues, but I'm wondering if there's a way to get any system logs from before the server went down so I can see if there was a reason for it listed.

That did it, thanks!

No I haven't gotten it working yet. You're saying it worked before, so maybe something in the new update broke it? This is the first time I've tried so I had assumed that I had something set up wrong.

Hello, I've just set this docker up to watch and auto process a folder. I keep getting an error "Invalid preset Fast 1080p30". I get this for any preset that I select in the docker settings. I'm not sure why... can somebody help? Snippet of the log file ------- CONVERSION OUTPUT Wed May 6 11:00:28 EDT 2020 ------- Cannot load libnvidia-encode.so.1 [11:00:28] hb_init: starting libhb thread [11:00:28] thread 14c1bfb04b20 started ("libhb") HandBrake 1.3.2 (2020050400) - Linux x86_64 - https://handbrake.fr 2 CPUs detected Invalid preset Fast 1080p30 Valid presets are: General/ Very Fast 1080p30 Small H.264 video (up to 1080p30) and AAC stereo audio, in an MP4 container. Very Fast 720p30 Small H.264 video (up to 720p30) and AAC stereo audio, in an MP4 container. Very Fast 576p25 Small H.264 video (up to 576p25) and AAC stereo audio, in an MP4 container. Very Fast 480p30 Small H.264 video (up to 480p30) and AAC stereo audio, in an MP4 container. Fast 1080p30 H.264 video (up to 1080p30) and AAC stereo audio, in an MP4 container. Attaching a screenshot of my docker settings: Just as an FYI, i'm trying to use this in conjunction with the plex post processing script https://gist.github.com/jlesage/06d8024d510b630025814fa5b776fef9

Thank you so much, i'm rebuilding again. Back up drive and a new controller are on the way to my house now. Much appreciated!

Well I'm a dummy and completely missed that check box I have the array back up now. How can I rebuild the disk that has the error? What's the proper procedure for that?

Ah, thanks for the info. Looks like it's time to do some shopping.

I am running SMART check on it now, but I will look for that checkbox after. I didn't notice it before but maybe I missed it. I see that RocketRaid 2300 is on the list of working controllers. I've had it hooked up for over a year with no issues, so I'm not sure that that's where the problem is. https://wiki.unraid.net/Hardware_Compatibility#PCI_SATA_Controllers

I did suspect that, but I moved disk 3 to the motherboard and it still is unmountable. I cannot start the array after I remove disk 3 from it, it just says a disk is missing and the start button is disabled.

I have a server set up with 5 drives: 2 parity and 3 data, all 8tb. I recently upgraded from version 6.7 to to 6.8.3. When the server came back up one of my drives, disk 3, said Unmountable: Unsupported partition layout. To be honest, I can't say for sure what exact steps I took after this: I believe I tried just rebooting the server. When the array was started, it was not emulating that drive, it just acted as if it was not there (the files on it were unaccessable and the available space was reduced by 8tb.) I stopped the array, clicked on disk 3 to remove it from the array (probably a mistake?). I added it back to the array and it started to rebuild parity. Now I was able to start the array, it was rebuilding, and the contents of disk 3 were being emulated, so it was useable for now. After a day or so, I noticed that the parity rebuild hadn't budged past a certain point. I also began to have some weird issues like the webgui terminal and the logging pop up window not displaying anything. I checked top and my CPU usage was very low, which was odd because I figured it should be at 100% from the rebuild. I rebooted my the server and now the drive is still unmountable but I cannot start the array (emulated) if that drive is not selected, there is a message next to "start" that says a disk is missing. I've tried moving the drive from the raid card that it's been attached to to the motherboard in case it was a hardware problem. I ran the xfs repair utility and it didn't appear to show any kind of errors: xfs_repair -v /dev/md3 Phase 1 - find and verify superblock... - block cache size set to 318696 entries Phase 2 - using internal log - zero log... zero_log: head block 0 tail block 0 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Mon Apr 27 20:41:56 2020 Phase Start End Duration Phase 1: 04/27 20:41:50 04/27 20:41:51 1 second Phase 2: 04/27 20:41:51 04/27 20:41:51 Phase 3: 04/27 20:41:51 04/27 20:41:53 2 seconds Phase 4: 04/27 20:41:53 04/27 20:41:53 Phase 5: 04/27 20:41:53 04/27 20:41:53 Phase 6: 04/27 20:41:53 04/27 20:41:55 2 seconds Phase 7: 04/27 20:41:55 04/27 20:41:55 Total run time: 5 seconds done When I view the disk log, I get this error in there: emhttpd: error: ckmbr, 2115: No such file or directory (2): open: /dev/sdb1 Indeed I have no sdb1, just sdb. I'm not sure what to do at this point. I am going to grab another drive to use to replace it or to keep as a backup if this drive is usable, but is the data from that drive just gone now or do you think it is still recoverable from the parity? Not a huge deal because most of it is backed up elsewhere. Diagnostics attached. Any help is appreciated, thanks. tower-diagnostics-20200427-2103.zip