tr0910

Either I am doing something stupid or this is an issue with 5b12a. I have the following script that backs up one server to another. Works fine from 4.7 to 4.7 and from 4.7 to 5b12a where it is run on a 5b12a polling a 4.7 server. It doesn't work from a 4.7 server polling a 5b12a server. Locks up, and the script sits after 8 hours. Do I have to do something else to get rsync to work when polling a 5b12a server?? mkdir /mnt/t2disk1 mkdir /mnt/t2disk2 mkdir /mnt/t2disk3 mount -t nfs tower2:/mnt/disk1/ /mnt/t2disk1 mount -t nfs tower2:/mnt/disk2/ /mnt/t2disk2 mount -t nfs tower2:/mnt/disk3/ /mnt/t2disk3 cd /boot echo ++ >> date.log echo ++++++ starting daily cron now ++++++++++ >> date.log # Backup Disk 3 # log to disk 1 so there are no conflicts with files echo ++++++ starting daily cron now with disk 3 ++++++++++ >> /mnt/disk1/disk3.log rsync -av --stats --progress /mnt/t2disk3/ /mnt/disk3/ >> /mnt/disk1/disk3.log date >> date.log date >> /mnt/disk1/disk3.log echo == >> date.log echo ====== ending daily cron now =========== >> date.log echo == >> date.log echo =___ powering down now ___= >> date.log powerdown There is no activity on the disks of either server and here is the list of processes on the 4.7 server running the script. Notice 3 instances of rsync that are inactive. When rsync is running, this will take up significant cpu.... (from /usr/bin/top -b -n1) top - 09:22:32 up 1 day, 10:39, 2 users, load average: 2.00, 1.99, 1.91 Tasks: 94 total, 1 running, 93 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 3.9%sy, 0.0%ni, 65.6%id, 30.1%wa, 0.1%hi, 0.3%si, 0.0%st Mem: 1814388k total, 1748560k used, 65828k free, 4176k buffers Swap: 0k total, 0k used, 0k free, 1665520k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 704 308 264 S 0.0 0.0 0:01.46 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd 3 root RT 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0 5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0 6 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 async/mgr 112 root 20 0 0 0 0 S 0.0 0.0 0:00.11 sync_supers 114 root 20 0 0 0 0 S 0.0 0.0 0:00.00 bdi-default 116 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kblockd/0 117 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpid 118 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpi_notify 119 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kacpi_hotplug 228 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ata/0 229 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ata_aux 233 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksuspend_usbd 238 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khubd 241 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kseriod 277 root 20 0 0 0 0 S 0.0 0.0 0:00.04 rpciod/0 302 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kswapd0 347 root 20 0 0 0 0 S 0.0 0.0 0:00.00 aio/0 353 root 20 0 0 0 0 S 0.0 0.0 0:00.03 nfsiod 358 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kslowd000 359 root 15 -5 0 0 0 S 0.0 0.0 0:00.00 kslowd001 579 root 20 0 0 0 0 S 0.0 0.0 0:00.00 usbhid_resumer 618 root 16 -4 1872 804 480 S 0.0 0.0 0:00.04 udevd 692 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_0 695 root 20 0 0 0 0 S 0.0 0.0 0:00.02 usb-storage 767 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_1 768 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_2 769 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_3 770 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_4 771 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_5 772 root 20 0 0 0 0 S 0.0 0.0 0:00.00 scsi_eh_6 1239 root 20 0 1688 592 504 S 0.0 0.0 0:00.01 syslogd 1243 root 20 0 1640 412 340 S 0.0 0.0 0:00.00 klogd 1282 root 20 0 1656 464 392 S 0.0 0.0 0:00.00 ifplugd 1312 root 20 0 1656 388 312 S 0.0 0.0 0:02.23 dhcpcd 1319 root 20 0 3916 1216 948 S 0.0 0.1 0:00.00 ntpd 1329 bin 20 0 1752 476 392 S 0.0 0.0 0:00.00 rpc.portmap 1333 nobody 20 0 1808 704 608 S 0.0 0.0 0:00.00 rpc.statd 1343 root 20 0 1664 528 464 S 0.0 0.0 0:00.01 inetd 1353 root 20 0 1632 536 468 S 0.0 0.0 0:00.00 acpid 1360 root 20 0 1816 660 548 S 0.0 0.0 0:00.00 crond 1362 daemon 20 0 1672 384 304 S 0.0 0.0 0:00.00 atd 1367 root 20 0 8488 1928 1316 S 0.0 0.1 0:00.63 nmbd 1369 root 20 0 13624 3364 2600 S 0.0 0.2 0:00.42 smbd 1373 root 20 0 13624 1724 960 S 0.0 0.1 0:00.00 smbd 1375 root 20 0 52764 1532 1148 S 0.0 0.1 0:00.63 emhttp 1447 root 20 0 0 0 0 S 0.0 0.0 11:39.55 mdrecoveryd 1451 root 20 0 0 0 0 S 0.0 0.0 0:00.00 spinupd 1453 root 20 0 0 0 0 S 0.0 0.0 0:00.00 spinupd 1455 root 20 0 0 0 0 S 0.0 0.0 0:00.00 spinupd 1457 root 20 0 0 0 0 S 0.0 0.0 0:00.00 spinupd 1458 root 20 0 0 0 0 S 0.0 0.0 0:00.00 spinupd 1739 root 20 0 0 0 0 S 0.0 0.0 0:00.00 lockd 1766 root 20 0 0 0 0 S 0.0 0.0 70:38.25 unraidd 1801 root 20 0 0 0 0 S 0.0 0.0 0:00.00 reiserfs/0 1849 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1850 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1851 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1852 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1853 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1854 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1855 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1856 root 20 0 0 0 0 S 0.0 0.0 0:00.00 nfsd 1858 root 20 0 1912 280 168 S 0.0 0.0 0:00.00 rpc.mountd 2663 root 20 0 1636 520 456 S 0.0 0.0 0:00.00 agetty 2664 root 20 0 1632 520 456 S 0.0 0.0 0:00.00 agetty 2665 root 20 0 1636 524 456 S 0.0 0.0 0:00.00 agetty 2666 root 20 0 1632 520 456 S 0.0 0.0 0:00.00 agetty 2667 root 20 0 1632 520 456 S 0.0 0.0 0:00.00 agetty 2668 root 20 0 1636 524 456 S 0.0 0.0 0:00.00 agetty 3138 root 20 0 1856 760 620 S 0.0 0.0 0:00.00 in.telnetd 3139 root 20 0 2376 1320 1060 S 0.0 0.1 0:00.00 bash 3178 root 20 0 2492 832 680 S 0.0 0.0 0:00.00 screen 3179 root 20 0 2516 988 708 S 0.0 0.1 0:00.00 screen 3180 root 20 0 2392 1272 1000 S 0.0 0.1 0:00.00 bash 3181 root 20 0 2400 1284 1008 S 0.0 0.1 0:00.00 bash 3186 root 20 0 2264 488 316 S 0.0 0.0 0:00.00 uu 3187 root 20 0 1616 440 384 S 0.0 0.0 0:00.00 logger 3190 root 20 0 4828 3856 904 S 0.0 0.2 0:00.12 awk 3318 root 20 0 14000 4020 2908 S 0.0 0.2 0:00.33 smbd 6444 root 20 0 2404 936 656 S 0.0 0.1 0:00.00 bash 6447 root 20 0 18216 1932 828 D 0.0 0.1 0:03.28 rsync 6448 root 20 0 17432 1340 592 S 0.0 0.1 0:00.00 rsync 6449 root 20 0 18124 1344 328 S 0.0 0.1 0:04.60 rsync 6529 root 20 0 1652 608 540 D 0.0 0.0 0:00.00 df 6534 root 20 0 2260 484 316 S 0.0 0.0 0:00.00 uu 6535 root 20 0 1616 552 484 S 0.0 0.0 0:00.00 logger 6538 root 20 0 4696 3668 888 S 0.0 0.2 0:00.14 awk 6908 root 20 0 2104 932 748 S 0.0 0.1 0:00.01 gawk 6911 root 20 0 2228 976 844 S 0.0 0.1 0:00.00 sh 6912 root 20 0 2116 896 700 R 0.0 0.0 0:00.00 top

