jaj08

It seems that after a reboot I can no longer access Crashplan via the GUI to configure/monitor the status of what is going on. Has anyone else ran into this? It is real annoying, but I know the Crashplan server is functioning as my clients are backing up to it without issue. When I first noticed this problem it was early on. So I deleted my Crashplan docker and all configs for it. Sure enough rebooted and my Windows GUI once again would not communicate with it. So then I got Crashplan installed configured, and I let it run for about 3 weeks no issues, GUI remained responsive, and all seemed well. Then Unraid released the new beta so I prepared for another Reboot which I knew would kill it. Sure enough, unraid is updated, docker is running and accepting incoming backups, but my GUI client is still not able to connect to the server. On the Windows client side I have uninstalled and deleted all configs for Crashplan before installing again but it still never establishes its connection. I double checked the ui.properties file on my Windows PC and it remains configured with my unraid IP address. GUI Client continues to say it can't connect to the backup engine. I can't say this for sure as it has been a few weeks, but I'm fairly sure that when I specify reboot it, that means rebooting either unraid or my Windows PC would cause the client to never connect again. So it basically seems that I can only initialize the GUI client one time and it remains functional until its forced to reconnect at a later time.

Simplefeatures now installed properly on both my unraid servers after making the changes to sqlite-3.7.17-i486-1.txz Thanks for the help.

I am attempting a fresh install of Simplefeatures on 5.0 Final and I get the following error in my web gui. Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /usr/local/emhttp/plugins/webGui/template.php on line 41 Thu Aug 29 19:38:05 2013 CDT I did some research, found some suggestions for a fix at http://lime-technology.com/forum/index.php?topic=19508.msg232982#msg232982 But still getting that error, I then noticed when I manually tried to reinstall the plugin it is complaining of being unable to download SQLlite. I tried copy the original plugin file as well and still get the same error. ile /boot/packages/sqlite-3.7.14.1-i486-1.txz: downloading from http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.14.1-i486-1.txz ... http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/ap/sqlite-3.7.14.1-i486-1.txz: 2013-09-03 14:39:13 ERROR 404: Not Found. Does the installer need to be updated with some new file locations?

I just had a screen capture that looked very similar to this after initiating a stop from the gui. I do have Simplefeatures installed and so far on reboot all is good and I did force a stop at least once more now without issue.

When you upgraded did you only copy over bzimage and bzroot from the zip file, or did you copy over other files as well (like menu.c32). I can say I am 100% sure I only copied those 2 files on my work Unraid system as I upgraded my personal first, and after having issues I saw comments of ensuring you only copy those 2 files. On my personal Unraid system I can't say for sure that it was only those 2 as I dragged and dropped the files without giving much thought.

I just wanted to post that on both my work and personal Unraid systems they both hung up on reboot after upgrading to RC9 on home and rc10 at work. I ran make bootable and it started up no problem. Its an easy enough fix, but annoying that so far 2 of my 3 unraid systems have required that I run the make bootable again. My last unraid system is still running 4.7 so I probably won't touch it until after 5 goes final. It sounds like your problem/fix may have been slightly different but I thought it was worth sharing my troubles.

I just wanted to put my vote into the mix that we need to hault any new features and work on making 5.0 stable and release it. Let anything new go in 5.1 I prefer a release be listed as final/stable as otherwise at the first symptom of problems someone in the forums will make the suggestion that you need to upgrade/downgrade to get something to work as expected, or a certain plugin only works on these betas and not those... I just want something stable that supports 3tb+ drives. If your going to continue to add new features to 5 then backport 3tb support to the 4.7 releases.

Anyone have any idea why my mnt/user Totals is not working? Hasn't worked for awhile on my office server. I have deleted the mnt/user, moved it to the end of the device list just for grins.. All the same, I get individual stats for everything except the Total. I am wondering if it is a size restriction or something. My server currently has 14 drives, most of which are 2tb. I know it worked at one point but I don't remember when it stopped reporting totals. My install was done through unmenu

Yeah I was aware that it didn't break anything, but at same time I figured if I could confirm one way or the other I could format it the way the HDD manufacturer expects.

Since this is one of Hitachi's newest drives I assumed it would be Advanced Format, but I don't see anything to backup this assumption. Is there a clear way of knowing? Do all manufacturers print a warning on the drive as Samsung and Seagate seem to do? I am just trying to confirm how I should preclear this drive, from what I can tell the drive appears to NOT be an advanced format drive.

