robinsj

Good point, I had never thought that it actually was a totally different part. Cause if it was the right part, it would be impossible to solder upside down. Well, glad I caught it before I had it loaded up with 10 3tb drives, as it surely would have fried them all, because of sending the wrong voltages back through the lines....

I am not sure if I am posting this in the right forum, but wanted to make sure people saw this. I purchased a Norco 4224 for a new build, with a supermicro motherboard. Hooked everything up, and tried powering it on, and the fan would spin for a couple of seconds and shut off, and a few seconds later would turn back on for a few seconds and shut off again, would continue until the power cord was pulled. Went through all the test procedures, just the motherboard and cpu hooked up, out of the case, on a piece of cardboard, same thing. Figured bad motherboard... Got the new motherboard, hooked just it up, out side the case, worked perfectly. So I figure I will take each step at a time, in turn, powering it on to make sure everything is powering on correctly. Put it back in the case, powers on. Start putting in SATA pci cards, still works. Now, I start hooking up the power to the backplane, get to the third one from the bottom, and boom, no dice. Same problem as before. So i pull everything back out, put the motherboard back on a piece of cardboard, and yep, same problem - motherboards fried. I start just going through every single thing, every nook and cranny to see what I can find - now mind you, I already had the power splitters hooked up to the backplanes before I hooked anything up. I couldn't believe what I found, one of the power plugs on the backplane was soldered in upside down. I was so dang mad! I was mad at Norco, mad at myself, that I didn't notice that one power plug went in upside down. Just mad.... Norco is sending me a new backplane, but now I am stuck waiting for another motherboard. Luckily I had no harddrives plugged in, as I am sure this would have fried them. I am thourghly confused as to why it was frying the motherboard, I would have thought it would fry the power supply. Maybe someone with some hardware knowledge could chime in here and tell me why this did this. I just posted so that everyone would know this, and not make the same mistake I made, and to double check the power plugs on the backplane to make sure they are orientated correctly! Hope I can help someone not make the same mistake! See Attached Picture!

Funny you posted this today, as I just searched for the exact same problem today.... I am having the exact same issues. I am not necessarily sure it is from the user share though, because some of my isos mount, and others don't. One of the ones that didn't, I tried copying off the server and then copying back, and it mounted. But then I realized it was on the cache drive, and wondered f that had something to do with it.... Any help out there?

Maybe someone can help me, not sure if you would need a log or not. I have installed sabnzbd through the unmenu pkg, but everytime I reset/restart my server, for some odd reason the config.ini gets reset, and I have to re-enter in all the settings.... Any suggestions?

Thats okay, I have unmenu up, I will try out your packages, those seem to be the only problems am having....

Okay, so I found where you can change them to run as root to run as nobody, but I can't get them to start when selecting run as nobody. It says there starting, but just hangs.... Never starts... Any ideas?

I had sabnzbd folder permissions set as 777, I will change it to 770. From what I can tell it looks like both sickbeard and sabnzbd are running as root, how do I make them run as nobody? Thanks for the help.

Not sure if anyone is reading these, would be nice to get a response. I found out now that sickbeard when it is processing and has to create a folder, I can't access that folder from anywhere, I have to login and change the permissions of that folder now... any ideas from anyone? I don't really want to have to manually go on and change the permission every time sickbeard creates a new directory. I didn't have to do this with 4.7... any help would be much appreciated....

I figured a little something else out. If my Windows 7 computer goes to sleep, and wakes up, I can't access the shares. I have to disable the network adapter on the computer and re-enable it and then I can access the share again?? Any ideas...

Seems I have done a bit of reading, and I guess when sabnzbd finished download the tv show, the permissions of that file were for root. So that is why I probably couldn't access that file? Doesn't explain why I can't access the network share anymore at all though. In addition, how do I make it so that when sabnzbd downloads anything, the permissions on the files it downloads anybody can access?

Maybe someone can help me out, as I really have no idea what I have done. So I upgraded from 4.7 and am running 5.0beta12a now. Everything went great, booted fine, ran the new permissions utlitity, got sabnzbd and sickbeard up and running. First TV show that downloaded, sabnzbd wouldn't run the script to automagically move it, I got that figured out figuring it was a permission setting on the script file, so I fixed that from reading another post on here. I don't know much about linux, but can fumble my way around. But then in the meantime I went to go and just rename the file myself from my windows 7 machine, and it wouldn't let me rename it,said access denied. Wouldn't let me copy it, or do anything. So I figured I would try just deleting the mapped drive, and reconnecting it. Well, it deleted it, but now it won't let me reconnect it at all. Says its a location thats unavailable. If I try to access it through network explorer, it just says Windows cannot access \\Tower\movies. I can still access the Webgui and everything. I honestly could care less about having absolute security, and having to specify user names and such. I just want to be able to access everything all the time. I liked that about 4.7, just setup it up and everyone has access. Can I not do that with 5.0? I had to upgrade to use my 3TB drives, so thats why I did.... Any help on this?

