zryder

Well, this gets even more interesting. After hitting the refresh button every hour or so, it finally finished a parity check this morning. Came back to work, and I proceeded to upload a file to the server just fine. It is currently uploading a file to the server, but I am unable to reach the unraid gui from the web browser. I am not able to post a syslog at the moment, due to not being able to access the gui. I know this isn't much info to go on, but I could really use some help. Thanks everyone.

So back in the day, I reverted to 4.7, and everything worked just great. Last night I upgraded to 5.13, and it wanted to rebuild parity. I let it start doing this, and went to bed. Woke up without being able to access the server again. Same symptoms as before.

it is responding at the moment, due to me writing things to it. it typically seems to go for 4-5 hours at least, but it wasnt responding when i came home to it this evening.

oot@Tower:~# free -m total used free shared buffers cached Mem: 2024 288 1735 0 4 210 -/+ buffers/cache: 73 1951 Swap: 0 0 0 root@Tower:~# top top - 21:48:29 up 5 min, 1 user, load average: 1.33, 0.85, 0.38 Tasks: 86 total, 2 running, 84 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 13.7%sy, 0.0%ni, 75.8%id, 0.0%wa, 0.0%hi, 10.5%si, 0.0%st Mem: 2073128k total, 295836k used, 1777292k free, 4876k buffers Swap: 0k total, 0k used, 0k free, 215672k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1266 root 20 0 0 0 0 S 14 0.0 0:42.03 unraidd 1180 root 20 0 0 0 0 D 7 0.0 0:22.79 mdrecoveryd 10 root 20 0 0 0 0 S 0 0.0 0:00.97 kworker/0:1 1647 root 20 0 2448 980 756 R 0 0.0 0:00.05 top 1 root 20 0 828 280 240 S 0 0.0 0:02.75 init 2 root 20 0 0 0 0 S 0 0.0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0 0.0 0:00.03 ksoftirqd/0 5 root 20 0 0 0 0 S 0 0.0 0:00.01 kworker/u:0 6 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/0 7 root RT 0 0 0 0 S 0 0.0 0:00.00 migration/1 9 root 20 0 0 0 0 S 0 0.0 0:00.00 ksoftirqd/1 11 root 0 -20 0 0 0 S 0 0.0 0:00.00 khelper 145 root 20 0 0 0 0 S 0 0.0 0:00.01 sync_supers 147 root 20 0 0 0 0 S 0 0.0 0:00.00 bdi-default 149 root 0 -20 0 0 0 S 0 0.0 0:00.00 kblockd 296 root 0 -20 0 0 0 S 0 0.0 0:00.00 ata_sff 306 root 20 0 0 0 0 S 0 0.0 0:00.00 khubd 409 root 0 -20 0 0 0 S 0 0.0 0:00.00 rpciod 436 root 20 0 0 0 0 S 0 0.0 0:00.00 kswapd0 495 root 20 0 0 0 0 S 0 0.0 0:00.00 fsnotify_mark 514 root 0 -20 0 0 0 S 0 0.0 0:00.00 nfsiod 522 root 0 -20 0 0 0 S 0 0.0 0:00.00 crypto 612 root 0 -20 0 0 0 S 0 0.0 0:00.00 cnic_wq 670 root 20 0 0 0 0 S 0 0.0 0:00.20 kworker/1:2 701 root 16 -4 2372 992 496 S 0 0.0 0:00.08 udevd 783 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_0 830 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_1 831 root 20 0 0 0 0 S 0 0.0 0:00.00 kworker/u:2 832 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_2 833 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_3 850 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_4 851 root 20 0 0 0 0 S 0 0.0 0:00.00 usb-storage 895 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_5 898 root 20 0 0 0 0 S 0 0.0 0:00.00 scsi_eh_6 1001 root 20 0 1908 612 524 S 0 0.0 0:00.02 syslogd 1005 root 20 0 1856 384 320 S 0 0.0 0:00.01 klogd 1031 root 20 0 2044 408 308 S 0 0.0 0:00.00 dhcpcd 1113 bin 20 0 1960 496 404 S 0 0.0 0:00.00 rpc.portmap 1117 root 20 0 2108 796 660 S 0 0.0 0:00.00 rpc.statd 1127 root 20 0 1900 540 468 S 0 0.0 0:00.00 inetd 1134 root 20 0 10440 2880 2136 S 0 0.1 0:00.03 ntpd 1141 root 20 0 1864 636 536 S 0 0.0 0:00.00 acpid 1152 messageb 20 0 2476 360 208 S 0 0.0 0:00.00 dbus-daemon 1157 root 20 0 1908 584 504 S 0 0.0 0:00.00 crond 1159 daemon 20 0 1900 292 216 S 0 0.0 0:00.00 atd 1165 root 20 0 53820 1404 1072 S 0 0.1 0:00.25 emhttp 1166 root 20 0 1856 532 472 S 0 0.0 0:00.00 agetty

