unraidnoob

Time flies.. I've been using unraid for about 10 years now and pretty much it just runs in the background for plex and other media. I'm thinking about trying to do some VM gaming on it. Where should I start? Crazy how storage has changed over time. I have 6 drives 2-3TB and a cache drive and only had to replace 1 HDD earlier this year. Completely new to gaming and VM but I'm not looking at hardcore gaming what should I buy for from a video card perspective that will make this transition smooth? I'm guessing I would play things from like fortnite and lost ark etc. I've been looking at the the AMD 5600x or G and then adding like a 1070ti and using moonlight i think? Going up to 16 gig ram can i keep mu old PSU?.. a corsair CX650. I'm running unraid 6.9.2, I'm also getting concerned that some of my drives will start failing now so just trying to be a little premptive.

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA4735713 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Nov 4 08:02:47 2012 EST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (36360) 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 185 185 051 Pre-fail Always - 35882 3 Spin_Up_Time 0x0027 253 172 021 Pre-fail Always - 991 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 573 5 Reallocated_Sector_Ct 0x0033 186 186 140 Pre-fail Always - 265 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14303 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 - 54 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 193 Load_Cycle_Count 0x0032 061 061 000 Old_age Always - 417841 194 Temperature_Celsius 0x0022 123 107 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 077 077 000 Old_age Always - 123 197 Current_Pending_Sector 0x0032 198 196 000 Old_age Always - 946 198 Offline_Uncorrectable 0x0030 200 198 000 Old_age Offline - 7 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 144 144 000 Old_age Offline - 15123 SMART Error Log Version: 1 ATA Error Count: 1745 (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 1745 occurred at disk power-on lifetime: 14303 hours (595 days + 23 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 08 98 b8 00 e0 Error: UNC 8 sectors at LBA = 0x0000b898 = 47256 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 08 98 b8 00 e0 08 5d+11:35:08.129 READ DMA ef 10 02 00 00 00 a0 08 5d+11:35:08.129 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+11:35:08.125 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+11:35:08.125 SET FEATURES [set transfer mode] Error 1744 occurred at disk power-on lifetime: 14303 hours (595 days + 23 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 08 98 b8 00 e0 Error: UNC 8 sectors at LBA = 0x0000b898 = 47256 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 08 98 b8 00 e0 08 5d+11:35:05.456 READ DMA e5 00 00 00 00 00 40 08 5d+11:35:02.474 CHECK POWER MODE ca 00 08 90 b8 00 e0 08 5d+11:34:59.572 WRITE DMA c8 00 08 90 b8 00 e0 08 5d+11:34:59.572 READ DMA Error 1743 occurred at disk power-on lifetime: 14302 hours (595 days + 22 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 08 78 b8 00 e0 Error: UNC 8 sectors at LBA = 0x0000b878 = 47224 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 08 78 b8 00 e0 08 5d+11:26:49.370 READ DMA ef 10 02 00 00 00 a0 08 5d+11:26:49.370 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+11:26:49.366 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+11:26:49.366 SET FEATURES [set transfer mode] Error 1742 occurred at disk power-on lifetime: 14302 hours (595 days + 22 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 08 78 b8 00 e0 Error: UNC 8 sectors at LBA = 0x0000b878 = 47224 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 08 78 b8 00 e0 08 5d+11:26:46.708 READ DMA ef 10 02 00 00 00 a0 08 5d+11:26:46.708 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+11:26:46.704 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+11:26:46.704 SET FEATURES [set transfer mode] Error 1741 occurred at disk power-on lifetime: 14302 hours (595 days + 22 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 08 78 b8 00 e0 Error: UNC 8 sectors at LBA = 0x0000b878 = 47224 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 08 78 b8 00 e0 08 5d+11:26:44.047 READ DMA ef 10 02 00 00 00 a0 08 5d+11:26:44.047 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+11:26:44.043 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+11:26:44.043 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 Extended offline Completed: read failure 90% 14293 27770344 # 2 Short offline Completed: read failure 90% 14293 27770344 # 3 Short offline Completed without error 00% 14171 - 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. long test will start moving data too bad no drives on sale right now... grrr

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA4735713 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Nov 3 23:57:57 2012 EDT 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (36360) 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 185 185 051 Pre-fail Always - 34376 3 Spin_Up_Time 0x0027 253 172 021 Pre-fail Always - 991 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 573 5 Reallocated_Sector_Ct 0x0033 187 187 140 Pre-fail Always - 264 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14293 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 - 54 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 193 Load_Cycle_Count 0x0032 061 061 000 Old_age Always - 417675 194 Temperature_Celsius 0x0022 125 107 000 Old_age Always - 25 196 Reallocated_Event_Count 0x0032 078 078 000 Old_age Always - 122 197 Current_Pending_Sector 0x0032 198 196 000 Old_age Always - 946 198 Offline_Uncorrectable 0x0030 200 198 000 Old_age Offline - 7 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 144 144 000 Old_age Offline - 15123 SMART Error Log Version: 1 ATA Error Count: 940 (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 940 occurred at disk power-on lifetime: 14293 hours (595 days + 13 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 58 90 c0 00 e0 Error: UNC 88 sectors at LBA = 0x0000c090 = 49296 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 58 40 c0 00 e0 08 5d+02:14:33.667 READ DMA c8 00 08 38 c0 00 e0 08 5d+02:14:33.667 READ DMA c8 00 08 30 c0 00 e0 08 5d+02:14:33.666 READ DMA Error 939 occurred at disk power-on lifetime: 14293 hours (595 days + 13 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 58 20 b9 00 e0 Error: UNC 88 sectors at LBA = 0x0000b920 = 47392 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 58 18 b9 00 e0 08 5d+02:14:30.310 READ DMA c8 00 08 10 b9 00 e0 08 5d+02:14:30.310 READ DMA c8 00 08 08 b9 00 e0 08 5d+02:14:30.310 READ DMA Error 938 occurred at disk power-on lifetime: 14293 hours (595 days + 13 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 58 38 b6 00 e0 Error: UNC 88 sectors at LBA = 0x0000b638 = 46648 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 58 38 b6 00 e0 08 5d+02:14:26.999 READ DMA ef 10 02 00 00 00 a0 08 5d+02:14:26.998 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+02:14:26.995 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+02:14:26.995 SET FEATURES [set transfer mode] Error 937 occurred at disk power-on lifetime: 14293 hours (595 days + 13 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 58 38 b6 00 e0 Error: UNC 88 sectors at LBA = 0x0000b638 = 46648 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 58 38 b6 00 e0 08 5d+02:14:24.338 READ DMA ef 10 02 00 00 00 a0 08 5d+02:14:24.337 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+02:14:24.334 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+02:14:24.334 SET FEATURES [set transfer mode] Error 936 occurred at disk power-on lifetime: 14293 hours (595 days + 13 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 58 38 b6 00 e0 Error: UNC 88 sectors at LBA = 0x0000b638 = 46648 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 58 38 b6 00 e0 08 5d+02:14:21.677 READ DMA ef 10 02 00 00 00 a0 08 5d+02:14:21.676 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 5d+02:14:21.673 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 5d+02:14:21.673 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: read failure 90% 14293 27770344 # 2 Short offline Completed without error 00% 14171 - 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 was installing some plugins today and had to do a reboot. It didn't shutdown cleanly and my server has been acting strange since. It's checking parity but going super slow... is my disk failing? writes 17636 errors 71434 here is a piece of the sys log i'm able to get... Oct 28 23:33:09 Server kernel: ata4: EH complete Oct 28 23:33:12 Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 28 23:33:12 Server kernel: ata4.00: irq_stat 0x40000001 Oct 28 23:33:12 Server kernel: ata4.00: failed command: READ DMA EXT Oct 28 23:33:12 Server kernel: ata4.00: cmd 25/00:00:18:f1:53/00:04:25:00:00/e0 tag 0 dma 524288 in Oct 28 23:33:12 Server kernel: res 51/40:9f:78:f1:53/00:03:25:00:00/e0 Emask 0x9 (media error) Oct 28 23:33:12 Server kernel: ata4.00: status: { DRDY ERR } Oct 28 23:33:12 Server kernel: ata4.00: error: { UNC } Oct 28 23:33:12 Server kernel: ata4.00: configured for UDMA/133 Oct 28 23:33:12 Server kernel: ata4: EH complete Oct 28 23:33:15 Server kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 28 23:33:15 Server kernel: ata4.00: irq_stat 0x40000001 Oct 28 23:33:15 Server kernel: ata4.00: failed command: READ DMA EXT Oct 28 23:33:15 Server kernel: ata4.00: cmd 25/00:00:18:f1:53/00:04:25:00:00/e0 tag 0 dma 524288 in Oct 28 23:33:15 Server kernel: res 51/40:ef:28:f2:53/00:02:25:00:00/e0 Emask 0x9 (media error) Oct 28 23:33:15 Server kernel: ata4.00: status: { DRDY ERR } Oct 28 23:33:15 Server kernel: ata4.00: error: { UNC }

thanks... seems to be sabnzb causing the issue

hi there, Can anyone help? I just tried to install the new version of plex and it looks like it installed but now the server just says starting but only the flash drive mounts. i've rebooted a few times and removed plex but it's still stuck... anyone know what's wrong? i have couchpotato, sickbeard and sabnzbd installed (but they've never been an issue before) everything is green on the main page though syslog.txt

anyone know why i keep getting "Tracker returned a 4xx message errors" lately? doesn't happen on the my mac version of transmission but does on the unraid version.

got it working on wifi thanks guys..next task is through 3g quick question how do i monitor cpu usage? i'm running 2 gig on a single core sempron 140... seems to be doing alright but i don't mind sticking some more ram in..

Trying to install this but i think my usb stick is out of space.. can the downloaded packages be deleted once installed?

finally figured it out.. umask 0 will allow everyone to read and write... but for some reason i had to create a new folder because the existing folder would not change permissions. i then ran the unraid new permissions utility again and it fixed all the old files that i couldn't delete.

are you connecting to the server as root? If so please create a user via the unRAID webGUI and then use that user to log into the server. yes it's just me so i do everything as root... i created a user under the webgui but i don't see it...how do i login as that user? sorry for the noob question i'm kinda lost.

anyone?? how do you guys manage your torrents then? you leave everything in the download folder?

no luck still says i don't have permissions tried 0 22 666 anyone have any ideas?

Use the link I gave you in the package manager and read up on it. Maybe try setting it to 0, but I don't know, it will be different for different people and there setup. thanks... i'm trying to set it to 0 but keep getting errors sed: couldn't open temporary file /boot/packages/sedSVoBep: Read-only file system i'm in 5beta12a does this mean my flash is set to read only? how do i make it read and write? Sounds like your flash drive is corrupt, shutdown the server and run a checkdisk on the flash drive from a windows machine. alright that fixed the write issue thanks.. doing a parity check now so will try again after that.

Use the link I gave you in the package manager and read up on it. Maybe try setting it to 0, but I don't know, it will be different for different people and there setup. thanks... i'm trying to set it to 0 but keep getting errors sed: couldn't open temporary file /boot/packages/sedSVoBep: Read-only file system i'm in 5beta12a does this mean my flash is set to read only? how do i make it read and write?

Check the umask settings for the config file. it's at 18 what should i change it to?

just installed transmission and it seems to be working well... i do have an issue though, i like to organize my downloaded into various folders when they are done.. i can copy files out of the download folder but i cannot cut or delete files when i'm done.. I get a user read/write access error any idea why? or how to fix? says something like i need server/user permission to make changes to file...

thanks guys... after a few reboots it seems a bit better still slow.. transfer 4 gigs now estimate is 55 mins..still not too great...

Hey guys, Wonder if anyone can help me figure out what's going on here. I've got an unraid server setup that hooks up to everything in the house.. -macbook pro laptop via wifi (wireless N) -htpc win7 box via wired gigabyte -windows laptop via wifi (wireless g) and various other devices like phones and stuff for some reason the file transfer on the mbp is very slow.. right now i'm trying to copy some files (14 files 2.5 gigs total ) and it's telling me it's gonna take 75 hours. transferrings files via pc is pretty much normal I'm using smb shares on everything...any idea why my mac doesn't seem to play nice with my unraid server? thanks in advance... i also use it to backup via timemachine and for the most part that seems fine...

thanks again Joe L!

Please help.. I just precleared 2 drives and have set one up as data disk and loaded content on it. Can it still be changed or do i need to transfer data out and preclear again? Also can the I have drives all mixed and matched? Once the disk has been assigned to the array it cannot be changed. Disks can easily be mixed and matched. Any disk can be used with any partition start. I cannot stress that enough. There are many who have used an AF drive with a partition starting on sector 63 and it did not affect their use of the drive for playing movies/music. If you are obsessed with absolute max performance of an AF drive, then yes, you'll need to transfer the files elsewhere, un-assign it from the array, and run the pre-clear again. i'm not obsessed lol this is my first time.. i just don't want to screw it up. i'll just make sure the other ones are 4k and maybe do a data swap next time my drives are full..thanks very much! so once my drive is done preclearing... i can just run this command and it will change it to 4k correct? ./preclear_disk.sh -C 64 -m [email protected] /dev/sdX

Quick question wouldn't the new xbmc iPhone app do this?

Please help.. I just precleared 2 drives and have set one up as data disk and loaded content on it. Can it still be changed or do i need to transfer data out and preclear again? Also can the I have drives all mixed and matched?

ummm.. ok even more lost now.. i've done 2 drives now.. samsung f4 2tb advanced format drive and currently doing a wd green 1.5 tb both times i just entered ./preclear_disk.sh /dev/sdX and then typed Yes the samsung has been setup as a data drive and has data in it now the 1.5 is still being cleared... i used the latest version from the preclear thread i think... do i need to do everything all over again?

Hey guys got a noob question.. just started building my unraid server and i've got 1 2tb drive up and running and just started preclearing the second one... i was following this config guide http://www.lime-technology.com/wiki/index.php?title=Configuration_Tutorial and then read somewhere in the forums about 4k alignments or something like that using -A or -a... i've precleared my first 2 drives with this ./preclear_disk.sh /dev/sdX then i noticed the guide was for an older version...i'm using the latest stable build 4.7 am i going to have any issues? please help thanks.. i still have my parity drive but need to get data off of it before a preclear.. should i preclear that drive differently?