Well I think I got it fixed. It was appearing to lock up pretty much around 60-65% complete of the parity build. So I decided to try swapping my graphics card slot for one of the Supermicro SATA card slots, and it booted, finished the parity build, and has been up and running for over 24 hours now....

Nobody Any input on that log? Got another lockup through the night....

Well, unfortunately, locked up again. I think it made it to somewhere between 55-65% of the parity build. But I do have everything it posted in my terminal window for the lockup. Hopefully someone can help me decipher what is going on. Here it is - Tower login: root Password: Linux 2.6.32.9-unRAID. root@Tower:~# tail -f /var/log/syslog Feb 11 11:15:49 Tower ntpd[2437]: ntp_io: estimated max descriptors: 1024, initi al socket boundary: 16 Feb 11 11:15:49 Tower ntpd[2437]: Listening on interface #0 wildcard, 0.0.0.0#12 3 Disabled Feb 11 11:15:49 Tower ntpd[2437]: Listening on interface #1 lo, 127.0.0.1#123 En abled Feb 11 11:15:49 Tower ntpd[2437]: Listening on interface #2 eth0, 192.168.1.110# 123 Enabled Feb 11 11:15:49 Tower ntpd[2437]: kernel time sync status 0040 Feb 11 11:15:49 Tower ntpd[2437]: frequency initialized 155.777 PPM from /etc/nt p/drift Feb 11 11:15:49 Tower ifplugd(eth0)[1708]: Program executed successfully. Feb 11 11:15:58 Tower ntpd[2437]: synchronized to 69.164.222.108, stratum 2 Feb 11 11:21:10 Tower in.telnetd[2706]: connect from 192.168.1.11 (192.168.1.11) Feb 11 11:21:12 Tower login[2707]: ROOT LOGIN on `pts/0' from `192.168.1.11' Feb 11 19:27:39 Tower kernel: sas: command 0xc3604600, task 0xf6e763c0, timed ou t: BLK_EH_NOT_HANDLED Feb 11 19:27:39 Tower kernel: sas: Enter sas_scsi_recover_host Feb 11 19:27:39 Tower kernel: sas: trying to find task 0xf6e763c0 Feb 11 19:27:39 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf6e763c0 Feb 11 19:27:39 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abo rt_task:rc= 5 Feb 11 19:27:39 Tower kernel: sas: sas_scsi_find_task: querying task 0xf6e763c0 Feb 11 19:27:39 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_que ry_task:rc= 5 Feb 11 19:27:39 Tower kernel: sas: sas_scsi_find_task: task 0xf6e763c0 failed to abort Feb 11 19:27:39 Tower kernel: sas: task 0xf6e763c0 is not at LU: I_T recover Feb 11 19:27:39 Tower kernel: sas: I_T nexus reset for dev 0600000000000000 Feb 11 19:27:39 Tower kernel: sas: I_T 0600000000000000 recovered Feb 11 19:27:39 Tower kernel: sas: --- Exit sas_scsi_recover_host Feb 11 19:28:09 Tower kernel: sas: command 0xc3604600, task 0xf6e54000, timed ou t: BLK_EH_NOT_HANDLED Feb 11 19:28:09 Tower kernel: sas: Enter sas_scsi_recover_host Feb 11 19:28:09 Tower kernel: sas: trying to find task 0xf6e54000 Feb 11 19:28:09 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf6e54000 Feb 11 19:28:09 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abo rt_task:rc= 5 Feb 11 19:28:09 Tower kernel: sas: sas_scsi_find_task: querying task 0xf6e54000 Feb 11 19:28:09 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_que ry_task:rc= 5 Feb 11 19:28:09 Tower kernel: sas: sas_scsi_find_task: task 0xf6e54000 failed to abort Feb 11 19:28:09 Tower kernel: sas: task 0xf6e54000 is not at LU: I_T recover Feb 11 19:28:09 Tower kernel: sas: I_T nexus reset for dev 0600000000000000 Feb 11 19:28:09 Tower kernel: sas: I_T 0600000000000000 recovered Feb 11 19:28:09 Tower kernel: sas: --- Exit sas_scsi_recover_host Feb 11 19:28:40 Tower kernel: sas: command 0xc3604600, task 0xf6e54000, timed ou t: BLK_EH_NOT_HANDLED Feb 11 19:28:40 Tower kernel: sas: Enter sas_scsi_recover_host Feb 11 19:28:40 Tower kernel: sas: trying to find task 0xf6e54000 Feb 11 19:28:40 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf6e54000 Feb 11 19:28:40 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1701:mvs_abo rt_task:rc= 5 Feb 11 19:28:40 Tower kernel: sas: sas_scsi_find_task: querying task 0xf6e54000 Feb 11 19:28:40 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 1645:mvs_que ry_task:rc= 5 Feb 11 19:28:40 Tower kernel: sas: sas_scsi_find_task: task 0xf6e54000 failed to abort Feb 11 19:28:40 Tower kernel: sas: task 0xf6e54000 is not at LU: I_T recover Feb 11 19:28:40 Tower kernel: sas: I_T nexus reset for dev 0600000000000000 Feb 11 19:28:40 Tower kernel: sas: I_T 0600000000000000 recovered Feb 11 19:28:40 Tower kernel: sas: --- Exit sas_scsi_recover_host Message from syslogd@Tower at Fri Feb 11 19:28:44 2011 ... Tower kernel: Oops: 0000 [#1] SMP Message from syslogd@Tower at Fri Feb 11 19:28:44 2011 ... Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host3/target 3:0:0/3:0:0:0/block/sdl/stat Message from syslogd@Tower at Fri Feb 11 19:28:44 2011 ... Tower kernel: Stack: Message from syslogd@Tower at Fri Feb 11 19:28:44 2011 ... Tower kernel: Process swapper (pid: 0, ti=f7498000 task=f7471ef0 task.ti=f749800 0) Message from syslogd@Tower at Fri Feb 11 19:28:44 2011 ... Tower kernel: Call Trace:

