kingsheep

No can't see that on mine ;-( will have to manually look on the web and see if there is a BIOS patch for this other than from Gigabyte. In the mean time I can always boot a HDAT2 USB drive on my Supermicro UnRaid and clear the disks down that way, starting with the parity.

My board is quite an old one and I have checked the BIOS with Gigabyte and it is the latest.... no HPA or copy BIOS in the menu list though... MOBO is a GA-MA78GM-S2H

Yes loaded the bios update utility and ran it.... no change Damn you GigaByte Damn you to Heck!!!!

Hi Guys lots of good comments. The unraid box has a Supermicro MoBo with no HPA enabled. The other machine is a GigaByte and I can find no way of turning HPA off. As the Raid in in operation and fully loaded with Data I think I will have to disable HPA on the other machine clean the Parity drive then rebuild it then after syncing rebuild the other drives one as a time!!!! Oh well its life!!!

Well I have taken all the disks out and ran them through HDAT2 which did not remove the HPA partion I guess it needs a re-format/partition after this? Putting the disks on my "clean up machine" even added a new HPA partition to one of the disks Grrrrrrr ....Strange thing is after all this work and re-starting Unraid the Parity disk started building!!!! Do I still need to remove the HPA partitions?

OK I can see from the list below that the Parity disk, 0, seems to have a slightly smaller size even though it is also a 3TB drive... Will try to find out how to disable HPA tonight.. Jan 15 06:39:20 MATRIX kernel: md: import disk0: [8,64] (sde) WDC_WD30EZRX-00MMMB0_WD-WCAWZ1613334 size: 2930265476 Jan 15 06:39:20 MATRIX kernel: md: disk0 replaced Jan 15 06:39:20 MATRIX kernel: mdcmd (2): import 1 8,80 1953514552 WDC_WD2002FYPS-01U1B1_WD-WCAVY0878979 Jan 15 06:39:20 MATRIX kernel: md: import disk1: [8,80] (sdf) WDC_WD2002FYPS-01U1B1_WD-WCAVY0878979 size: 1953514552 Jan 15 06:39:20 MATRIX kernel: mdcmd (3): import 2 8,48 2930266532 WDC_WD30EZRS-00J99B0_WD-WCAWZ0983361 Jan 15 06:39:20 MATRIX kernel: md: import disk2: [8,48] (sdd) WDC_WD30EZRS-00J99B0_WD-WCAWZ0983361 size: 2930266532 Jan 15 06:39:20 MATRIX kernel: mdcmd (4): import 3 8,32 1953513496 WDC_WD2002FYPS-01U1B1_WD-WCAVY1705381 Jan 15 06:39:20 MATRIX kernel: md: import disk3: [8,32] (sdc) WDC_WD2002FYPS-01U1B1_WD-WCAVY1705381 size: 1953513496 Jan 15 06:39:20 MATRIX kernel: mdcmd (5): import 4 8,16 2930265476 WDC_WD30EZRS-00J99B0_WD-WCAWZ0912979 Jan 15 06:39:20 MATRIX kernel: md: import disk4: [8,16] (sdb) WDC_WD30EZRS-00J99B0_WD-WCAWZ0912979 size: 2930265476 Jan 15 06:39:20 MATRIX kernel: mdcmd (6): import 5 8,112 1953514552 WDC_WD2002FYPS-01U1B1_WD-WCAVY0704588 Jan 15 06:39:20 MATRIX kernel: md: import disk5: [8,112] (sdh) WDC_WD2002FYPS-01U1B1_WD-WCAVY0704588 size: 1953514552 Jan 15 06:39:20 MATRIX kernel: mdcmd (7): import 6 8,96 1953514552 WDC_WD2002FYPS-02W3B0_WD-WCAVY7162087 Jan 15 06:39:20 MATRIX kernel: md: import disk6: [8,96] (sdg) WDC_WD2002FYPS-02W3B0_WD-WCAVY7162087 size: 1953514552 Ok i've had chance to check my BIOS and there is no obvious HPA setting. As I currently have 7 disks on the box and only 3 are showing HPA I think these must be the disks from my other Raid system and have a hidden HPA partition on them. I have PreCleared the disk but guess it has not removed the partition. Is this partition really such an issue for Unraid, if so I have to fine some method of cleansing the disks

Is HPA an issue with this release then as the BIOS settings have not been changed since the system was running fully configured with 4.7?

Cheers. Same problem, Syslog attached. syslog.txt

All ready to upgrade but looks like the release notes section is offline, so I don't know what bits to patch ;-(

I have an array made up of 2 and 3 TB disk. When I try to add a 3TB disk as the parity I get the message that it is not the largest and it wont add it? Is a 3TB parity disk acceptable still or is there a work around for this?

The command is identical to what it was before the upgrade it all scripted. Essentially there are 6 drives with 3 directories per drive that are encrypted... an example of the unmount command is: fusermount -u /mnt/disk1/Data Is it an issue to do with FUSE and this version of the Kernel? I was on beta14 prior to this, can I downgrade from rc8? Certainly if I bounce the system I am able to mount all encrypted directories after.

