BigHair

I recently upgraded from 4.03 to 5.0.5 pro and am having access problems from win7 clients. Everything went smoothly during the upgrade, parity checks complete without errors. But, every Win7 install in my house can't see more than a single subdirectoy under the dvd share. Odd thing is that the linux systems can see the contents of all subdirectories - mounted as "mount -t cifs -o ro,username=foo,password=bar //192.x.x.x/dvd /mnt/dvd Share layout: dvd dvd/combined dvd/bluRay dvd/misc dvd/junk /dvd is exported read-only, with an exception for my account(so family can access content without accidentally deleting files) The Win7 systems can see the contents of /dvd/combined; but either get 'access denied', or an empty list for the other directories. I've connected to the share via "net use * \\192.x.x.x\dvd /user:foo", and enter the correct password - can see the contents of /dvd/Combined. The linux systems see the contents of all directories fine The unraid share settings for dvd are: name:dvd AllocationMethod: mostFree min free space: 0 Split level 3 included and excluded disks are empty SMB Security settings are: Export:yes Security: Secure userAccess: foo:read-only; me:read-write SMB settings are: Enable SMB: Yes (Workgroup) Workgroup: someName LocalMaster: Yes Settings-Share Settings has Enable User Shares enabled, with empty fields for included and excluded disks The 5.0.5 gui reports that the dvd share spans 15 drives. I can see all files using the 5.0.5 gui - dvd/bluRay and others are visible. I've tried changing the workgroup of the local win7 machines to 'someName', but that did not make a difference. I did follow the release notes and clicked on Utils->"New Permissions" after upgrading. Anybody have an idea why the win7 machines can't see anything but /dvd/Combined, but the linux machines can? Thanks in advance,

Update: Tom sent me a link for the 4.7 binaries. Thanks!

The plan is for two upgrades. First to 4.7, then to V5. I'd prefer to be safe then sorry. Waiting on a link/email on where to download 4.3. Tom / Anyone: Can you please provide link to download 4.3? Thanks in advance, Nick

Alternatively - years ago when I bought Unraid I paid for two licenses. Would the following work: 1) Parity check 4.3.3 system, screenshot drive assignments, shutdown 2) Install 5.05 on 2nd USB, boot into unraid, assign same drives as 4.3.3, 3) Woud I just have to recreate the user shares? I've 14TB of data on the array that would be really painfuil to lose. I don't mind doing the multiple upgrade path, incl mult parity checks, just want to have 4TB drives installed with no data loss... Thanks in advance,

I've an Unraid 4.3.3 pro system that I'm upgrading to support 4TB drives. From the forum it seems like the recommended path is to upgrade to 4.7, then upgrade to 5.05. Some questions: 1) Is this the recommended path to upgrade a 4.3.3 system? Where can I get the 4.7 binaries? 2) Are the instructions at http://lime-technology.com/wiki/index.php/Upgrade_Instructions the ones I should follow? 3) Once the system is up and stable I'll be upgrading parity drive to 4TB HGST drives. Are there any additional steps I should take for 4TB drives? (other than normal parity drive upgrade steps) Thanks in advance, Nick

Hi All. I'm stopped on this and would really appreciate any suggestions/opinions/input... I thought that maybe the SATA port on the motherboard was bad, so I connected the drive to another port on the motherboard with a new sata cable. Once the system started drive 9 was reported as missing, so I assigned the drive to drive 9 in the devices tab (all normal up till now) The UI reports the array as "Stopped. Configuration valid", with the Start button indicating "Start will bring the array on-line and start Data-Rebuild". Alas, the symptoms remain the same, the drive shows up with an orange button. Clicking the start button just re-displays the same page, and the syslog reports the error below. Pressing the Refresh button, refreshing the page, re-connecting from a different browser on diff machine -no difference still just a re-display of the page. Jul 24 11:09:40 Tower kernel: md: do_run: lock_rdev error: -6 Any ideas/comments on where to look/change next? Some Options I've thought of include: 1) I've a second unraid USB key, originally bought two Pro licenses. I can try that USB, but not sure what that will prove. 2) upgrade to a newer version of unraid. Not sure if this will solve the problem - The drive was a replacement, not adding a new drive. 3) remove the new 2TB drive from the devices tab, start the array and copy the data off to another system. I'm a little concerned as the initial drive was 750GB, and the new drive is 2Tb - I'd hope that unraid would recreate the contents of the 750 from the parity drive, but I'm not 100% sure, as unraid right now seems to be stuck in the middle of expanding/recreating the file system, and I really don't want to lose any data. I'd have to purchase the drives for the 'other array', but if that what it takes to insure I can get to my data, the it is what it is, as it were. So some direct questions: 1) If I remove the new 2TB from the devices tab would you expect the array to start? 2) Would data be lost? 3) Has anyone hit this type of error, and what did they do to resolve? Syslog is attached, thanks in advance, unraid_syslog_after_move_2nd_sata_port.zip

