limetech Posted June 16, 2011 Author Share Posted June 16, 2011 madburg is right, but for me just stop the array once triggered the kernel bug: Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (100): exit status: 1 Jun 16 00:51:36 Servidor emhttp: shcmd (101): rmdir /mnt/cache >/dev/null 2>&1 Jun 16 00:51:36 Servidor emhttp: _shcmd: shcmd (101): exit status: 1 Jun 16 00:51:36 Servidor emhttp: Retry unmounting disk share(s)... Jun 16 00:51:36 Servidor kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Jun 16 00:51:36 Servidor kernel: IP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: *pdpt = 000000002e863001 *pde = 0000000000000000 Jun 16 00:51:36 Servidor kernel: Oops: 0000 [#1] SMP Jun 16 00:51:36 Servidor kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0/host0/target0:0:0/0:0:0:0/block/sdd/stat Jun 16 00:51:36 Servidor kernel: Modules linked in: bridge stp llc tun vboxnetflt vboxnetadp vboxdrv md_mod xor pata_jmicron mvsas libsas ahci jmicron r8169 libahci scsi_transport_sas asus_atk0110 hwmon Jun 16 00:51:36 Servidor kernel: Jun 16 00:51:36 Servidor kernel: Pid: 133, comm: sync_supers Not tainted 2.6.37.6-unRAID #2 System manufacturer System Product Name/M4A87TD/USB3 Jun 16 00:51:36 Servidor kernel: EIP: 0060:[<c1037e75>] EFLAGS: 00010246 CPU: 0 Jun 16 00:51:36 Servidor kernel: EIP is at queue_delayed_work_on+0x33/0xbf Jun 16 00:51:36 Servidor kernel: EAX: f8580138 EBX: ffffffff ECX: f8580134 EDX: 00000000 Jun 16 00:51:36 Servidor kernel: ESI: 00000000 EDI: f8580134 EBP: f0e0fed0 ESP: f0e0fec4 Jun 16 00:51:36 Servidor kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jun 16 00:51:36 Servidor kernel: Process sync_supers (pid: 133, ti=f0e0e000 task=f0e013e0 task.ti=f0e0e000) Jun 16 00:51:36 Servidor kernel: Stack: Jun 16 00:51:36 Servidor kernel: f8570000 ec7ed6d4 ec7ed680 f0e0fedc c10382f3 0000000a f0e0ff40 c10d2c75 Jun 16 00:51:36 Servidor kernel: f8570000 00000012 00000000 e02d2e70 006d50ee 03c0c8b0 00000000 047804db Jun 16 00:51:36 Servidor kernel: ec7ed698 00000012 00000004 f8570000 00000763 00000000 e918c000 f1b47060 Jun 16 00:51:36 Servidor kernel: Call Trace: Jun 16 00:51:36 Servidor kernel: [<c10382f3>] ? queue_delayed_work+0x1b/0x1e Jun 16 00:51:36 Servidor kernel: [<c10d2c75>] ? do_journal_end+0x7e5/0xb46 Jun 16 00:51:36 Servidor kernel: [<c10d3031>] ? journal_end_sync+0x5b/0x63 Jun 16 00:51:36 Servidor kernel: [<c10c7289>] ? reiserfs_sync_fs+0x32/0x51 Jun 16 00:51:36 Servidor kernel: [<c10c72b5>] ? reiserfs_write_super+0xd/0xf Jun 16 00:51:36 Servidor kernel: [<c107d379>] ? sync_supers+0x5e/0xa2 Jun 16 00:51:36 Servidor kernel: [<c106555b>] ? bdi_sync_supers+0x0/0x44 Jun 16 00:51:36 Servidor kernel: [<c1065590>] ? bdi_sync_supers+0x35/0x44 Jun 16 00:51:36 Servidor kernel: [<c103af7e>] ? kthread+0x62/0x67 Jun 16 00:51:36 Servidor kernel: [<c103af1c>] ? kthread+0x0/0x67 Jun 16 00:51:36 Servidor kernel: [<c1002cb6>] ? kernel_thread_helper+0x6/0x10 Jun 16 00:51:36 Servidor kernel: Code: d6 53 89 c3 f0 0f ba 29 00 19 d2 31 c0 85 d2 0f 85 9d 00 00 00 83 79 10 00 74 04 0f 0b eb fe 8d 41 04 39 41 04 74 04 0f 0b eb fe <f6> 06 02 b8 08 00 00 00 75 19 89 c8 e8 b1 e6 ff ff 85 c0 74 08 Jun 16 00:51:36 Servidor kernel: EIP: [<c1037e75>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f0e0fec4 Jun 16 00:51:36 Servidor kernel: CR2: 0000000000000000 Jun 16 00:51:36 Servidor kernel: ---[ end trace ba1b4febe6addce3 ]--- Post entire log if you have it please. Quote Link to comment
limetech Posted June 16, 2011 Author Share Posted June 16, 2011 Whatever is the problem, is appears to be related to specific configurations. Seems to be the case, thanks for trying and posting the results. I am running on: SuperMicro X8SI6-F-O (Xeon 3470) Kingston Fully Buffered ECC (2 x 4GB RAM) Onboard SAS2008 (LSI) LSI SAS 9201-16i (Add-on card) Various HD's from 2TB->160GB Hitachi Deskstar's (from 7K -> 5k) (1) Seagate 7K 250GB (1) WD 10K 80gb Reboot your server. You mentioned it is not in 'auto start' mode - good. (If not and array is started after reboot, then Stop array before next step). You need to run 'reiserfsck' on all of your data disks; and this is simpler since you don't have a parity disk. For each of your data disks: 1. Make a note of which linux device identifier it has been assigned to. This is the string in parenthesis under Identification on the Main page. For example (sdj). 2. Type this command in a telnet session: reiserfsck /dev/sdj1 <-- you put the string identified above and added a '1' The program will ask you to confirm the operation, to which you type Yes (exactly like that - upper case Y, lower case e and lower case s - hit return. The program make take several minutes to run and will output a report. If there are errors it will tell you how re-invoke reiserfsck using certain switches to correct the error - follow those instructions. Do this for all your data disks. Once complete, Start the array and repeat your testing. Note to others reading this post: These specific instructions only apply if you don't have a Parity disk. If you do have a parity disk and you invoke 'reiserfsck' in this manner, it will invalidate Parity. Quote Link to comment
sacretagent Posted June 16, 2011 Share Posted June 16, 2011 knocking wood but i have no issues at all with this new beta i had the first issue with the reebuild without format but that was my own fault ... i ran reiserfsck on dev/sdX instead of dev/mdX before so in a way i was very lucky to get my stuff back now ran already 3 parity checks and upgraded a 750 GB to a 1 tb disk with no issues start stopped the array to upgrade sabnzbd and 2 times rebooted for the good form (i know unraid will detect my new disks when the array is stopped but i still like to reboot to be sure ) thing has been more stable then before but that was probably due to that first bad disk anyway lesson learned again.... Quote Link to comment
madburg Posted June 16, 2011 Share Posted June 16, 2011 Whatever is the problem, is appears to be related to specific configurations. Seems to be the case, thanks for trying and posting the results. I am running on: SuperMicro X8SI6-F-O (Xeon 3470) Kingston Fully Buffered ECC (2 x 4GB RAM) Onboard SAS2008 (LSI) LSI SAS 9201-16i (Add-on card) Various HD's from 2TB->160GB Hitachi Deskstar's (from 7K -> 5k) (1) Seagate 7K 250GB (1) WD 10K 80gb Reboot your server. You mentioned it is not in 'auto start' mode - good. (If not and array is started after reboot, then Stop array before next step). You need to run 'reiserfsck' on all of your data disks; and this is simpler since you don't have a parity disk. For each of your data disks: 1. Make a note of which linux device identifier it has been assigned to. This is the string in parenthesis under Identification on the Main page. For example (sdj). 2. Type this command in a telnet session: reiserfsck /dev/sdj1 <-- you put the string identified above and added a '1' The program will ask you to confirm the operation, to which you type Yes (exactly like that - upper case Y, lower case e and lower case s - hit return. The program make take several minutes to run and will output a report. If there are errors it will tell you how re-invoke reiserfsck using certain switches to correct the error - follow those instructions. Do this for all your data disks. Once complete, Start the array and repeat your testing. Note to others reading this post: These specific instructions only apply if you don't have a Parity disk. If you do have a parity disk and you invoke 'reiserfsck' in this manner, it will invalidate Parity. Thank you Tom, I have just completed the reiserfs checks on all the drives, attaching log "reiserfs_log.txt" to this post for your review. I only notice there was a journal replay on the cache drive (the last drive in the log). It only has 2 directories on it. I never had a hung system with these drives before until testing this release. Probably this jornaling on this one drive was caused by this. In either case, what do you recommend I do now. Proceed to start the array and test again? I dont believe the reiserfs log shows anything that would cause unRAID to behave like it is doing so. But I will proceed to do whatever you recommend, let me know. P.S. unless i am mistaken (first time ever running reiserfsck) I did not see anything calling/requesting for a repair. Reiserfs_log.txt Quote Link to comment
mvdzwaan Posted June 16, 2011 Share Posted June 16, 2011 I have ust built a new test server with 2 3Tb disks (WD EZRS) attached to the Highpoint Rocket 620 controllers which came with the cards. Tried madburg's test case but after a spindown the data drive spins up within a couple of seconds so I cannot test your scenario. I do have spindown troubles, auto spindown never works, and manual spindown works for a couple of seconds. Quote Link to comment
madburg Posted June 16, 2011 Share Posted June 16, 2011 I have ust built a new test server with 2 3Tb disks (WD EZRS) attached to the Highpoint Rocket 620 controllers which came with the cards. Tried madburg's test case but after a spindown the data drive spins up within a couple of seconds so I cannot test your scenario. I do have spindown troubles, auto spindown never works, and manual spindown works for a couple of seconds. Make sure you are not running any add-ons at ALL for your first tests. for "auto spindown never works" try this, Change your global disk settings to the smallest time frame (15 mins, this is under disk settings), on the main web page click on each disk to get to their individual settings and just click the "apply" button on each one (one by one). Then once again on the main page look at the upper right corner you will see the word "log" click it, it will open another browser window, watch it and see what it say's in 15 minutes. Quote Link to comment
mvdzwaan Posted June 16, 2011 Share Posted June 16, 2011 I have ust built a new test server with 2 3Tb disks (WD EZRS) attached to the Highpoint Rocket 620 controllers which came with the cards. Tried madburg's test case but after a spindown the data drive spins up within a couple of seconds so I cannot test your scenario. I do have spindown troubles, auto spindown never works, and manual spindown works for a couple of seconds. Make sure you are not running any add-ons at ALL for your first tests. for "auto spindown never works" try this, Change your global disk settings to the smallest time frame (15 mins, this is under disk settings), on the main web page click on each disk to get to their individual settings and just click the "apply" button on each one (one by one). Then once again on the main page look at the upper right corner you will see the word "log" click it, it will open another browser window, watch it and see what it say's in 15 minutes. It's a clean install so no addons, the not working auto spindown should be solved when the manual spindown starts working. I can spindown/spinup without problem, never had the unformatted error you got. I'll dig into my syslog to see which process keeps accessing the data disk and spins it up. Quote Link to comment
bcbgboy13 Posted June 17, 2011 Share Posted June 17, 2011 I also upgraded a week ago. Parity check was fine but with the usual speed (the initial estimates of under 6 hours did not materialize) madburg test (spin up, spin down, spin up, spin down, stop, reboot - controlled with power meter) performed a few times - no problem whatsoever. (knock on wood) Hardware used: Biostar TA790GX 4 GB ECC DDR2 (2 x 2GB HP Smart Buy) 750W UPS 10 HDs (from 1 to 2 TB) One Supermicro AOC-SASLP-MV8 One M1015 flashed to LSI IT BIOS (for now diskless) No cache disk and only Unmenu. I am going to preclear a 3TB disk now and probably unavailable for 36- 40 hours??? Quote Link to comment
EdgarWallace Posted June 17, 2011 Share Posted June 17, 2011 I just upgraded from 5.0-beta6a to 5.0-beta7 without any hassle. Parity Check was running without any error. The upgrade can't be easier. Thanks for that. Quote Link to comment
Joe L. Posted June 17, 2011 Share Posted June 17, 2011 Bug in user-share names with "&" in their name in 5.0beta7. (Possibly in earlier versions too) See here: http://lime-technology.com/forum/index.php?topic=13518.msg128163#msg128163 Joe L. Quote Link to comment
madburg Posted June 17, 2011 Share Posted June 17, 2011 Just an FYI, dont know if this is normal behavior. I inserted my new 3TB (5K) into the unRAID chassis before leaving to work at 9:43am. Once I got to the office I vpn'ed in to my network and rdp'ed into my desktop, refresh the unRAID gui, on the Main Page (array was stop since yesturday waiting on Tom's response to my reiserfsck log i posted), I select an available disk# that was unassigned, click the drop down to see if the drive could be seen and could be added to the array, there was no sign of it. So I figured I should telnet in and see if preclear_disk.sh would see it via "preclear_disk.sh -L", which it did, so I went to check the syslog via the unRAID "Utils" tab. Here is when I inserted the drive: Jun 17 09:43:49 PNTower kernel: scsi 0:0:6:0: Direct-Access ATA Hitachi HDS5C303 A580 PQ: 0 ANSI: 5 Jun 17 09:43:49 PNTower kernel: scsi 0:0:6:0: SATA: handle(0x0017), sas_addr(0x4433221102000000), phy(2), device_name(0x0000000000000000) Jun 17 09:43:49 PNTower kernel: scsi 0:0:6:0: SATA: enclosure_logical_id(0x500062b200094f40), slot(2) Jun 17 09:43:49 PNTower kernel: scsi 0:0:6:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) Jun 17 09:43:49 PNTower kernel: scsi 0:0:6:0: qdepth(32), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) Jun 17 09:43:49 PNTower kernel: sd 0:0:6:0: [sdp] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jun 17 09:43:49 PNTower kernel: sd 0:0:6:0: [sdp] Write Protect is off Jun 17 09:43:49 PNTower kernel: sd 0:0:6:0: [sdp] Mode Sense: 73 00 00 08 Jun 17 09:43:49 PNTower kernel: sd 0:0:6:0: [sdp] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 17 09:43:49 PNTower kernel: sdp: unknown partition table Jun 17 09:43:49 PNTower kernel: sd 0:0:6:0: [sdp] Attached SCSI disk Then there were no events until I telneted in, and that seemed to kick of a drive available refresh (for a lack of better words): Jun 17 11:23:24 PNTower emhttp: shcmd (48): rmmod md-mod 2>&1 |logger Jun 17 11:23:24 PNTower emhttp: shcmd (49): udevadm settle Jun 17 11:23:24 PNTower emhttp: Device inventory: %ALL MY DRIVES HERE LIST ONE BY ONE%, BELOW IS THE 3TB Drive assign sdp Jun 17 11:23:24 PNTower emhttp: Hitachi_HDS5C3030ALA630_MJ1311YNG0TA1A (sdp) 2930266584 So I went back to the WebGUi, now when I hit the drop down the drive was seen and available to be added to the array. Again this is just an FYI, dont know if this is normal behavior. Quote Link to comment
madburg Posted June 17, 2011 Share Posted June 17, 2011 Whatever is the problem, is appears to be related to specific configurations. Seems to be the case, thanks for trying and posting the results. I am running on: SuperMicro X8SI6-F-O (Xeon 3470) Kingston Fully Buffered ECC (2 x 4GB RAM) Onboard SAS2008 (LSI) LSI SAS 9201-16i (Add-on card) Various HD's from 2TB->160GB Hitachi Deskstar's (from 7K -> 5k) (1) Seagate 7K 250GB (1) WD 10K 80gb Reboot your server. You mentioned it is not in 'auto start' mode - good. (If not and array is started after reboot, then Stop array before next step). You need to run 'reiserfsck' on all of your data disks; and this is simpler since you don't have a parity disk. For each of your data disks: 1. Make a note of which linux device identifier it has been assigned to. This is the string in parenthesis under Identification on the Main page. For example (sdj). 2. Type this command in a telnet session: reiserfsck /dev/sdj1 <-- you put the string identified above and added a '1' The program will ask you to confirm the operation, to which you type Yes (exactly like that - upper case Y, lower case e and lower case s - hit return. The program make take several minutes to run and will output a report. If there are errors it will tell you how re-invoke reiserfsck using certain switches to correct the error - follow those instructions. Do this for all your data disks. Once complete, Start the array and repeat your testing. Note to others reading this post: These specific instructions only apply if you don't have a Parity disk. If you do have a parity disk and you invoke 'reiserfsck' in this manner, it will invalidate Parity. Thank you Tom, I have just completed the reiserfs checks on all the drives, attaching log "reiserfs_log.txt" to this post for your review. I only notice there was a journal replay on the cache drive (the last drive in the log). It only has 2 directories on it. I never had a hung system with these drives before until testing this release. Probably this jornaling on this one drive was caused by this. In either case, what do you recommend I do now. Proceed to start the array and test again? I dont believe the reiserfs log shows anything that would cause unRAID to behave like it is doing so. But I will proceed to do whatever you recommend, let me know. P.S. unless i am mistaken (first time ever running reiserfsck) I did not see anything calling/requesting for a repair. I repeated all steps today after running and posting the 'reiserfsck' log. This time reboot succeeded. Attaching a full tail log from beginning to end, should Tom wish to review it to see and notice anything else for the future. I hope this ends the issue I ran into and never comes back , I will keep monitoring and testing forward. If the journaling on the cache drive is what caused this (and no repair was required) then I am OK with it, not sure how it could have happend thought. On to 3TB preclear testing now. tail_log2.txt Quote Link to comment
madburg Posted June 17, 2011 Share Posted June 17, 2011 I also upgraded a week ago. Parity check was fine but with the usual speed (the initial estimates of under 6 hours did not materialize) madburg test (spin up, spin down, spin up, spin down, stop, reboot - controlled with power meter) performed a few times - no problem whatsoever. (knock on wood) Hardware used: Biostar TA790GX 4 GB ECC DDR2 (2 x 2GB HP Smart Buy) 750W UPS 10 HDs (from 1 to 2 TB) One Supermicro AOC-SASLP-MV8 One M1015 flashed to LSI IT BIOS (for now diskless) No cache disk and only Unmenu. I am going to preclear a 3TB disk now and probably unavailable for 36- 40 hours??? IF you can, and its not production or you feel comfortable, shutdown and move some of your existing disk to the M1015 to test. Quote Link to comment
limetech Posted June 17, 2011 Author Share Posted June 17, 2011 I bit the bullet and updated. I thought I was prepared but I had overlooked the one time permision reset and the PHP could not be installed by unmenu. I do see the bug where unmenu does not show the unraid main but if you go directly it works... It does work some times I just dont know why. the rest looks really good I am using my UPS and Twonky media with no problems. Here are a few lines in my syslog I dont understand. syslog attached. Jun 12 13:54:24 Dragon-Tower kernel: ide0: BM-DMA at 0xff00-0xff07 Jun 12 13:54:24 Dragon-Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors) Jun 12 13:54:24 Dragon-Tower kernel: ide1: DMA disabled (Errors) Jun 12 13:54:24 Dragon-Tower kernel: Probing IDE interface ide0... Refer to this thread: http://lime-technology.com/forum/index.php?topic=4810.0 Jun 12 15:15:18 Dragon-Tower kernel: twonkymediaserv[1391]: segfault at 30d0 ip 0806db70 sp b76a8af0 error 4 in twonkymediaserver[8048000+69000] (Errors) This one is not good, says that a twonkymediaserv process crashed (probably due to programming error). Sorry can't help with this one. Jun 12 15:40:01 Dragon-Tower crond[1232]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jun 12 This was fixed several releases back, should not occur with -beta7. Can't explain it, perhaps an add-on? Quote Link to comment
defected07 Posted June 17, 2011 Share Posted June 17, 2011 Jun 12 15:40:01 Dragon-Tower crond[1232]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jun 12 This was fixed several releases back, should not occur with -beta7. Can't explain it, perhaps an add-on? I get this error all the time too. Still on 5.0b6a, but plan on updating this weekend. I do have a lot of add-ons installed, but I'm not sure which it could be. Is it an add-on that's trying to run as "root-" possibly? Where was it in the previous builds that you corrected it, limetech? I'll try to grep for "root-" on my system this evening. Quote Link to comment
Joe L. Posted June 17, 2011 Share Posted June 17, 2011 I bit the bullet and updated. I thought I was prepared but I had overlooked the one time permision reset and the PHP could not be installed by unmenu. I do see the bug where unmenu does not show the unraid main but if you go directly it works... It does work some times I just dont know why. the rest looks really good I am using my UPS and Twonky media with no problems. Here are a few lines in my syslog I dont understand. syslog attached. Jun 12 13:54:24 Dragon-Tower kernel: ide0: BM-DMA at 0xff00-0xff07 Jun 12 13:54:24 Dragon-Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled (Errors) Jun 12 13:54:24 Dragon-Tower kernel: ide1: DMA disabled (Errors) Jun 12 13:54:24 Dragon-Tower kernel: Probing IDE interface ide0... Refer to this thread: http://lime-technology.com/forum/index.php?topic=4810.0 Jun 12 15:15:18 Dragon-Tower kernel: twonkymediaserv[1391]: segfault at 30d0 ip 0806db70 sp b76a8af0 error 4 in twonkymediaserver[8048000+69000] (Errors) This one is not good, says that a twonkymediaserv process crashed (probably due to programming error). Sorry can't help with this one. Jun 12 15:40:01 Dragon-Tower crond[1232]: ignoring /var/spool/cron/crontabs/root- (non-existent user) Jun 12 This was fixed several releases back, should not occur with -beta7. Can't explain it, perhaps an add-on? most all the add-ons that add cron entries create this file because older releases of unRAID used it instead of re-reading the output of crontab -l. Therefore, to fix it is easy, delete the file in /var/spool/cron/crontabs/root- or ignore the warning, it is harmless. Quote Link to comment
prostuff1 Posted June 17, 2011 Share Posted June 17, 2011 I believe my DS_Store package still create the root- file. I have not updated it to work with both unRAID 4.7 and 5.0bX series. It should not be overly difficult, just have not had the time. And as Joe L. mentioned the message is harmless, so I have not felt pressed to fix the little "error" message that happens. Quote Link to comment
dertbv Posted June 17, 2011 Share Posted June 17, 2011 I am currently running the release version (4.7) with a drive mounted outside of the array (/dev/sdk). When I try to upgrade it mounts the wrong drive causing it to give the error missing drive. When I remove the commands to mount the drive outside of the array, it boots fine. But the drive that I want out side of the array is still showing as /dev/sdk. Is there a way to get the drive to mount outside of the array. what am i missing.. Quote Link to comment
Joe L. Posted June 17, 2011 Share Posted June 17, 2011 I am currently running the release version (4.7) with a drive mounted outside of the array (/dev/sdk). When I try to upgrade it mounts the wrong drive causing it to give the error missing drive. When I remove the commands to mount the drive outside of the array, it boots fine. But the drive that I want out side of the array is still showing as /dev/sdk. Is there a way to get the drive to mount outside of the array. what am i missing.. The specific drive letters may change from one release to another, and in fact, from one boot to another. Since this is apparently a customization, and nothing to do with 5.0-beta7, post the exact commands you are attempting to use AND a syslog in the customizations forum. Quote Link to comment
najames Posted June 18, 2011 Share Posted June 18, 2011 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 Quote Link to comment
BRiT Posted June 18, 2011 Share Posted June 18, 2011 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? Did you run the FIX PERMISSIONS script? Quote Link to comment
najames Posted June 18, 2011 Share Posted June 18, 2011 Uhhh, no. Where is the fix permissions script? I just followed instructions in the release notes. Quote Link to comment
Joe L. Posted June 18, 2011 Share Posted June 18, 2011 Did you run the "Permissions" utility program, as described in the upgrade instructions? Quote Link to comment
SCSI Posted June 18, 2011 Share Posted June 18, 2011 Uhhh, no. Where is the fix permissions script? I just followed instructions in the release notes. Check under "Utils" page of the Unraid web interface. Quote Link to comment
najames Posted June 18, 2011 Share Posted June 18, 2011 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. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.