TopTrainer

I have added a Mac to my system along side my windows box, I have not written anything to the servers using the Mac only viewed files and I notice its leaving DS_store files on the servers, is there anything already in UnRaid to deal with it or do I have to install something?Perhaps someone could point me in the right direction. I am using 6.1.9 on both servers though the older one still runs reiser. Thanks Peter

I have absolutely no docker experience, but am i able to run linux distros from it as I would like to try them. If this is an option perhaps someone could point me in the right direction. Thanks

I am showing orange triangles in the dashboard on three drives, raw value on the Parity.... 65534, disk2.... 1459, disk 6....8 I am guessing these need replacing, also guessing the parity first? My drives on this box are currently reiser would this be a good time to change them to xfs? Peter

I have run reiserfsck already, after it told me of the corruption, it is still throwing the problem. Did the sys log not say I had rebuilt the tree? Are you saying I need to rebuild it again then? could it be that the corruption occurred when parity rebuilt the new drive? there is only a small portion of the drive I can read, what is the way forward with this?

Hi Frank I have attached the diagnostics zip. On looking with fresh eyes today, this server, as in my old server, displayed the actual drives as opposed to the shares. After had downloaded the diag file, the drive, Drive4 folder has re-populated with the data. Windows is still telling me I cant access it, though I can a couple of folders Its really strange behavior. Surely I would not be able-to access anything would I? Is there any value in running the permissions on this drive again? I did it a couple of times and it did not make any difference. Peter tower-diagnostics-20160208-1656.zip

Frank, thanks for the pointing me towards the info. I now have gone through the process of rebuilding the file tree which reiser advised but have additional issues that i need some fairly urgent help with. I watched most of the process, the deleting and flushing etc. But now having mounted the drive there is nothing in it, its empty. Do I need to re-boot or something else because the folder is showing empty at this time, i hope I have not made things a whole lot worse. Peter

I have completely run the new permissions tool on all 15 disks and it has not changed the situation. I have not run a file system check as I am unsure how i do that in in 6.1.7 ? The new drive was installed under 4.7 and was accessible, so clearly there was no file system problems then, the file structure is reiserf. The upgrade to 6.1.7 was then undertaken and permissions tool run as per instructions it was after that the drive displayed access issues. The drive opens I can see the folders but individual access is refused, if you think there is value in running a file system check I will, if someone could tell me how its done. I am getting nowhere with this issue I cant help thinking the problem is with 6.1.7 as i was able to access it in 4.7.

Only two other possible causes spring to mind: There is some level of file system corruption. Running a file system check would resolve this. There is a permissions issue. Running Tools->New Permissions would resolve this. I ran the new permissions when I upgraded to 6.1.7 and have also individually run it on the disk in question since. I assumed this was a windows issue, not an UnRaid one? Do you mean run another complete new permissions in terms of changing it? there is only me uses the system its not affecting anyone else. Peter

Thanks for your reply and suggestion, I was very hopeful, but had never actually heard of it so I knew I had never saved anything to there. When I looked at it all the credentials were empty. Peter

I have recently replaced a failing drive and rebuilt it whilst in Unraid V4.7 . I then upgraded to version 6.1.7 ran permissions etc. The new drive is visible and opens, and folders open. But windows 7 refuses permissions to view data on that drive only every other drive is fine. I have tried changing things in the permissions and the problem remains. Its clearly to do with just adding the new drive and I just don't know what it could be. Has anyone else experienced a similar problem, and what solutions did you achieve. Thanks Pete

The new disk has arrived, do I need to format the disk for the rebuild to work? I understand the pre-clear is not required. Thanks

I have run a smart report on the drive I suspected it to be, It the report did not show up in the sys log for some reason but I viewed in UnMenu drive reports. I dont think things look good? If I put in a new drive and pre-clear would parity rebuild it? smartctl -a -d ata /dev/sdn (disk4) smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3617251 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Jan 22 21:31:51 2016 GMT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 73) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: (36000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 152 152 051 Pre-fail Always - 132388 3 Spin_Up_Time 0x0027 189 169 021 Pre-fail Always - 5533 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5077 5 Reallocated_Sector_Ct 0x0033 136 136 140 Pre-fail Always FAILING_NOW 1213 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 044 044 000 Old_age Always - 41315 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 138 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 23 193 Load_Cycle_Count 0x0032 188 188 000 Old_age Always - 36608 194 Temperature_Celsius 0x0022 126 111 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 360 197 Current_Pending_Sector 0x0032 200 001 000 Old_age Always - 70 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 33 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 040 037 000 Old_age Offline - 42736 SMART Error Log Version: 1 ATA Error Count: 35 (device log contains only the most recent five errors) 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 35 occurred at disk power-on lifetime: 40577 hours (1690 days + 17 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 b0 8f a0 ef Error: UNC at LBA = 0x0fa08fb0 = 262180784 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 08 8f a0 ef 08 01:19:39.684 READ DMA c8 00 00 08 86 a0 ef 08 01:19:39.439 READ DMA e5 00 00 00 00 00 00 08 01:19:39.439 CHECK POWER MODE Error 34 occurred at disk power-on lifetime: 40556 hours (1689 days + 20 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 b8 78 a0 ef Error: UNC at LBA = 0x0fa078b8 = 262174904 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 90 78 a0 ef 08 1d+07:15:36.940 READ DMA c8 00 00 90 6f a0 ef 08 1d+07:15:35.132 READ DMA Error 33 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 48 3a 17 ef Error: UNC at LBA = 0x0f173a48 = 253180488 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:34.687 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:34.687 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:34.683 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:34.683 SET FEATURES [set transfer mode] Error 32 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 90 39 17 ef Error: UNC at LBA = 0x0f173990 = 253180304 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:31.535 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:31.535 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:31.531 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:31.531 SET FEATURES [set transfer mode] Error 31 occurred at disk power-on lifetime: 40050 hours (1668 days + 18 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 40 3a 17 ef Error: UNC at LBA = 0x0f173a40 = 253180480 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 70 39 17 ef 08 23d+06:07:27.171 READ DMA ef 10 02 00 00 00 a0 08 23d+06:07:27.171 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 23d+06:07:27.167 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 23d+06:07:27.167 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: unknown failure 90% 41314 - # 2 Short offline Completed: read failure 90% 40055 93257669 # 3 Short offline Completed: read failure 90% 40055 93257665 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.

I am poised to upgrade my older server to 6.1.7 from 4.7. I thought I saw information as I was closing the array down before a close down suggesting a drive failure was about to occur I cant see the information anymore. Could someone please cast an expert eye over the attached sys log and advise me accordingly. Thanks Peter syslog-2016-01-22.txt

Could someone advise me please what is the preferred method to update from 6.1.3. to 6.1.7 Thanks