Because I've not had a reason to upgrade. System has been stable until now. All previous (~11) disk upgrades went very smoothly.

I tried the new 2TB drive in another Windows system, it mounted/formatted without complaint. Then I put the 2TB drive back into the unraid system, and now all the 14 drives (+parity+cache) show up, with an orange ball next to the new 2TB drive. The text under the Start button now is just "start data rebuild", not "expand file system and start data rebuild" But when I click Start the browser just re-displays the same screen with the Start button re-enabled. If i remember from the last time I expanded the array it should have gone into a rebuild process. The tail end of the syslog has an message about a lock error: Tower kernel: md: do_run: lock_rdev error: -6 I've attached the full syslog. I'm no sure what to suspect - the SATA cables seemed well seated, the system has been running fine for a couple years without problems. I'm not adverse to picking up a new motherboard as an 'upgrade', but really, really need to have the data persisted across a possible new build. Any pointers or suggestions would be most welcome, I've a non-trivial amount of data on this system that means a great deal to me. Thanks in advance unraid_syslog_after_2ndi_Insertof2TB.zip

It does not seem to be a browser refresh problem. None of the drives that should be displayed are displayed. The syslog is complaining about failing to mount disk9: Jul 20 19:55:04 Tower emhttp: disk9 mount error: -117 I've removed the drive and will try and see if the drive works in another PC.

Hi All, I'm trying to replace a drive that was reporting read/write errors. I stopped the array, powered down the machine and swapped a 750 GB for a brand new 2TB drive. Started the machine, then went to web console and saw the new drive with the blue icon. Clicked "I want to do this"; and pressed the "Start and expand file system button". The system seems to not have found the drives after the new drive, and is stuck in a "Mounting state". The new drive was not pre-cleared, did not try and use it in another system, so perhaps the drive is bad? Any suggestions on how to proceed? My first inclination is to power the system down via a telnet window, remove the drive and see if the new 2TB mounts in another system. Syslog, and screensnaps of before/after are attached. Any suggestions? Thanks in advance syslog.zip

Hi All, Finally a chance to contribute something back. The steps above were used to successfully 'upsize' a parity disk from 750 GB to 1 TB; then the 750 GB was added back in as a data disk. Note: I did not follow bjp999's option of doing it a a 'special' case of upsizing the parity disk, as was not that concerned about the time taken in the upgrade. The steps and associated screen caps were: 1 - Ran parity check last night, no errors. This step not really required, but a sanity issue: Note the system is reporting up (all green) and no errors on any drive: 2 - stop the array Note the system is reporting Stopped, and the configuration is valid: 3 - go to devices tab, remove parity drive from configuration First image of the device list, note parity drive exists: Second image - the parity drive has been removed: Third image - went back to main tab - note message that system reporting Partiy drive missing: 4 - power down system via "powerdown" button - sorry, no image 5 - remove existing 750 GB parity drive, replace with new 1 TB drive, 750 GB drive moved to new slot in system, but SATA cable not connected 6 - power on unraid machine 7 - go to devices tab, assign 1TB drive as parity drive 8 - start the array with the "start" button Note that the "I'm sure.." checkbox had to be checked before the start button became active. 9 - wait for parity rebuild to complete First image showing disks mounting: Second image showing parity build in progress: Alas, I don't have images for the following, but it was very straightforward - power down, re-connect the SATA cable to the 750 GB, power on the system, add the 750 to the devices tab, and up it came - the 750 GB did go thru a format stage, believe I had to check "yes". Technically step 12 says start the array, but I think I did that just to see the system come up - the array will have to be stopped to added the 750 back in using the devices tab... 10 - power off array and system 11 - install 750 GB drive removed in step 5 12 - power on machine, start the array 13 - go to devices tab, add the new/old 750 GB as a data disk 14 - start the array - disk will be formatted and added to the array. 15 - Done, kick back with the Shiraz and enjoy the show Final image with system before upgrading:

