zaniix

I thought if I had a path specified like /mnt/cache/appdata it would only look at the cache drive and not the array. are you saying that /mnt/user/appdata and /mnt/cache/appdata are the same?

I made some mistakes and now I need some help trying to fix it in the simplest way. I need to replace my cache drive with a larger one, but I realized that I used my cache drive as the location for /mnt/cache/appdata/ that some dockers are using I also set Docker vDisk location: /mnt/cache/docker.img Can I create new shares for these on the array, stop array and copy the files to the new shares, change the docker location settings, start the array? swap the cache disk and then set those new shares to cache prefer and invoke mover so the files will live on the cache drive, but have an array path. Would that work?

Thank you, that clears that part up. I just know how easy it can be to forget a small detail and destroy all the data.

So are you saying that I should move the unassigned drive to the parity slot and the old parity drive to a data drive slot and do a copy parity? then start array and format?

I have searched around a bit and I think I know what I need to do, but I am hoping some of you that are more experienced could chime in if my plan seems stupid. Current setup uRaid 6.8.3 One Parity Drive 3TB two Data drives each 3TB - formated ResierFS new drive not installed yet 4TB End goal 1) new 4TB drive as Parity 2) old Parity drive as Data Drive formated XFS 3) all data drives reformatted to XFS 4) end result one new 4TB parity and Three 3TB data drives I realize this is multiple processes, but I am want to make sure I am doing this in the most efficient and safe manner with the least risk to my data. My Plan 1) add new drive as unassigned and preclear just to make sure it is safe to use 2) stop all backups to unRaid, shut all VMs and Docker images. 3) turn off auto start, shutdown remove old parity drive 4) boot add new drive to parity slot, start array, wait for parity rebuild 5) shutdown and connect old parity drive, add as data drive, add exclusion to all shares for this drive to prevent any data being written t it start array, format XFS following this process https://wiki.unraid.net/File_System_Conversion#Mirroring_procedure_to_convert_drives in short copying data to empty drive and then swapping positions and format and restarting array each time. 6) restart any VMs, Dockers, and backup jobs 7) backup flash drive config I know this topic has been covered a lot, but there is always a detail or two that I find unclear so I appreciate any help.

Thank you, I picked this old drive that I had remove because I suspected it was flaky so I could see what negative result look like. Planning on replacing all my drives with some new HGST 3tb NAS drives soon. thanks!

I ran a preclear on a drive I just replaced and do not trust in an attempt to understand the preclear results so I can test all drives I use moving forward. Can you help me understand these results? Id this good or bad and what tells me that ========================================================================1.15 == invoked as: ./preclear_disk.sh -A /dev/sdd == WDCWD5000AAKS-00YGA0 WD-WCAS80792713 == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 7:20:48 (18 MB/s) == Last Cycle's Zeroing time : 2:13:43 (62 MB/s) == Last Cycle's Post Read Time : 20:00:24 (6 MB/s) == Last Cycle's Total Time : 29:35:54 == == Total Elapsed Time 29:35:54 == == Disk Start Temperature: 41C == == Current Disk Temperature: -->41<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 199 200 51 ok 180125 Reallocated_Sector_Ct = 199 200 140 ok 1 Power_On_Hours = 10 10 0 near_thresh 66111 Reallocated_Event_Count = 199 200 0 ok 1 Current_Pending_Sector = 200 196 0 ok 9 Multi_Zone_Error_Rate = 1 1 51 FAILING_NOW 22423 *** Failing SMART Attributes in /tmp/smart_finish_sdd *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 200 Multi_Zone_Error_Rate 0x0008 001 001 051 Old_age Offline FAILING_NOW 22423 327 sectors were pending re-allocation before the start of the preclear. 331 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 9 sectors are pending re-allocation at the end of the preclear, a change of -318 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, a change of 1 in the number of sectors re-allocated. ============================================================================

I do not want to risk messing up my existing setup until I have a stable V6 running. My current plan is to build a complete new rig with V6 and then I just have to figure out the best way to get the data there. I may have to just use Teracopy, but this is not efficient,will take a toll on my home network and will take days. You are correct I have no plan to use the old drives in the new system.

