churchb

OK Maybe I will get something new to replace them, what I really want to understand is whether the above should all be compatible with each other, dont want to find out something isnt compatible after dismantling my old server.

I need to upgrade my server as it is pretty ancient, I've built many a PC but not for probably near to 10 years!! Below is what I am thinking, I just need to understand if this should all work ok together? Case:- Fractal Design Define XL (Existing) Motherboard:- Supermicro MBD-X11SCH-LN4F-O (New) CPU:- Intel Xeon E-2278G (New) Cooler:- Noctua NH-U12A (New) Memory:- 64GB (4x16GB) Corsair DDR4 Vengeance LPX Black, PC4-19200 (2400), Non-ECC Unbuffered, CAS 14-16-16-31, XMP 2.0, 1.2V (New) PSU:- 1000W Corsair RM1000x, Full Modular, 80PLUS Gold, SLI/CrossFire, Single Rail, 83.3A, 135mm Fan, ATX PSU (New) SATA:- 2 x Supermicro AOC-SASLP-MV8 (Existing) I will be putting all my existing drives in which is 7 x 8TB, 9 x 4TB + SSD Cache drive + 2TB unassigned drive

Seems my whole issue was browser related! Cleared the chrome cache and things displayed correctly, re-enabled the unassigned devices plugin and array starts without issue. Sometimes its the simple things doh! Thanks for the help.

Diagnostic following fresh reboot and starting the array attached. tower-diagnostics-20190223-2357.zip

OK I narrowed the issue down to unassigned devices plugin, when I disable that plugin by renaming the .plg on the flash I can now start the array, but still I cant see any of the docker details (although they are running) and also the dashboard details are empty?

I recently had a disk fail and i replaced it, rebuilt parity no worries but had an odd issue where I couldnt see various things in the GUI, ie docker images not showing although were running, data on the dashboard missing etc. I eventually rebooted the server with the array set not to autostart. when I try to start it I am seeing the following error in the log each time Feb 23 12:03:21 Tower emhttpd: req (5): startState=STOPPED&file=&cmdStart=Start Feb 23 12:03:21 Tower emhttpd: error: cmdStart: missing csrf_token diagnostics attached, I have searched for this error and there are some matches but seem to related to outdated plugins rather than stopping the array from starting? Any help or advice much appreciated. tower-diagnostics-20190223-1154.zip

Cheers, that did the trick with just a few files corrupted during the process... I guess I need to look to migrate to xfs but it sounds a bit of a chore for the 14 disks that are ReiserFS ?

Yeah that is what I do, separate folders, I have Movies, TV Shows and subfolders under these... Kids and Normal, I initially had kids and adult but it sounded a bit too porny which it isnt! As the kids get older, every so often I move some things from Normal to the kids folders.

I powered off my server and swapped a couple of disks around internally and powered back up, everything seems to be normal and ok except one of the disks is displaying weirdly like below.. Any ideas how to rectify this?

OK Thanks... Its been running for a few hours now.. fingers crossed [edit] All seems to be ok, panic over [/edit]

Suddenly found one of my disks is read-only, I ran a filesystem check whilst in maintenance mode with attached results. Looking on the wiki if the recommended action is to run with --rebuild-tree then there are warnings about possible file loss and that recovery may not be 100%, this is only Disk2 in my array, is this corruption within the parity? ie am I better to just remove the drive and let it rebuild again? will this restore everything back to normal or what would be recommended in my case? reiserfsck.txt

I had exact same problem I *think* since I upgraded to 6.1.2 The mover script moved Movies ok but NOT TV Shows My Movies.cfg file.. # Generated settings: shareComment="" shareInclude="" shareExclude="" shareUseCache="yes" shareAllocator="highwater" shareSplitLevel="4" shareFloor="41943040" shareExport="e" shareSecurity="public" shareReadList="" shareWriteList="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="public" shareHostListNFS="" shareExportAFP="-" shareSecurityAFP="public" shareReadListAFP="" shareWriteListAFP="" shareVolsizelimitAFP="" My TV Shows.cfg file.... # Generated settings: shareExport=e shareExportNfs= shareExportNfsFsid=0 shareComment= shareValidUsers= shareInvalidUsers= shareExceptions= shareInclude= shareExclude= shareUseCache=yes shareAllocator=highwater shareSplitLevel=3 shareFloor=20971520 So I changed the cache drive from 'Yes' to 'Only' saved and changed back to 'Yes' Now TV Shows.cfg looks like this # Generated settings: shareComment="" shareInclude="" shareExclude="" shareUseCache="yes" shareCOW="auto" shareAllocator="highwater" shareSplitLevel="3" shareFloor="20971520" shareExport="e" shareSecurity="public" shareReadList="" shareWriteList="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="public" shareHostListNFS="" shareExportAFP="-" shareSecurityAFP="public" shareReadListAFP="" shareWriteListAFP="" shareVolsizelimitAFP="" shareVoldbpathAFP="" Re-ran mover script and its now moving them all ok... is this a bug? Thanks for this, sorted my issue out

I have RMA and it looks like they are sending the same size, I have been meaning to upgrade to v5 to start incorporating bigger disks but need to get the array stable and working before going for it.

Drive is still in warranty so nice, free replacement! Thanks for your help.

My system is at 4.7 I have a disk showing as DISK_DSBL, I tried carrying out the advice of... stopping the array unassign drive start the array with it un-assigned stop the array re-assign the drive that was disabled start the array This then started rebuilding the drive but I came back and its showing DISK_DSBL again, this must have been before it finished rebuilding as it was only a few hours later. system log attached. I ran smart report for the drive but this doesnt fail? smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EZRX-00DC0B0 Serial Number: WD-WMC1T2235192 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Jan 9 23:18:35 2014 Local time zone must be set--see zic m 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: (26580) 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: (0x70b5) 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 200 200 051 Pre-fail Always - 62 3 Spin_Up_Time 0x0027 182 159 021 Pre-fail Always - 5900 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1211 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 7101 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 30 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21 193 Load_Cycle_Count 0x0032 196 196 000 Old_age Always - 13537 194 Temperature_Celsius 0x0022 122 103 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 198 198 000 Old_age Always - 854 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 121 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 194 186 000 Old_age Offline - 1934 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 7101 - # 2 Short offline Completed without error 00% 7095 - # 3 Short offline Completed without error 00% 6321 - # 4 Extended offline Aborted by host 90% 6321 - 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. The drive is connected to a AOC-SASLP-MV8 controller, I have tried changing the cable already, any advice please? syslog-2014-01-09.zip