Joe, bjp999: Thanks a lot for your quick responses. I saw Joe's response and immediatly proceeded with the outlines steps - currently only 5 Hrs. lefts in parity build, at about 39,000 KB/sec. I wanted to move the new 750 to a new place in the case so that the physical location of the drive matches the drive number in the devices page. The case has 3 4x3 adapters, keeping the ordering in sync makes it easier to locate a drive if/when it fails. Could write it down, but then its something else to track. Uh, I've taken screen caps of the web admin page for each step above, would be happy to post annotated copy here if someone thinks it would be usefull. Thanks again...

Hi All, I've a system with 6x 750 GB and 3x 500 GB drives; just received new 1 TB drive I would like to use as the parity drive. I think I understand the steps to replace the 750 GB parity with the new 1TB parity drive, but hoping for someone to tell me the following steps are correct. 1 - Ran parity check last night, no errors. This step not really required, but a sanity issue 2 - stop the array 3 - go to devices tab, remove parity drive from configuration 4 - power down system via "powerdown" button 5 - remove existing 750 GB parity drive, replace with new 1 TB drive 6 - power on unraid 7 - go to devices tab, assign 1TB drive as parity drive 8 - start the array with the "start" button 9 - wait for parity rebuild to complete 10 - power off array and system 11 - install 750 GB drive removed in step 5 12 - power on machine, start the array 13 - go to devices tab, add the new/old 750 GB as a data disk 14 - start the array - disk will be formatted and added to the array. From the posts I've read I should never ahve ot press the "restore" button at any time during this process Thanks in advance. FWIW: I uses UNRAID as DVD .iso server to 2 mod'ed xbox's running XBMC; also a ubuntu desktop running XBMC; and my live-in brother in law uses a mac version of XBMC. Also serves as archive for gobs of family movies off of 8mm DAT tapes. Currently not using cache drive, as I do the editing on windows box with 500 GB 'working' disk; then just start file copy before going to bed. Gigabyte EP35-DS3R; 2Gb Corsair, Kingston traveller USB stick, now waiting for 1.5 TB drives to be available.

FYI more info: It seems like its a USB key issue. After changing the key volume label to foo, then back to UNRAID, the boot message now includes a line: Mounting non-root local filesystems: mount: special device /dev/disk/by-label/UNRAID does not exist then the error message about missiing /boot/config/network.cfg - understandable as the file system did not mount. So I'm off to reformat USB and/or try another key. Will post back on final resolution...

Thanks a lot for the quick reply, but alas, still not working. I've double checked that the volume label is UNRAID - six chars only. reset it to "foo", then reset back to UNRAID I've tried capturing syslog and dmesg by copying them to /boot - I can see them there while in the cmd prompt, but they are not there after shutdown. The troubleshooting instuctions mention to run "stop", some minor messages are output - but I think normal as this is a new install and no drives are configured. The "powerdown" command was not found - I did a find from /, and it was not located; so used shutdown -h now. When look at USB key under windows the syslog.txt and dmesg.text files are missing. I bought the gigabyte board because I've read other members used it (and the 8 sata ports). The only change made to the bios was to enable AHCI FWIW I'm using UNRAID 4.2.4 I clearly get a command prompt, and ifconfig shows me the MAC address, but no IP address. The error message is from /etc/rc.d/rc.inet1.conf - its trying to use /boot/config/network.cfg as input. Any pointers / assistance would be appreciated - I'm linux handy, thought about extracting contents of bzroot/bzimage and hardcoding values in rc.inet1.conf; but that just really seems like the wrong hammer for the problem.