I have been using this with no problem of previous releases. Since up grading to rc8a every time i try un-mountig a encfs I get fInvalid argument e.g. usermount: failed to unmount /mnt/disk6/Video: Invalid argument This is an identica syntax to what I had previously... has something changed as part of this release?

Thanks for you help, I'l try that later. My main question was, I know this is a beta release, but would we expect the system to lock up and in such a spectacular fashion or just handle it as it would with a normal disk failure?

I have a strange one here.... I've just been moving my disks around after upgrading some to 2 TB from 1 TB however after a while of rebuilding parity the system just locks up, web server goes down as does any remote session!! When I look at the local console I can see it has got a constant line regarding a bad disk rolling over and over and you can not even login!!! After bouncing the box I can see that one disk is marked as bad!!! After a few attempts I'm now replacing the bad disk and rebuilding from what was in parity then will update from my back up. I just thought it was worth pointing out as this is strange behavior i.e. the system locking up. I've attached some pics and a MOV of the console screen and a syslog all be it after a reboot. Sorry had to amend uploads due to size restrictions.

I could not see it as assigned anywhere and even deleted to super.dat file and restarted..... weird...

When ever I try preclearing a newly added drive I get: Sorry, /dev/sda is already assigned as part of the unRAID array.Clearing will NOT be performed The drive is not part of an array so why am i getting this?

I've had problems seening user shares since upgrading from 4.7 to 5.0.14... I ran the fix permissions... run it from the command line but nothing!! When I go into the mnt/user/shares I see all the files and directories are own by root? If I then run the chown -R nobody:users mnt/user/shares command the ownership changes to nobody:users and the share appears? Is this a problem or is it just me missing something?

boof - Many thanks, thats great news ;-) Unraid just gets better and better what a great system.

I’ve been playing around with EncFS on my unraid box and so far it all seems to have gone well. I can let unraid start up mount all the disks then run my EncFS mount using telnet/expect from my Apple (just so I don’t keep the EncFS keys on the Unraid box). My question however is how does loading up an EncFS directory work with the parity disk, as before mounting an EncFS directpry the disk would have two directories say Video (unencrypted, with no data) and .Video (encrypted, with data). After the mount Video would now show as having all the files. So would the parity disk try to try to update every time I mount/unmount the EncFS drive, if it does it will never be up to date and cover the disks?

Well Pre-clear was taking such a long time on this drive >37 Hours!!! A non-enterprise WD 2TB drive had finished the preclear in 34 Hrs. So I started thinking maybe this drive is a bit on the slow side and decided to to try the WD Diag tool. This passed with flying colours.. so maybe it was a glitch, after all, just a slow drive?

Cheers Guys. I'm running a pre clear first using version 1.12 of the script on another box to see if the problem has gone away, if it fails again I'll use the WD diagnostic tool and report back ;-) In the mean time i've been running a Memtest on my main box, i've attached the screen dump but all looks fine to me, please advise if I'm wrong.

Many thanks. I'll give the memory test a try tonight plus I can also boot my main machine up as Unraid using the trial version and will run a Pre-Clear on the same disk and see what it comes back with.... Such a pain having all these variables but at least the disk it first failed as having Errors on was able to be read on another machine and the data extracted... You don't get that with a propitiatory RAID system, and the fact that the disk was readable on another machine may also point to the hardware on the first..... Joe L - I just followed the link you gave and can only see preclear for up to version 1.11 ?

I'm running Unraid version 4.7. One of my Drives generated tons of errors during updating the Parity disk and red balled. So I replaced it with another disk in the same slot but pre-cleared failed. I know it might be down to the cables etc.. but is there anything in the log file that can help see where the issue is? ========================================================================1.4 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:19:39 (75 MB/s) == Last Cycle's Zeroing time : 6:28:40 (85 MB/s) == Last Cycle's Post Read Time : ( MB/s) == Last Cycle's Total Time : == == Total Elapsed Time == == Disk Start Temperature: 33C == == Current == ============================================================================ ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sde == Disk: /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2002FYPS-01U1B0 Serial Number: WD-WCAVY0941964 Firmware Version: 04.05G05 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: Wed Aug 17 22:45:50 2011 BST 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: (40260) 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: (0x303f) 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 - 0 3 Spin_Up_Time 0x0027 148 145 021 Pre-fail Always - 9575 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1748 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 082 082 000 Old_age Always - 13372 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 - 89 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 74 193 Load_Cycle_Count 0x0032 154 154 000 Old_age Always - 139352 194 Temperature_Celsius 0x0022 119 098 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 195 167 000 Old_age Offline - 1030 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sde == Disk: /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Probable ATA device behind a SAT layer Try an additional '-d ata' or '-d sat' argument. == ============================================================================

Any ideas... anyone... please...?

I've noticed when I'm copying files and directories from my old server to Unraid that directories are being created with today's timestamp but files are retaining their original timestamp!! Has anyone seen this before? My old system was a Thecus using ext2 and I never saw this on a samba share before?