Just reread your post bcbgboy13, and must not have read between the lines the first time about the Marvell Network. Does Marvell not work very well? I have since disabled 3 of the lan controllers and so just the one is running, but if there is a better card that is out that I can throw in there I would do it...

Thanks for the Response. I have the Asus PQ5 Premium Board - which is Intel Chipset. Its not on the hardware list, but it was the motherboard I had at the time. Which it has worked great for me so far. Probably been running for a year with no problems. Seems these problems kicked in when i added that 2nd supermicro card. I know I had disabled all the extra stuff in the bios, but must have missed the 4 lan ports, so I will get the extra 3 disabled. I will also check into the bios to see if it needs an update. I am running a telnet session on my pc, with the tail -f /var/log/syslog so I can see what happens if it locks up again... Also, I am pretty sure it isn't a power supply issue, as I am using a Seasonic SS-650KM, which has 54A on the 12V, which should be plenty.

Thanks for the response Joe. Just noticed it locked up again through the night. Any other recommendations? On a side note, when the computer is booting up, when it is at the Bios Screen for the Supermicro cards where it spins up the drives, after it has spun up the drives, it sits at that screen for at least 10 minutes before moving on. Before I added the second card, once the drives were spun up, it moved along right away? Think that could be related?

Okay, so I have been using unraid for awhile now, and not had any issues. I just added another supermicro AOC-SAT2-MV8, so now I have 2. At the same time I did that, I changed out my 1.5tb parity drive for a 2tb parity drive, and added the old parity drive to the array. Everything was going well, it was rebuilding the parity data, then tonight it just locked up. I couldn't pull up the webpage, I couldn't telnet into it, a ping was even non-responsive. I had no monitor hooked up to it, so couldn't see anything on screen. I hooked up a monitor to it, but nothing come on, which would happen if it was completely locked up. So I had to do a Hard reset. I have left the monitor hooked up, just in case it locks up again and I can see what is happening. In the mean time it has booted back up, and has restarted building the parity drive. I took a look at the system log and looks like there is some errors as posted below. I am running unraid 4.7. I have attached the whole system log to the post also. Any help is very very much appreciated. I have no idea what they mean.... Feb 10 23:47:11 Tower kernel: ------------[ cut here ]------------ Feb 10 23:47:11 Tower kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() (Minor Issues) Feb 10 23:47:11 Tower kernel: Hardware name: P5Q Premium Feb 10 23:47:11 Tower kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered (Drive related) Feb 10 23:47:11 Tower kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas (Drive related) Feb 10 23:47:11 Tower kernel: Pid: 890, comm: modprobe Not tainted 2.6.32.9-unRAID #8 (Errors) Feb 10 23:47:11 Tower kernel: Call Trace: (Errors) Feb 10 23:47:11 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Feb 10 23:47:11 Tower kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 (Errors) Feb 10 23:47:11 Tower kernel: [<c109cf0e>] proc_register+0x11c/0x14b (Errors) Feb 10 23:47:11 Tower kernel: [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 (Errors) Feb 10 23:47:11 Tower kernel: [<c109d0ef>] proc_mkdir+0xf/0x11 (Errors) Feb 10 23:47:11 Tower kernel: [<f83e7a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] (Routine) Feb 10 23:47:11 Tower kernel: [<f83ceca9>] __scst_register_target_template+0x16c/0x3af [scst] (Routine) Feb 10 23:47:11 Tower kernel: [<f844cd5d>] mvst_init+0x3b/0x5b [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<f8451895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb (Errors) Feb 10 23:47:11 Tower kernel: [<c1142050>] local_pci_probe+0xe/0x10 (Errors) Feb 10 23:47:11 Tower kernel: [<c11426ad>] pci_device_probe+0x48/0x66 (Errors) Feb 10 23:47:11 Tower kernel: [<c1194956>] driver_probe_device+0x79/0xed (Errors) Feb 10 23:47:11 Tower kernel: [<c1194a0d>] __driver_attach+0x43/0x5f (Errors) Feb 10 23:47:11 Tower kernel: [<c11940a7>] bus_for_each_dev+0x39/0x5a (Errors) Feb 10 23:47:11 Tower kernel: [<f8459000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<c119482f>] driver_attach+0x14/0x16 (Errors) Feb 10 23:47:11 Tower kernel: [<c11949ca>] ? __driver_attach+0x0/0x5f (Errors) Feb 10 23:47:11 Tower kernel: [<c119451c>] bus_add_driver+0x9f/0x1c5 (Errors) Feb 10 23:47:11 Tower kernel: [<f8459000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<c1194ccf>] driver_register+0x7b/0xd7 (Errors) Feb 10 23:47:11 Tower kernel: [<f8459000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<c1142882>] __pci_register_driver+0x39/0x8c (Errors) Feb 10 23:47:11 Tower kernel: [<f8459000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<f8459030>] mvs_init+0x30/0x45 [mvsas] (Errors) Feb 10 23:47:11 Tower kernel: [<c1001139>] do_one_initcall+0x4c/0x131 (Errors) Feb 10 23:47:11 Tower kernel: [<c1042e6e>] sys_init_module+0xa7/0x1dd (Errors) Feb 10 23:47:11 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Feb 10 23:47:11 Tower kernel: ---[ end trace 9b764bc3b4e92c4f ]--- syslog.txt

