PashaK

What other plugins are you using and which version of unraid? Have you tried a reboot of the system and also if you are running unmenu do you have g++ and GCC installed? Using Influencers Logitech media server, Sabnzbd, headphones and sickbeard. Have had unmenu in the past but its disabled. My linux knowledge isnt great so dont know what else will help you to help me It's probably a dependency installing that's breaking the webgui. You can switch your plugins over to use mine for sab headphones and sickbeard. I would delete everything in your packages folder and then reboot so it's a clean install on reboot. All the required packages will redownload. That's a good place to start. I've deleted all items in packages folder. switched plugins for Sab and SB to yours, and removed all other plugins like LMS and Headphones, then rebooted. Still the same. I also tried your Maraschino Plugin and i get "maraschino.pid not created for some reason" I keep my Plugin Install folder at /boot/pluginInstall/xxxxxxxx and Plugin Data folder at /boot/PluginData/xxxxxxxx I know this reduces the lifetime of the flash but its only until I get myself a cache drive I also updated my powerdown addon from 1.02 to 2.06. I dont think i can start anymore fresh. Not sure where else to go from here. Unraid version recently updated to 5.0.5 Stable. So i fixed CP, changed Config Dir to a disk, instead of Boot. Also fixed Maraschino this way by changing install and config dir to disk, not boot. thanks for all your help

What other plugins are you using and which version of unraid? Have you tried a reboot of the system and also if you are running unmenu do you have g++ and GCC installed? Using Influencers Logitech media server, Sabnzbd, headphones and sickbeard. Have had unmenu in the past but its disabled. My linux knowledge isnt great so dont know what else will help you to help me It's probably a dependency installing that's breaking the webgui. You can switch your plugins over to use mine for sab headphones and sickbeard. I would delete everything in your packages folder and then reboot so it's a clean install on reboot. All the required packages will redownload. That's a good place to start. I've deleted all items in packages folder. switched plugins for Sab and SB to yours, and removed all other plugins like LMS and Headphones, then rebooted. Still the same. I also tried your Maraschino Plugin and i get "maraschino.pid not created for some reason" I keep my Plugin Install folder at /boot/pluginInstall/xxxxxxxx and Plugin Data folder at /boot/PluginData/xxxxxxxx I know this reduces the lifetime of the flash but its only until I get myself a cache drive I also updated my powerdown addon from 1.02 to 2.06. I dont think i can start anymore fresh. Not sure where else to go from here. Unraid version recently updated to 5.0.5 Stable.

What other plugins are you using and which version of unraid? Have you tried a reboot of the system and also if you are running unmenu do you have g++ and GCC installed? Using Influencers Logitech media server, Sabnzbd, headphones and sickbeard. Have had unmenu in the past but its disabled. My linux knowledge isnt great so dont know what else will help you to help me It's probably a dependency installing that's breaking the webgui. You can switch your plugins over to use mine for sab headphones and sickbeard. I would delete everything in your packages folder and then reboot so it's a clean install on reboot. All the required packages will redownload. That's a good place to start. OK thanks. Will give that go. Cheers

What other plugins are you using and which version of unraid? Have you tried a reboot of the system and also if you are running unmenu do you have g++ and GCC installed? Using Influencers Logitech media server, Sabnzbd, headphones and sickbeard. Have had unmenu in the past but its disabled. My linux knowledge isnt great so dont know what else will help you to help me

Hi guys, Just tried the plugins for Sab, Sick beard and CP. All working well except for CP. I did have a previous version installed, but its been playing up recently and wasnt starting, so decided to start fresh. I used different Install and config paths to the previous installs. The CP service starts however the page appears flat with no formatting. As Attached: Any thoughts on where I can start troubleshooting? thanks in advance

Yeah everythings normal. I just added more time as im redoing parity. no big deal. should be done in 5 hrs. all good practice

Damn it, i just went back and re-read the upgrade notes. i was reading from the beta section, not rc section. so you're right, i didnt need to delete the super.dat file. Once this parity sync finishes, i will copy over syslinux.cfg and reboot server. then run the utils/new permissions utility as it probably needs that too. Hope it doesnt mess with any plugins or shares thanks again

Thanks mejutty. I was only looking in rc4 section. As for the other issue, I contacted a friend who recently upgraded and was told to assign drives as they were so i did that. All is good. parity rebuilding. hope this helps someone else