I did some searches and I do not feel liek I found an answer that I understand so that is why I am posting. Current setup is unRaid 4.7 with 3 drives, I want to boot the system with V6 and 3 new drives and then mount the old drives one at a time to move all the data to the new unRaid. I just have no idea how to do this. I considered just upgrading but it seemed like there were too many potential issues and copying the data over the network will take too long. From v6 how can I simply mount a old unraid drive from 4.7 and directly copy the data to one of the new unraid drives running V6. thanks

Looking for people who are using this board. I am considering upgrading my current 4.7 unraid system to a board that has more ports and better CPU selection so I can move to a 5.x build I am trying to keep cost down and I do not see myself going past (6) 4tb drives anytime soon. Are there better options for the price? Did anyone have issues with this board? http://www.newegg.com/Product/Product.aspx?Item=N82E16813157293 Many of the suggestions I see are hard to find or discontinued, way too expensive or just do more than I need. I am also not looking for equipment I have to flash in some special way. I just want some simple out of the box working components for minimal cost I do not have size constraints I use a midtower in my basement so I don't need a tiny mitx board, but I also do not need high end equipment that will let me run 24 drives. I am currently running this BIOSTAR A880G+ AM3 , but if it was to break I am not sure what I could use to upgrade it as it seems like nobody here uses anything but intel now so I am apprehensive about upgrading it to a newer AM3 board.

Hello I am currently using this Motherboard BIOSTAR A880G+ AM3 AMD 880G HDMI Micro ATX I have 3 drives attached and I am about to purchases a license and expand, but the board only has 4 SATA ports onboard and I need help finding a good card to expand that to 6 or 8 total I have 1 PCI-E slot and 2 PCI slots for expansion What do you suggest?

I have been using 4.7 for a long time and I am ready to buy a license and upgrade to some larger drives but to do this I need a stable version 5 release. Do you guys think we can expect a stable version 5 release in 2013?

I have 2tb green drives and I get about 25-30mb/sec write speeds with no cache drive

I am seeing some ACPI errors in the log, can someone tell me if they really mean anything and what I can do to fix it? I am only posting the errors not the entire log to save space. Aug 15 18:00:30 Tower kernel: ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0000000000000000/1 (20090903/tbfadt-557) (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (psargs-0359): [ECEN] Namespace lookup failure, AE_NOT_FOUND (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\] (Node c14760c8), AE_NOT_FOUND (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI: Executed 4 blocks of module-level executable AML code Aug 15 18:00:30 Tower kernel: ACPI: Interpreter enabled Aug 15 18:00:30 Tower kernel: ACPI: (supports S0 S1 S5) Aug 15 18:00:30 Tower kernel: ACPI: Using IOAPIC for interrupt routing Aug 15 18:00:30 Tower kernel: PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: PCI: MCFG area at e0000000 reserved in ACPI motherboard resources Aug 15 18:00:30 Tower kernel: PCI: Using MMCONFIG for extended config space Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D0._STA] (Node f7417c48), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\PRID.P_D1._STA] (Node f7417cf0), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D0._STA] (Node f7417e58), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error: No handler for Region [sACS] (f741e820) [PCI_Config] (20090903/evregion-319) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error: Region PCI_Config(2) has no handler (20090903/exfldio-295) (Errors) Aug 15 18:00:30 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:30 Tower kernel: ACPI Error (uteval-0250): Method execution failed [\SECD.S_D1._STA] (Node f7417f00), AE_NOT_EXIST (Minor Issues) Aug 15 18:00:33 Tower emhttp: shcmd (16): killall -HUP smbd (Minor Issues)

So if I install my new EARS drives with the jumper, what am I loosing? I was under the assumption that the safest and easiest thing to do was install them with the jumper always and never mess with any of this. My new parity drive is a 2tb EARS drive and its working so I guess I will just leave it be and not use the jumper when I add the others I will be adding soon.