redia

Djboss, thanks for you answer, yeah I picked up the hooks. I was simply wondering if it could be done more automatically. bad habbits dies hard, I have a full process (with my own scripted part) which does already everything, but I used to run it on a workstation, and now I am considering moving all the processing part to my unraid which is (now) more powerfull.. I was just being lazy.. lol If you will conisder the second idea though my concept could make sense (depending on how you implement it) : imagine having multiple conversion preset (linked to independent folders), it would be amazing to have the file renamed based on the name of the preset, thus granting us clear vision on what is happening. anyway, I have been playing around with your docker over the week end and it has yet to fail me ,so again thank you Cheers, R

first of all thanks for this docker, I really like it. The GUI works flawlessly and I use it when I want to tune something specific.. for the automated part I am only missing one thing, but maybe I am the one doing something wrong. I would love the result file to be renamed upon completion. in the remaining part of my process I use a flag to process the files and I would love to avoid having to go and manually add it. it would be something pretty simple abce.2x10.fghij.mkv ---> abce .2x10.fghij (flag).mkv in fact an exceptional added feature would be to have multiple watch folders, allowing us to have a specific preset/config applied per folder (for example I require less quality for some show than some action movies) but seriously thank you for your work. Cheers, R

hello everyone, JoeL, your new script is really sweet running 1.3 I got this result... should I worry ? ================================================================== 1.3 = unRAID server Pre-Clear disk /dev/sdj = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Step 10 of 10 - Verifying the clear has been successful. = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 27:35:50 ========================================================================1.3 == == Disk /dev/sdj has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 120 6 ok 220222410 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 69 71 45 near_thresh 31 Temperature_Celsius = 31 29 0 ok 31 Hardware_ECC_Recovered = 52 50 0 ok 220222410 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I don't know these attributes and can't seem to find conclusive information. thanks for your help, R

hello everyone, sorry to bother. I thought I could figure it out by myself. but I am not sure. == Disk /dev/sde has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 9525 --- > 1 Raw_Read_Error_Rate 0x000f 109 100 006 Pre-fail Always - 21790999 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 28 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 156494 64c64 < 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 --- > 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 66,67c66,67 < 190 Airflow_Temperature_Cel 0x0022 070 070 045 Old_age Always - 30 (Lifetime Min/Max 29/30) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 064 064 045 Old_age Always - 36 (Lifetime Min/Max 29/36) > 195 Hardware_ECC_Recovered 0x001a 051 047 000 Old_age Always 70,73c70,73 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 193269233352719 < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1716 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 121027883434026 > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3906582512 > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3693395106 ============================================================================ if someone could strip it down for me it would be awesome. I have a bunch of disk I am pre-clearing.. so if you could explain your findings I will try to learn from it. here is what I am understanding (I am sorry if I show some ignorance.), I reformatted it to make it easier to read. first rule is to ignore the raw value changes (I think... lol) < ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 9525 > 1 Raw_Read_Error_Rate 0x000f 109 100 006 Pre-fail Always - 21790999 value going away from the treshold.. so positive < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 28 > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 156494 ignored as per the "first rule" < 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 > 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 worst going toward the threshold.. but I do not know how to analyse that.. < 190 Airflow_Temperature_Cel 0x0022 070 070 045 Old_age Always - 30 (Lifetime Min/Max 29/30) > 190 Airflow_Temperature_Cel 0x0022 064 064 045 Old_age Always - 36 (Lifetime Min/Max 29/36) kinda normal that the temp changes during a preclear < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always > 195 Hardware_ECC_Recovered 0x001a 051 047 000 Old_age Always value change, worst change, both are going toward the threshold. shouldn't I be worried ? < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 worst going toward the threshold. shouldn't I be worried ? < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 193269233352719 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 121027883434026 ignored as per the "first rule" < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3906582512 ignored as per the "first rule" < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1716 > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3693395106 ignored as per the "first rule" any help is welcome, R