Well i contacted a friend who recently upgraded and was told to assign drives as they were so i did that. All is good. parity rebuilding. hope this helps someone else

Hi guys, got a bit of an issue. Im not great with Linux and been a while since upgrading beta versions but need to put some bigger drives in. Anyway, I was previously on RC4, everything working smoothly. As directed by release notes, i copied over bzroot and bzimage, as well as : "Delete the file config/super.dat. You will need to re-assign all your hard drives." theres isnt a mention of syslinux.cfg to copy over, but in a previous thread, it was mentioned to do so, i havent yet, wanted to confirm. Anyway, on boot up, all my drives are unassigned, which is fine, thats what the step above says it would do, but the next line in the release notes says: "you should see "Stopped. Configuration valid." array status with all disks assigned correctly". so im a bit confused. I did take a screenshot of where each disk is assigned in which slot, but should i do so? i tried assigning parity drive, and was a blue ball. That good? What should i expect after all drives assigned correctly and array started? thanks in advance

Noticed this thread might not be so active, so will repost in general support. Thanks

Hi guys, got a bit of an issue. Im not great with Linux and been a while since upgrading beta versions but need to put some bigger drives in. Anyway, I was previously on RC4, everything working smoothly. As directed by release notes, i copied over bzroot and bzimage, as well as : "Delete the file config/super.dat. You will need to re-assign all your hard drives." theres isnt a mention of syslinux.cfg to copy over, but in a previous thread, it was mentioned to do so, i havent yet, wanted to confirm. Anyway, on boot up, all my drives are unassigned, which is fine, thats what the step above says it would do, but the next line in the release notes says: "you should see "Stopped. Configuration valid." array status with all disks assigned correctly" so im a bit confused. I did take a screenshot of where each disk is assigned in which slot, but should i do so? i tried assigning parity drive, and was a blue ball. That good? What should i expect after all drives assigned correctly and array started? thanks in advance

Looks like evrything is back to normal after a reboot. all shares are visible and accessible and all data looks intact. thanks very much for the tips.

ok will do. i havent done that yet because parity sync was still going when i left for work. will give it a shot in a few hours. then will mark this as solved if all goes well. thanks

Well the actual folders on each of the disks is still there, and all the data present. but yes all the shares that are missing in the shares view has data in it. I alos noticed one of the shares that is still available is nt actually showing data from all the disks. if i recreate the shares in the shares tab as they were will they detect the folders on the disks already and keep the data or will it wipe them and create them new?

I decided to start the parity sync, and it appears all my data is intact. However, I am missing some shares in the shares tab. 2 still appear but the other 8 or so are missing. Should I just add them as they used to be or should I recover them another way?