In everything in life, you pays your money and you takes your chances..... While I understand and share the frustration, having just purchased 2 more pro keys in anticipation of ver 5, I have to admit that what we have now is still pretty good. We just all have very high expectations.....

It appears that the problem is that ver 5 has NFS turned off by default, and I couldn't find out how it was turned on. Once I figured out that you just click the disk on the main screen, and you can set the export via SMB and via NFS from there, it was real easy.

It looks like NFS was enabled, but I reenabled it from the menu. Had to restart NFS again though. Still getting root@Tower1:~# mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1 mount.nfs: access denied by server while mounting 192.168.1.106:/mnt/disk1 root@Tower1:~#

Here is what it give back: root@Tower1:~# mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1 mount.nfs: access denied by server while mounting 192.168.1.106:/mnt/disk1 root@Tower1:~# I realized that i entered the nfs restart on the wrong machine..... dumb.... dumb.... When I did it right: root@Server1:~# showmount -e clnt_create: RPC: Program not registered root@Server1:~# showmount -e clnt_create: RPC: Program not registered root@Server1:~# /etc/rc.d/rc.nfsd restart Starting NFS server daemons: /usr/sbin/exportfs -r /usr/sbin/rpc.nfsd 8 /usr/sbin/rpc.mountd root@Server1:~# showmount -e Export list for Server1: root@Server1:~# I realized this and fixed it before I entered your command above.... Looks like a permissions issue now?? I have no users or security set up on server1 at all. Only the root account has a password, and there are no other users.

