ShangHangin

dgaschk, Thanks, I had not. I found them on the utilities page after my last post and started it running prior to going to bed. All is good now . Chalk it up to an id10t error. I will monitor the new version and hopefully it also resolves my shutdown issues of 4.7 (http://lime-technology.com/forum/index.php?topic=19470) that were resulting in a restart with continuous parity check.

Rebooting the Mac does not do it. I have fussed with the settings: With SMB enabled, and AFP off it will not let me connect only to the flash drive. If I try to connect to any other share directly (through Finder->GO->Connect to Server->pick the share, it get a message that I do not have permissions. Once connected to the flash drive, the other share appear, but can not be accessed (per my first post). With SMB and AFP enabled, I get two shared servers; one with a -SMB designation, the other not (assuming it is AFP). This does not help with access. Am I missing setting a permission somewhere? Thanks

I just upgraded from 4.7 to 5b14 hoping it would resolve my extraneous resetting and parity check issues (another topic). All went fine until I tried to look at my share drives from my Mac. I get the following error message The operation can’t be completed because the original item for “Video_Library” can’t be found. I get this for all the shares, except the flash drive, which I can access fine. I can see the disks (shared) and the associated shares but can not access, getting the following error message The folder “Video_Library” can’t be opened because you don’t have permission to see its contents. I have tried turning the shares on and off, with no luck. My original shares were created on 4.7; On 5b14, I have them shared only with SMB, Security Public (have not played with AFP yet). System: ASUS P8Z68-V LX mother board with 6 onboard SATA; Intel i5-2300, 2.8Ghz; 2-4G RAM Additional SATA card (4 port) - no name chinese card Antec 750W PSU 5- 2TB data, 1- 2TB Parity, 1- 500G Cache - all Seagate drives Antec 300 case Sony 4GB flash drive I have 3 shares that include all disks. Guidance appreciated. syslog_20120412.txt

Thanks. I have attached my latest syslog that has a few different items (sorry for my ignorance) prior to the uncontrolled shut down. i will give an upgrade to 5b014 later this week SH Apr 11 08:12:59 HAL_9000 in.telnetd[3959]: connect from 192.168.11.10 (192.168.11.10) Apr 11 08:13:01 HAL_9000 login[3960]: invalid password for `UNKNOWN' on `pts/0' from `192.168.11.10' Apr 11 08:13:03 HAL_9000 login[3960]: ROOT LOGIN on `pts/0' from `192.168.11.10' Apr 11 11:44:48 HAL_9000 emhttp: shcmd (37): /usr/sbin/hdparm -y /dev/sdc >/dev/null Apr 11 13:51:29 HAL_9000 kernel: md: sync done. time=22015sec rate=88735K/sec Apr 11 13:51:31 HAL_9000 kernel: md: recovery thread sync completion status: 0 Message from syslogd@HAL_9000 at Wed Apr 11 16:14:37 2012 ... HAL_9000 kernel: Disabling IRQ #17 Apr 11 16:14:37 HAL_9000 kernel: irq 17: nobody cared (try booting with the "irqpoll" option) Apr 11 16:14:37 HAL_9000 kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 Apr 11 16:14:37 HAL_9000 kernel: Call Trace: Apr 11 16:14:37 HAL_9000 kernel: [<c10451cf>] __report_bad_irq+0x2e/0x6f Apr 11 16:14:37 HAL_9000 kernel: [<c1045305>] note_interrupt+0xf5/0x13c Apr 11 16:14:37 HAL_9000 kernel: [<c1045a14>] handle_fasteoi_irq+0x5f/0x9d Apr 11 16:14:37 HAL_9000 kernel: [<c1004a82>] handle_irq+0x1a/0x24 Apr 11 16:14:37 HAL_9000 kernel: [<c1004285>] do_IRQ+0x40/0x96 Apr 11 16:14:37 HAL_9000 kernel: [<c1002f29>] common_interrupt+0x29/0x30 Apr 11 16:14:37 HAL_9000 kernel: [<c116d019>] ? acpi_idle_enter_bm+0x216/0x23f Apr 11 16:14:37 HAL_9000 kernel: [<c12108e8>] cpuidle_idle_call+0x63/0x9b Apr 11 16:14:37 HAL_9000 kernel: [<c1001a14>] cpu_idle+0x3a/0x4e Apr 11 16:14:37 HAL_9000 kernel: [<c128a8bf>] rest_init+0x53/0x55 Apr 11 16:14:37 HAL_9000 kernel: [<c13f580c>] start_kernel+0x27b/0x280 Apr 11 16:14:37 HAL_9000 kernel: [<c13f5091>] i386_start_kernel+0x91/0x96 Apr 11 16:14:37 HAL_9000 kernel: handlers: Apr 11 16:14:37 HAL_9000 kernel: [<f826a58b>] (sil_interrupt+0x0/0x26d [sata_sil]) Apr 11 16:14:37 HAL_9000 kernel: Disabling IRQ #17 Apr 11 17:51:33 HAL_9000 kernel: mdcmd (18): spindown 0 Apr 11 17:51:34 HAL_9000 kernel: mdcmd (19): spindown 1 Apr 11 17:51:35 HAL_9000 kernel: mdcmd (20): spindown 2 Apr 11 17:51:36 HAL_9000 kernel: mdcmd (21): spindown 3 Apr 11 17:51:37 HAL_9000 kernel: mdcmd (22): spindown 4 syslog_20120411_1.txt

OK - here is a log file through the shutdown - file attached, but here are the last few lines after I telnet'd in and fed the syslog Apr 11 06:22:31 HAL_9000 login[4931]: ROOT LOGIN on `pts/0' from `192.168.11.10' Apr 11 07:43:26 HAL_9000 kernel: mdcmd (33): spindown 0 Apr 11 07:43:27 HAL_9000 kernel: mdcmd (34): spindown 1 Apr 11 07:43:28 HAL_9000 kernel: mdcmd (35): spindown 2 Apr 11 07:43:29 HAL_9000 kernel: mdcmd (36): spindown 3 Apr 11 07:43:30 HAL_9000 kernel: mdcmd (37): spindown 4 Apr 11 07:43:31 HAL_9000 kernel: mdcmd (38): spindown 5 Thoughts? syslog_20120411.txt

Another syslog. Seems my system restarted at 2PM this afternoon while I was at work - running a parity check again! Uhg! Any thoughts on how to grab a syslog from the prior "session" to be able to better diagnose the cause of the shutdown and restart? Thanks SH syslog_20120410_2.txt

System rebooted at 1:01am on its own. Attached is the syslog as of 6:08am. I am guessing that something is causing the system to shut down (not cleanly), then restart - thus invoking a parity check. now the big question is why? I will try to capture something later that is close to the shut down. syslog_20120410.txt

Thanks - so it is normal behavior. - problem/question solved.

System: ASUS P8Z68-V LX mother board with 6 onboard SATA; Intel i5-2300, 2.8Ghz; 2-2G RAM Additional SATA card (4 port) - no name chinese card Antec 750W PSU 5- 2TB data, 1- 2TB Parity, 1- 500G Cache - all Seagate drives Antec 300 case Sony 4GB flash drive Installed 4.7 unRaid unMenu Additional Packages: "C" Compiler Mail & ssmtp UnRaid-Web 3 User Shares that include all disks.

Attached is a screen shot of the current disk usage. Disk 5 has nothing on it. Not even a directory has been created. Any thoughts?

Syslog attached. Seems my system restarted on its own this morning at 11:40AM and ran another parity check. Guidance appreciated. syslog-2012-04-09.txt

All disks are 2T seagate drives

Newbie question. A new set up running 4.7. I have set up my User shares to include all disks at split-level 3. File structure as follows: \\Server\ - Video_Library (this is the share) -Movies - <movie folder> - <movie data files - usually mkv> The splits seem to be working, as movies are spread across the disks, but the disk1 is 100% full, disk2 88%, disk3 78%, disk 4 15%, disk 5 empty. The allocation does not follow what I expected in high-water. Any thoughts?

I have just built my first unRaid - 1-2T parity, 5-2T data, 1-500G cache, running version 4.7. All has gone pretty well, but my system seems to run a parity check all the time. Yesterday, it started one are 6:01AM, continued until noon time (I was not at home); restarted another around 1PM ran until 8PM when I did a clean shut down and restart (parity has not completed). System came up and displayed parity as valid. The the system started another parity check at 1:05AM - now 87% complete at 6:20am) Since the system restart last night, there has been no new data written to the system; the only thing it has been accessed for is Plex server running on a mini-mac to pull video files a few hours prior to the 1AM parity check start. Is this normal behavior?