Also, using unraid 4.7. syslog as captured from unmenu: thanks System Log Nov 3 18:38:57 Tower kernel: sd 4:0:0:0: [sdk] Mode Sense: 03 00 00 00 Nov 3 18:38:57 Tower kernel: sd 4:0:0:0: [sdk] Assuming drive cache: write through Nov 3 18:38:57 Tower kernel: usb-storage: device scan complete Nov 3 18:38:57 Tower kernel: sd 4:0:0:0: [sdk] Assuming drive cache: write through Nov 3 18:38:57 Tower kernel: sdk: sdk1 Nov 3 18:38:57 Tower kernel: sd 4:0:0:0: [sdk] Assuming drive cache: write through Nov 3 18:38:57 Tower kernel: sd 4:0:0:0: [sdk] Attached SCSI removable disk Nov 3 18:38:57 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Nov 3 18:38:57 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Nov 3 18:38:57 Tower ifplugd(eth0)[1503]: ifplugd 0.28 initializing. Nov 3 18:38:57 Tower ifplugd(eth0)[1503]: Using interface eth0/00:16:E6:DB:C9:6C with driver (version: 1.25) Nov 3 18:38:57 Tower ifplugd(eth0)[1503]: Using detection mode: SIOCETHTOOL Nov 3 18:38:57 Tower ifplugd(eth0)[1503]: Initialization complete, link beat not detected. Nov 3 18:38:57 Tower kernel: sky2 eth0: enabling interface Nov 3 18:38:57 Tower rpc.statd[1515]: Version 1.1.4 Starting Nov 3 18:38:57 Tower emhttp: unRAID System Management Utility version 4.7 Nov 3 18:38:57 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC Nov 3 18:38:57 Tower emhttp: Pro key detected, GUID: 058F-6387-0000-0000ZL7DSXKZ Nov 3 18:38:57 Tower emhttp: shcmd (1): udevadm settle Nov 3 18:38:57 Tower emhttp: Device inventory: Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host7 (sde) ST31500341AS_9VS17097 Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host7 (sdf) ST31000528AS_9VP4W3W9 Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host8 (sdg) ST31500341AS_9VS3MH5Z Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:1:0 host8 (sdh) ST31500341AS_9VS3QFDJ Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.5-scsi-0:0:0:0 host9 (sdi) ST31500341AS_9VS15FEZ Nov 3 18:38:57 Tower emhttp: pci-0000:00:1f.5-scsi-1:0:0:0 host10 (sdj) ST2000DL003-9VT166_5YD38H9W Nov 3 18:38:57 Tower emhttp: pci-0000:02:00.0-scsi-0:0:0:0 host0 (sda) ST31000528AS_9VP4V67D Nov 3 18:38:57 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 host1 (sdb) ST31500341AS_9VS1450Q Nov 3 18:38:57 Tower emhttp: pci-0000:04:00.0-scsi-0:0:0:0 host5 (sdc) ST31000340AS_5QJ0QD84 Nov 3 18:38:57 Tower emhttp: pci-0000:04:00.0-scsi-1:0:0:0 host6 (sdd) ST31000340AS_9QJ1CQ2W Nov 3 18:38:57 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger Nov 3 18:38:57 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,144,8,64,8,96,8,0,8,112,8,128,8,32,8,48,8,16,8,80,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Nov 3 18:38:57 Tower kernel: xor: automatically using best checksumming function: pIII_sse Nov 3 18:38:57 Tower kernel: pIII_sse : 7883.200 MB/sec Nov 3 18:38:57 Tower kernel: xor: using function: pIII_sse (7883.200 MB/sec) Nov 3 18:38:57 Tower kernel: md: unRAID driver 1.1.1 installed Nov 3 18:38:57 Tower kernel: md: import disk0: [8,144] (sdj) ST2000DL003-9VT1 5YD38H9W size: 1953514552 Nov 3 18:38:57 Tower kernel: md: disk0 replaced Nov 3 18:38:57 Tower kernel: md: import disk1: [8,64] (sde) ST31500341AS 9VS17097 size: 1465138552 Nov 3 18:38:57 Tower kernel: md: import disk2: [8,96] (sdg) ST31500341AS 9VS3MH5Z size: 1465138552 Nov 3 18:38:57 Tower kernel: md: import disk3: [8,0] (sda) ST31000528AS 9VP4V67D size: 976762552 Nov 3 18:38:57 Tower kernel: md: import disk4: [8,112] (sdh) ST31500341AS 9VS3QFDJ size: 1465138552 Nov 3 18:38:57 Tower kernel: md: import disk5: [8,128] (sdi) ST31500341AS 9VS15FEZ size: 1465138552 Nov 3 18:38:57 Tower kernel: md: import disk6: [8,32] (sdc) ST31000340AS 5QJ0QD84 size: 976762552 Nov 3 18:38:57 Tower kernel: md: import disk7: [8,48] (sdd) ST31000340AS 9QJ1CQ2W size: 976762552 Nov 3 18:38:57 Tower kernel: md: import disk8: [8,16] (sdb) ST31500341AS 9VS1450Q size: 1465138552 Nov 3 18:38:57 Tower kernel: md: import disk9: [8,80] (sdf) ST31000528AS 9VP4W3W9 size: 976762552 Nov 3 18:38:57 Tower kernel: mdcmd (1): set md_num_stripes 1280 Nov 3 18:38:57 Tower kernel: mdcmd (2): set md_write_limit 768 Nov 3 18:38:57 Tower kernel: mdcmd (3): set md_sync_window 288 Nov 3 18:38:57 Tower kernel: mdcmd (4): set spinup_group 0 8 Nov 3 18:38:57 Tower kernel: mdcmd (5): set spinup_group 1 256 Nov 3 18:38:57 Tower kernel: mdcmd (6): set spinup_group 2 0 Nov 3 18:38:57 Tower kernel: mdcmd (7): set spinup_group 3 1 Nov 3 18:38:57 Tower kernel: mdcmd (: set spinup_group 4 0 Nov 3 18:38:57 Tower kernel: mdcmd (9): set spinup_group 5 0 Nov 3 18:38:57 Tower kernel: mdcmd (10): set spinup_group 6 0 Nov 3 18:38:57 Tower kernel: mdcmd (11): set spinup_group 7 512 Nov 3 18:38:57 Tower kernel: mdcmd (12): set spinup_group 8 2 Nov 3 18:38:57 Tower kernel: mdcmd (13): set spinup_group 9 128 Nov 3 18:38:57 Tower emhttp: Spinning up all drives... Nov 3 18:38:57 Tower kernel: mdcmd (14): spinup 0 Nov 3 18:38:57 Tower kernel: mdcmd (15): spinup 1 Nov 3 18:38:57 Tower kernel: mdcmd (16): spinup 2 Nov 3 18:38:57 Tower kernel: mdcmd (17): spinup 3 Nov 3 18:38:57 Tower kernel: mdcmd (18): spinup 4 Nov 3 18:38:57 Tower kernel: mdcmd (19): spinup 5 Nov 3 18:38:57 Tower kernel: mdcmd (20): spinup 6 Nov 3 18:38:57 Tower kernel: mdcmd (21): spinup 7 Nov 3 18:38:57 Tower kernel: mdcmd (22): spinup 8 Nov 3 18:38:57 Tower kernel: mdcmd (23): spinup 9 Nov 3 18:38:57 Tower emhttp: stale configuration Nov 3 18:38:57 Tower emhttp: shcmd (4): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Nov 3 18:38:57 Tower emhttp: _shcmd: shcmd (4): exit status: 1 Nov 3 18:38:57 Tower emhttp: shcmd (5): cp /etc/exports- /etc/exports Nov 3 18:38:57 Tower emhttp: shcmd (6): killall -HUP smbd Nov 3 18:38:57 Tower emhttp: shcmd (7): /etc/rc.d/rc.nfsd restart | logger Nov 3 18:38:58 Tower emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 3 18:38:58 Tower emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 3 18:38:58 Tower emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Nov 3 18:38:58 Tower emhttp: shcmd (10): crontab /var/spool/cron/crontabs/root Nov 3 18:38:59 Tower kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both Nov 3 18:39:00 Tower ifplugd(eth0)[1503]: Link beat detected. Nov 3 18:39:01 Tower ifplugd(eth0)[1503]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Nov 3 18:39:01 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:16:E6:DB:C9:6C Nov 3 18:39:01 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.20.105 broadcast 192.168.20.255 netmask 255.255.255.0 Nov 3 18:39:01 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.20.2 metric 1 Nov 3 18:39:01 Tower ntpd[1798]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1) Nov 3 18:39:01 Tower ifplugd(eth0)[1503]: client: Starting NTP daemon: /usr/sbin/ntpd -g Nov 3 18:39:01 Tower ntpd[1799]: precision = 1.000 usec Nov 3 18:39:01 Tower ntpd[1799]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Nov 3 18:39:01 Tower ntpd[1799]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Nov 3 18:39:01 Tower ntpd[1799]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Nov 3 18:39:01 Tower ntpd[1799]: Listening on interface #2 eth0, 192.168.20.105#123 Enabled Nov 3 18:39:01 Tower ntpd[1799]: kernel time sync status 0040 Nov 3 18:39:01 Tower ntpd[1799]: frequency initialized -84.551 PPM from /etc/ntp/drift Nov 3 18:39:01 Tower ifplugd(eth0)[1503]: Program executed successfully.

Hi Guys, Hoping someone can provide me with some advice. I'm no unraid or linux expert so would appreciate it. Earlier today there was an unexpected power outage. The server was in the middle of copying data from my unraid to another when the power went out. I turned the server back on and saw that the array had started but the parity drive was showing red and 494 errors were displayed. I proceeded to stop the array so I can take a better look but drives wouldnt unmount probably because files were open due to sabnzbd so used scripted shutdown (ctrl alt delete) to turn the server off. I then turned it back on and now the parity drive is showing Blue and telling me a new parity disk is installed. Pressing Start will bring the array on-line and start Parity-Sync. Im not sure what to do from here. Should I proceed by checking the box and doing a parity sync and all my existing data will sync back to parity or is there some others steps i should take? Any help is appreciated