phenomeus

I did the same again. following steps: 1. macOS Catalina 10.15.1, working since hours, forcing TM Backup on Server > failed cant find the share 2. creating failing.txt 3. stopping the unraid array 4. creating offline.txt 5. starting the unraid array 6. forcing TM Backup on Server > working, its preparing the backup, scanning files, all good what it should do everytime 7. creating working.txt 8. diff working.txt failing.txt > no results 9. diff working.txt offline.txt > some results of course still no solution to this damn problem. I don't understand what is the difference to a freshly started array? is something differently broadcasted? hope you can help me guys. keeping the .txt files for further inspection

I did that right now. it wasn't working, I created the failing.txt. than I stopped the array, restarted the array (no reboot) and TM started by clicking/ forcing it to do a backup. so I created a working.txt. but diff don't show any differences. further ideas?

#unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end

yes

Yes but it will not stay this way. The next backup will fail again until I stop and restart the array

hey guys, I'm on 6.7.2 + macOS 10.14.6 and still have problems with an already presented TM backup/share over smb. the thing is still that it cant be reached from my MacBook(s). ONLY when I stop the array and restart the array immediately it finds the share and is working flawlessly and as expected. how can I extract my log for this bug to track down? it has to unraids side doesn't it?

like me with pre final, I'm shutting down the array and restarting it, after that the TM share is visible or can be found by an already set up TM

i reinserted it and commented everything out besides the low include command for unassigned shares. so its still working. something in the global part f'ckd something up

finally did it. sreknobs tips couldn't help… so I took all the crap out of my smb extra configurations: [global] security = USER guest account = nobody public = yes guest ok = yes map to guest = bad user kernel oplocks = no oplocks = no level2 oplocks = no #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end and emptied it. voila! it's working. can anyone tell me what was important in that config?

I tried that already. still no luck… - afp is disabled - Enhanced macOS interoperability is on - public, secure or private doesnt matter - new share names - Different sizes - with or without cache drive - 2 MacBooks, brand new reinstalled or one that worked with afp - up2date macOS installations - …

tried everything by now… not working. same odd error "The network backup disk does not support the required capabilities" even a freshly installed Mojave macOS on another macbook gets the same error. so I assume I have to search here at unraid for the solution. did exactly what everyone else did. hidden time machine, normal, secured, public, empty directory, deleted share, created a new one every time the same error. its mounting the drive but error 45 in console. I can upload files to it, its not about write permissions

i have to connect to mine first and its not working. was working good with afp, so I will wait till 6.7 final and hope for the best… I tried everything already. all manual smb configs, reseting time machine on my Mac, etc. new shares, blank shares, everything

i also have the feeling that its a macOS behaviour. adding the drive with cli I get the following error: sudo tmutil setdestination -a smb://name:password@server/Backups Disk does not support Time Machine backups. (error 45) The backup destination could not be added.

hey, thanks but I did that and still, not working. its exported and visible but not connecting at the end its just creating this file in the share: .com.apple.timemachine.supported

hi all, im on 6.7rc5 and can't get TM to work over SMB. its showing up and I can login but while adding, its saying something like: "The network backup disk does not support the required capabilities" what steps do I have to configure manually before its working with the 6.7. final release? thnx in advance

Like you said. No trust. I tried add it back as parity and instantly there were read errors. So the drive goes back. And yeah i need to do something. The Seagate ran cooler and now it’s summer it died. My mistake

is it safe to use it after this? I mean this drive was running 13 hours. right now the array Is unprotected so I tend to use it if its safe enough.

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 316 - # 2 Short offline Completed without error 00% 296 - but the drive is still not accepted by unraid. can I do anything else except returning the drive/rma? the drive was running max 58° /55° and now at 52°

you are totally right. here the zip. thank you stitch-diagnostics-20180427-0743.zip

hi everybody, I'm on the latest unraidos and a longtime user. in the last 2 weeks I had 2 dying drives as parity drives?! first it was a long time used 5TB from seagate and as the drives died, I quickly ordered a HGST NAS Drive 4TB. today it died too! i noticed it ran 2-3 times at 65° C… both hdds were connected to the same sata cable and to the same pice card in a n40l hp server. I'm surprised that the second drive made the same exit after just some days of running. brand new hdd what can I do to verify if its really broken or if I can fix something? quick help would be nice, thank you in advance. I'm a little bit confused right now

alright I suppose seagate is not exchanging this drives? so it goes to garbage.

oh infamous? hm, got this drive 2 times… which parameters gave you the hint? what is uncorrectable and where do I have to look in the future? thanks in advancea

am i in the wrong forum section? admin please move me if so. just wanted to know if this drive is save enough to be used in unraid or do I have to throw it away?

hi after years of error free times in unraid I got my first errors with this drive (see smart). there were 201 Errors shown on the Main Tab before I removed it and replaced it. everything is fine. my question is: can I preclear the drive error-free oder something? I'm finishing a two cycle preclear right now, but smartctl still got me this status: thank you for any help or informations smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-9YN166 Serial Number: Z1F1A22L LU WWN Device Id: 5 000c50 04e6234bb Firmware Version: CC4H User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Oct 19 16:19:18 2017 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 339) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 149700320 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 092 092 020 Old_age Always - 8783 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 150314807 9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 21725 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1113 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 096 096 000 Old_age Always - 4 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 054 047 045 Old_age Always - 46 (Min/Max 20/46 #3) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 106 193 Load_Cycle_Count 0x0032 004 004 000 Old_age Always - 192839 194 Temperature_Celsius 0x0022 046 053 000 Old_age Always - 46 (128 0 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5736h+31m+38.717s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 162549425757 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 7125024280174 SMART Error Log Version: 1 ATA Error Count: 3 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 3 occurred at disk power-on lifetime: 21376 hours (890 days + 16 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 08 ff ff ff ef 00 5d+22:27:56.859 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+22:27:56.838 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+22:27:56.838 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+22:27:56.838 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+22:27:56.837 READ DMA EXT Error 2 occurred at disk power-on lifetime: 21376 hours (890 days + 16 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+22:27:44.275 READ DMA EXT 25 00 40 ff ff ff ef 00 5d+22:27:44.270 READ DMA EXT 25 00 50 ff ff ff ef 00 5d+22:27:44.256 READ DMA EXT 25 00 50 ff ff ff ef 00 5d+22:27:44.251 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+22:27:44.250 READ DMA EXT Error 1 occurred at disk power-on lifetime: 21345 hours (889 days + 9 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 4d+15:16:06.182 READ DMA EXT 25 00 c0 ff ff ff ef 00 4d+15:16:06.168 READ DMA EXT 25 00 c0 ff ff ff ef 00 4d+15:16:00.139 READ DMA EXT 25 00 40 ff ff ff ef 00 4d+15:16:00.127 READ DMA EXT 25 00 40 ff ff ff ef 00 4d+15:15:54.034 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 21622 - # 2 Short offline Aborted by host 90% 21420 - # 3 Extended offline Completed without error 00% 21380 - # 4 Short offline Completed without error 00% 21274 - # 5 Short offline Completed without error 00% 5373 - # 6 Short offline Aborted by host 90% 3518 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

hi bonienl. could you please make System Buttons responsive? I often check the page with my iPhone or iPad and the buttons are taking a lot of space. maybe after a certain size you can hide the labels and just offer the icons? its just cosmetic but never the less it would make it perfect.