Normally I would fully believe that, but the one major thing I find frustrating is that the firmware version doesn't change when you apply the patch. So your left assuming that all went well with the upgrade with no way to verify. With that said I still trust the drives, which is why I have 2 of them, but with the lack of verifying that the firmware has updated I personally would never want this drive as a parity drive.

I have 2 drives in use as well but the thing to keep in mind is that the firmware bug has a very specific cause. Your not going to know if your drive is taking errors until you do a parity check. From what I understand is if you don't use any addons, specifically Unmenu, then the cause of the bug should never occur. Its not a fault in unmenu either, its the fault of the hard drive not liking to be accessed by certain utilities during data copies. If you do use unmenu, like myself, then I plan to avoid ever accessing it when data is being copied to the system. Even with the firmware upgrade, and my planning to not use Unmenu during data copies, I personally would still never trust one of these drives as my Parity drive.

So I have Unraid 4.7b1 running on both my Office and Home Unraid servers with each server having 1 AF drive in the array. For testing purposes I filled up the new AF drive and all is seeming well. No stability issues with Unraid, and no write issues to the AF drive... So in my testing this build seems solid.

So I added my first Advanced Format drive to the array. Its an EARS drive that I had previously forgotten to jumper.

Just to confirm I understand things. Changing the default setting to 4k is irrelevant for my setup because i use preclear script %100 of the time correct? So no matter what, it would be up to me to remember to use the correct settings when clearing. I currently have a drive clearing with the advanced format option in both my home and office 4.7 servers.

So I now have this beta running on both my home and office Unraid servers. No problems so far. I am using the preclear script now on an advanced format drive at home so I will try adding a new drive sometime over the weekend depending on how long the clear takes.

Ok Sounds good just wanted to check.

When I try to format a drive with the -A option, the confirmation screen still seems to show its going to do format on 63. Is this screen wrong? or it not accepting the -A properly? Pre-Clear unRAID Disk ######################################################################## Device Model: WDC WD10EARS-00MVWB0 Serial Number: WD-WCAZA0168148 Firmware Version: 50.0AB50 User Capacity: 1,000,204,886,016 bytes Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 1 heads, 63 sectors/track, 31008336 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 63 1953525167 976762552+ 83 Linux Partition 1 does not end on cylinder boundary. ######################################################################## Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'):

Upgraded home unraid to 4.7beta1 Appears I have a couple EARS drives too that I probably never paid attention to.... Suppose I will give it a few before I go through the rebuild process to format those correctly.

Yeah a poll makes since, I think tomorrow I will update my home system with this, but will hold off on the office unit for a bit longer.

Got my 2 drives updated today. Took a couple workstations to find one with a SATA controller that the Samsung utility liked. Now to just hope this really fixes the problem. For grins I am going to remove all data off the one active Samsung drive I had, and will cross my fingers that 4.7 goes final soon so that I can have these format properly.

So I am tempted to run this build in a production environment for the Advanced Format support. As I have 2 drives that are going through the break in process that support advanced formatting so if I upgrade I can prevent any hard drives in Unraid having the wrong formatting. Any ideas when this goes final? Normally I have patience, but I have been filling drives just as fast I have been adding them so delaying the install of these 2 drives is not optimal. Just wondering what the usual time frame is from Beta to final, especially since so much work is going on with 5.0 these days.

Fixed, I also was going by the Wiki that said 4.6.1 supported advanced formatting, I assumed that was a final build but looks like 4.7beta would be my only choice. So I guess I may hold off on the advanced formatting anyway as don't really think I want to run a beta.

Blah wouldn't you know it, I have 1 of these drives in use, and another drive going through my 'break in' process. Taking array offline and I think my plan will be to move all the data off manually, remove from array and allow Unraid to rebuild the array without the drive. I will then Update Unraid to 4.6.1, Update the Samsung Firmware, and use Preclear_disk.sh with the -A advanced format option before adding the drive back into the array. Does the above procedure make since? I didn't bother with the advanced formatting before as it was my understanding it just caused a performance hit. But If I am starting from scratch with this drive I thought it made since to get all the above done.

Weird, wonder how this one disk got setup differently from all the others.