Same result going directly to the ip address. Here is what I did edit the following was entered on the wrong machine root@Tower1:~# showmount -e Export list for Tower1: /mnt/disk4 * /mnt/disk3 * /mnt/disk2 * /mnt/disk1 * root@Tower1:~# /etc/rc.d/rc.nfsd restart | logger root@Tower1:~# showmount -e Export list for Tower1: /mnt/disk4 * /mnt/disk3 * /mnt/disk2 * /mnt/disk1 * root@Tower1:~# mkdir /mnt/s1disk1 mkdir: cannot create directory `/mnt/s1disk1': File exists root@Tower1:~# mount -t nfs server1:/mnt/disk1/ /mnt/s1disk1 mount.nfs: mount to NFS server 'server1:/mnt/disk1/' failed: RPC Error: Program not registered root@Tower1:~# Not sure if I restarted nfs correctly though.... Thanks so much for the tips....

Thanks, here is are the servers. Server1 192.168.1.106 5b12a Tower1 192.168.1.118 4.7 Tower2 192.168.1.139 4.7 The results from 5b12a server1: root@Server1:~# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Server1:~# rpcinfo -p 192.168.1.118 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd root@Server1:~# rpcinfo -p 192.168.1.139 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd The results from Tower1 running 4.7 calling the other 2 machines with 106 being the 5b12a machine. root@Tower1:/boot# rpcinfo -p 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd root@Tower1:/boot# rpcinfo -p 192.168.1.106 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Tower1:/boot# rpcinfo -p 192.168.1.139 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd and from the other 4.7 machine Tower2: root@Tower2:~# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd root@Tower2:~# rpcinfo -p 192.168.1.106 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Tower2:~# rpcinfo -p 192.168.1.118 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd

I do the following on 4.7 from one 4.7 server to another successfully, but this isn't working when connecting from a 4.7 server to a 5b12a server. (Tower1 is 4.7 and server1 is 5b12a) root@Tower1:/boot# mkdir /mnt/s1disk1 root@Tower1:/boot# mount -t nfs server1:/mnt/disk1/ /mnt/s1disk1 mount.nfs: mount to NFS server 'server1:/mnt/disk1/' failed: RPC Error: Program not registered What am I doing wrong??

l have a mixed environment 4.7 and 5b12a servers. Presently the 5b12a is a backup of the 4.7 server, and this happens by rsync. The problem, is each time rsync runs, I lose the ability to access some of the files from Win7 Ult on the 5b12a server. I get: Windows cannot access \\server1\disk3\pix2011\etc.... Yet on other folders access is still possible. Running the permissions script seems to fix everything, but I cannot run this every day. Is there a way to have the permissions correctly set by rsync, or is this not possible...

Even with no data on a 3tb drive? My 3 tb drives are parity, and an empty data drive. I can clobber them without a problem. I have 4 other 2tb drives loaded with data, and one empty 2tb drive. I've switched to my backup flash drive to see if the problem is related to the flash drive and unRaid is back up running again.

Another issue with the flash drive going read only, and likely corrupted. Packages directory on the flash was clobbered again. (syslog attached.) After the last problem, I successfully did a parity check, rebooted the server, and everything has been fine until now. I may need to go back to 4.7 on this server. What is the recommended procedure to go back? I have 3tb drives that I will first have to downsize to 2.2 via: http://lime-technology.com/forum/index.php?topic=11183.30 Hardware: Supermicro X9SCM-F Intel i3-2100 and 4 gig RAM Supermicro AOC-SASLP-MV8 8-Port all in a Norco 4224 syslog-2011-10-05.zip

Nothing would stop unRaid at all. Even "shutdown now" would try but get no results. After successfully stopping the array, I shut the power off, and pulled the flash drive, mounted it in Windows and ran chkdsk fixing file system errors in the "package" directory. After fixing, the packages directory was gone and I reloaded it from a backup that I had done of the usb drive a few days earlier. Server is back up again, and parity is still valid. Syslog doesn't show any errors with the flash drive. Is this a one time event, or are others having problems with flash drive corruption too??? (Background, the server was just completing its first successful parity check when it went cuckoo)