The machine has 2G of ram, if I remember right. It wouldn't have anything less than 1G I will try and see if i can do that once I get home tonight. Thanks.

the shares are also not avalable.

Also, FWIW, the server has been running exactly as expected for about a year and a half without much issue. Lately certain folders would be write protected, and when i would try to add or move things to these folders i am told i do not have permissions. This is when i moved from 4.7 to 5.0b10, and now I am having the issue with the server becoming unresponsive.

Hello Everyone. I have a relatively odd problem with my unraid server, and I haven't the first idea where to look to fix it. After the server first boots, I can access it just fine through the web gui, but after a few hours of sitting idle, or a few hours of me not polling it from the browser, i will be unable to connect to it through either samba or the browser. I am running 5.0 beta 10 Any idea where I should look to find the issue?

sounds good. Thanks for all your help! I figured if nothing else, this is a "test" of the biggest feature of Unraid.. single disk failure data recovery.

Thanks guys. I just finished a parity check just a few days ago, in anticipation of this swap. in regard to pre-clearing, I can surely understand the need to test the new drive, but so long as I don't touch the data on the old drive untill everything is done, will it write 0's to the remaining sector's of the new disk, to verify that it is working, just as a pre-clear would do?

Just thought I would confirm my assumptions before I do something dumb. I have an Unraid server running with 1 2.0t drive as the parity drive, 1 2.0t, 3 1.5, and 1 500g drive as data drives. I have another 2.0 coming in today. If I removed the 500g, and put the 2.0 in its place, the parity drive should rebuild the data on the new 2.0, and everything will be fine in the end, right? Should I pre-clear the new 2.0?

excelent, thank you.. I take it you paste " sed -i -e "s/host msdfs = Yes/host msdfs = No/" -e "s/msdfs root = Yes/msdfs root = No/" /etc/samba/smb.conf smbcontrol smbd reload-config " into the go files of both servers, restart both, and have a happy day? is this in any way detrimental to copying to/from a windows box as well? I need to know if I should be removing this line when I am done.

also, for what its worth, I can drag and drop from a windows box at about 10mbps... still seems slower than it should be though.. The destination server does not have a parity drive installed.

from the destination machine, named Tower: root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:17:31:74:71:87 inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18804369 errors:0 dropped:0 overruns:0 frame:0 TX packets:6200014 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1498815642 (1.3 GiB) TX bytes:510307262 (486.6 MiB) Interrupt:18 root@Tower:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: g Current message level: 0x00000037 (55) Link detected: yes From the source machine, named Server root@Server:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:30:48:dc:5d:34 inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1350026262 errors:25 dropped:707 overruns:0 frame:17 TX packets:221378361 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3873863433 (3.6 GiB) TX bytes:677681544 (646.2 MiB) Memory:e0d00000-e0d20000 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes

I started using the rsync method indicated in the post you linked Joe, but it was only transfering at a little over 1mbps... that seems oddly slow.. Both servers are connected to the same gigabit switch.. would the cp command go faster?