Nope... they have spaces in them... thats it. This is one: Dec 31 12:08:06 Tower shfs: duplicate object: /mnt/disk8/Movies/TV Shows/Two and a Half Men/season04.tbn Hmm... Looking closer at the syslog, I think the spaces are the problems, these were further down: Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access /mnt/*/*Movies/TV: No such file or directory Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access Shows/Two: No such file or directory Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access and: No such file or directory Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access a: No such file or directory Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access Half: No such file or directory Dec 31 12:22:35 Tower unmenu[5041]: ls: cannot access Men/season04.tbn*: No such file or directory

I think this is where I should post this. I am trying to use the Dupe Files, but it doesn't seem to do anything. I know there are Dupe Files because it shows them in the Syslog on the main unmenu page. Another problem too when i actually click the SysLog link all I get is a e 0 at the top. When I click the dupe files button it takes about 2 seconds and then shows Duplicate Files on Disk Shares and File with nothing else. Any help? EDIT: Nevermind about syslog, just needed to restart unmenu. Still same problem with dupe files though...

The one in unmenu, bmw-ng...

The bandwidth monitor is pretty cool. I am wondering, does it do any sort of logging? Or is there an application that I can run on my windows computer to get the data from it? I am interested in Statistics on usage over time, you know transfer rates/totals for the last 24 hours/7 days/month so on and so forth.... IF this is not what this tool is for is there such a tool?

I am running 0.5.3, but haven't tried using .gz files from bin-req... If anybody has an ipad, go and get the NZBpad app, works awesome with sabnzbd on your server...

I got it working, thanks for the response....

Don't put it on its side, then all the data will fall off the harddrives....