I'm trying, but the server is going unresponsive. Powerdown from the command line doesn't work. The shutdown command is still available though. Is that any better then just pulling the power cord? Any other ideas? Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: Oops: 0000 [#1] SMP Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: Process umount (pid: 8260, ti=f7610000 task=f0368360 task.ti=f7610000) Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: Stack: Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: Call Trace: Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: EIP: [<c1038811>] queue_delayed_work_on+0x33/0xbf SS:ESP 0068:f7611e34 Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 kernel: CR2: 0000000000000000 Message from syslogd@Server1 at Mon Oct 3 13:30:18 2011 ... Server1 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 02 e5 ff ff 85 c0 74 08

Lost write access to the usbkey after a lengthly 3 day server load. I've attached the syslog below. Oct 3 08:07:12 Server1 kernel: FAT-fs (sde1): error, fat_get_cluster: invalid cluster chain (i_pos 0) Oct 3 08:07:12 Server1 kernel: FAT-fs (sde1): Filesystem has been set read-only Oct 3 08:07:12 Server1 kernel: FAT-fs (sde1): error, fat_get_cluster: invalid cluster chain (i_pos 0) My unMenu package manager screen has gone blank, and it reports: "No Packages defined in package configuration file(s)" Do I have problems with the usb boot key, or is this a software problem? (beta 12a running for 7 days otherwise fine and no indication of these errors in previous syslogs) syslog-2011-10-03.zip

Now I know why this drive had an HPA... It was hooked up to a Gigabyte motherboard for only a few minutes to adjust the partition size with Gparted when this disk was installed into a Linkstation Pro. In these few minutes, the dirty work was done.

Great, that is equivalent to 4 billion - 2tb drives. Not in my lifetime am I likely to have to worry about it.... This reminds me of: "640K should be enough for anybody" - Bill Gates 1981 http://en.wikiquote.org/wiki/Bill_Gates

I have a b12a server starting the testing process. Just preclearing 3 tb drives now. Sorry, no problems to report yet. Supermicro X9SCM-F Intel i3-2100 and 4 gig RAM Supermicro AOC-SASLP-MV8 8-Port all in a Norco 4224 But I do have a question. With ver 5, how large a drive will unRaid support? 4tb drives are just announced, and 5tb drives are likely soon after that. When do we hit the next wall requiring major software retooling like is going on right now with the ver 5 betas....

Thanks, I noticed the monoprice ones, but was trying to find a 7 to 1 splitter like the Norco one, and no luck....

Should the 4224 come with molex splitters for the backplane. (I ordered from Raj's recommended prototype list for a 24 drive beast, and no molex splitters were identified.) Mine arrived with nothing. Need 6 molex for the drive backplane, one for the midwall fans, and one for the back of the case. My powersupply only has 3 molex connectors. Is there any better place to get these splitters than the Norco ones from Newegg, http://www.newegg.com/Product/Product.aspx?Item=N82E16816133040

I thought I had it set up right, but there is a diff between * (rw) and *(rw). I've updated and corrected that. Are you sure that that warning is the source of this problem?

Yesterday 9/12 at noon in particular, it got real bad. I've attached the logs for several days. I had this happen one other time, and the solution seemed to be to reboot the server. At that time it went away and never returned. Since that time, I've built a clone of that server. Now it happens to my newly built twin of tower1. Can anyone see anything my logs that are questionable? I've had to reboot the server as it gets used lots.... Unraid 4.7 on an Asus m4a785m mb AMD 140 with 2 GB ram, and all 6 Sata ports connected to 2TB drives. syslog-20110913-081045.zip

Well it is rebooted, and running fine. Can't remember if that erases the log file or not. Other than the long delay in accessing files, it seemed to perform well once it was reading and writing. It was real puzzling. If it does it again, I will call for help before rebooting.

I have an unRaid 4.7 box that has seen heavy use in the last few months without being shut down. Lately it has been very sluggish when accessing files. Sometimes you can wait over a minute before it responds to a directory listing, or a file request. I shut it down and restarted it, and all is back to normal. Is this expected behavior? How long can you go between reboots?

I guess there was a reason why Google couldn't find anyone using it with unRaid. Thanks all....

So nobody has used it?? I have no plans of being a pioneer. I'll go with the one of the tried and true ones. Here in Canada, we pay way more for the same unit, and this one was at least comparable with the US price, and had additional capability to manage over the internet. OH well.....