najames

Ok, found it, ran it. It looks like it does the same thing I did with commands. I remapped the drives in Win7 and can see the files ok now. Thanks for the help.

Uhhh, no. Where is the fix permissions script? I just followed instructions in the release notes.

I upgraded from 4.7 to 5.0Beta7. Shares created under 4.7 can no longer be accessed by my Win7 PC, but new shares I created under 5.0beta7 are accessible. It acts like there is a permission issue with the old shares. How do I fix the old shares so they can be accessed? Update: I think I have this fixed. I used the command prompt, commands below, to change permissions on the directory to match what was set under 5.0beta7. The old directories were owned by root with no RWX for anyone else. I can access files in the directories from Win7 but my "mapped drives" are still not functioning, I bet if I remap them it will work. Ditto for all the files, same commands with a wild card * for the file names. chmod 770 Videos chown nobody:users Videos

Joe and Rob, thanks for taking time to look at my log messages. Now I can move forward and try set up the file system for SageTV, then start copying recordings over from the old WHS system while I work on building a new SageTV 7 box. I'd really like to run SageTV 7 on the same unRAID box, but don't think it will work **sigh**.

Sure, I just get unRAID 4.7b1 working and the real 4.7 comes out, time to test my first update!!! My first "update" seems to be successful. I get the following warnings and errors (in bold). Any reason to be alarmed? Jan 25 04:12:08 Tower kernel: ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0000000000000000/1 (20090903/tbfadt-557) (Minor Issues) Jan 25 04:12:08 Tower kernel: ACPI Error (psargs-0359): [ECEN] Namespace lookup failure, AE_NOT_FOUND (Minor Issues) Jan 25 04:12:08 Tower kernel: ACPI Error (psparse-0537): Method parse/execution failed [\] (Node c14760c8), AE_NOT_FOUND (Minor Issues) Jan 25 04:12:08 Tower kernel: ACPI Warning: Incorrect checksum in table [OEMB] - 91, should be 8C (20090903/tbutils-314) (Minor Issues) Jan 25 04:12:08 Tower kernel: ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region SIOE [0x290-0x2af] (Minor Issues) Jan 25 04:12:08 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors) Jan 25 04:12:08 Tower kernel: ide1: DMA disabled (Errors) Jan 25 04:12:10 Tower emhttp: shcmd (14): killall -HUP smbd (Minor Issues)

Have you updated the firmware for the F4 as you haven't, then thats the first place I would start. Yup, did it before I started on this "project". You can set the MBR-4k-align option in the unRAID settings. This is what I did originally. It set the parity disk to the 64 offset, but the other two data drives were set at 63. Since I last posted, I downloaded partitionmagic (?) software, ran it from a CD, reset partitions to start at 2048, wiped my unRAID flash drive & reinstalled everything from scratch. Now with the box "MBR-4k-align" box checked it realigned all 3 disks from 2048 to 64, like I thought it would've done from the start. DOH!!! After not caring about alignment in the past, these new drives are a "learning experience". Forgot: thanks for your quick replies, it is really nice.

Thanks Joe!! I appreciate the clarification on 4.7x vs 5x forks. I tried searching but seemed to come up empty. If unRAID doesn't sleep, then it looks like when Win7 must be napping, then stopping the terminal preclearing sessions. I could see the preclear running issuing "top" in unRAID, left to run an errand, and now it's gone in top, (halted at 11% in the Win7 terminal session), so Win7 must be the culprit. I don't want to spend a lot of time pre-clearing, maybe will try to find another way to align. I am off work for 2 days and have a lot of other stuff to do. At a glance - I checked /var/log/syslog and can see where I telnet in, but nothing showing it stopped. None of the drives were precleared initally, I just stuck them in checked the alignment box, blindly hoped it would set it up correctly.

Old computer guy, new with unRAID, built a new PC, and trying to get it going using 4.71b. The PC is a Asus M4A785-M motherboard with a Sempron 140 CPU, 2x1GB RAM. I have 3 new Samsung 2TB F4 drives purchased when they first came out, but am just now using for the first time. 1) what is the difference between the 4.71b fork and the 5.0x fork of unRAID? Will I be able to upgrade from one to the other later? 2) installing unRAID was uneventful added unMenu, in 4.71b I selected the Main Menu option for using advanced format drives, but only the partition drive was listed as starting at 64, the other 2 were listed as starting at 63. Shouldn't they all have aligned to 64? I decided to stop building the array and run the preclear script with the -A flag to check the drives, clear, and align them. 3) I opened 3 telnet sessions in Win7 and started them preclearing last night at about midnight. It is now 10:30am and the preclear looks to have stopped on them. SDA is still showing 4% complete on the disk pre-read for sda & sdc. I closed one session for sdb, restarted it, seems to be running has already surpassed the other 2 sessions. It looks like the unRAID computer is going asleep and the processes hang?