jumperalex Posted February 13, 2014 Share Posted February 13, 2014 So here I sit with Snowmagedon II coming my way in the DC area and I'm wondering ... What are the chances I'll have 6.0 Beta 4 to play with in my weather enforced sequestration? As good as the odds I might not have power with which to power my unraid? Nice try ;D I bet it is available 10 minutes after the power goes out... Since I am north of Baltimore... Well its 9:02 and I still have power. So beta 4 release is on hold until the sleet freezes and takes down a powerline. Not being in MD and beholden to PEPCO at least I can count on getting my power back before spring >;-) Quote Link to comment
dlandon Posted February 13, 2014 Share Posted February 13, 2014 Tom, I have found a hang up when shutting down unRAID for a reboot. I have unRAID with Xen running and no plugins installed. I have installed Ironicbadger's ArchVM and it is running. It has some unRAID samba shares mounted and I have the Logitech Media Server running in the VM. If I run a "shutdown -r now" command without shutting down the Arch VM, the system hangs after switching to runlevel 6. The syslog before initiating a shutdown is attached. The attached picture is what the console shows when shutting down and where it hangs. If I shutdown the VM first, everything proceeds as normal. Let me know if you need any further information. syslog.txt Quote Link to comment
peter_sm Posted February 13, 2014 Share Posted February 13, 2014 @Tom Can you look into a issue I see ? its something with timezone and php?? It was no issue on V5, and I have tried several different timezone settings, and rebooted between. I see this when starting the only plugin I use, and also when execute Smart History in unMenu Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /usr/local/emhttp/plugins/apcupsd/apcupsdctl.php on line 76 Unmenu Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 224 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 224 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 419 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 441 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 491 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 492 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 494 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 495 Warning: strtotime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 528 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 528 Warning: date(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 532 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use th Quote Link to comment
archedraft Posted February 13, 2014 Share Posted February 13, 2014 Otherwise I just look like a Dufus who has 12 TB of storage but can't play a DVD. False, they look like the Dufus for bringing one of those old school DVD things that like to skip about the whole time you watch them! Quote Link to comment
ironicbadger Posted February 13, 2014 Share Posted February 13, 2014 Otherwise I just look like a Dufus who has 12 TB of storage but can't play a DVD. False, they look like the Dufus for bringing one of those old school DVD things that like to skip about the whole time you watch them! You laugh about 'old school tech' but my Wife is a primary school teacher here in England (teaches 5 - 6 year olds) and she had some cassette tapes in stock cupboard. One of the kids went in there to get some paper and came out brandishing the cassette asking "Miss? What's this?!" *siiiiigh* Quote Link to comment
binhex Posted February 13, 2014 Share Posted February 13, 2014 peter_sm, stupid question but im assuming you have actually specified your timezone in settings/date and time in the unraid webui yeah?, potentially this setting may of got reset when you moved to v6, worth checking. Quote Link to comment
peter_sm Posted February 13, 2014 Share Posted February 13, 2014 of course I have tested various timezone, and reboot between, same issue, the worst is that the Smart History is broken Syslog attached. I have disabled autostart while I setting up some VM //Peter syslog-2014-02-13.zip Quote Link to comment
limetech Posted February 13, 2014 Author Share Posted February 13, 2014 It sees the PCI device though. It doesn't matter if UNRAID can't see it because you'll end up hiding it from UNRAID anyways. Hm... Then how do I give it to the VM? Here's my disk spec so far: disk = [ 'phy:/mnt/vms/windows/disk.img,hda,w', 'phy:/dev/disk/by-id/ata-Hitachi_HDS5C3030ALA630_MJ1313YNG2450C,hdb,w' ] I thought I needed to add something like: phy:/dev/sr0,hdc:cdrom,r' Since there is no /dev/sr0 for the DVD r/w drive, this won't work. Added SCSI CDROM support to -beta4 (like pata/sata hard drives, pata/sata cdrom support is provided by libata via SCSI layer which is why it shows up as "SCSI" in linux). Quote Link to comment
BobPhoenix Posted February 13, 2014 Share Posted February 13, 2014 Added SCSI CDROM support to -beta4 (like pata/sata hard drives, pata/sata cdrom support is provided by libata via SCSI layer which is why it shows up as "SCSI" in linux). Thank you! Quote Link to comment
limetech Posted February 13, 2014 Author Share Posted February 13, 2014 Tom, I have found a hang up when shutting down unRAID for a reboot. I have unRAID with Xen running and no plugins installed. I have installed Ironicbadger's ArchVM and it is running. It has some unRAID samba shares mounted and I have the Logitech Media Server running in the VM. If I run a "shutdown -r now" command without shutting down the Arch VM, the system hangs after switching to runlevel 6. The syslog before initiating a shutdown is attached. The attached picture is what the console shows when shutting down and where it hangs. If I shutdown the VM first, everything proceeds as normal. Let me know if you need any further information. Ok. I'll investigate this at some point. Quote Link to comment
jbartlett Posted February 13, 2014 Share Posted February 13, 2014 It sees the PCI device though. It doesn't matter if UNRAID can't see it because you'll end up hiding it from UNRAID anyways. Hm... Then how do I give it to the VM? Here's my disk spec so far: disk = [ 'phy:/mnt/vms/windows/disk.img,hda,w', 'phy:/dev/disk/by-id/ata-Hitachi_HDS5C3030ALA630_MJ1313YNG2450C,hdb,w' ] I thought I needed to add something like: phy:/dev/sr0,hdc:cdrom,r' Since there is no /dev/sr0 for the DVD r/w drive, this won't work. If you don't want to wait until beta4 and assuming your hardware supports PCI passthrough: Edit your syslinux file to hide the PCI port in question. append /xen dom0_mem=2097152 --- /bzimage xen-pciback.hide=[glow=red,2,300](04:00.0)[/glow] --- /bzroot In your xen config file, you'd add the following, update to reflect your PCI port pci = ['04:00.0'] Quote Link to comment
limetech Posted February 13, 2014 Author Share Posted February 13, 2014 @Tom Can you look into a issue I see ? its something with timezone and php?? It was no issue on V5, and I have tried several different timezone settings, and rebooted between. I see this when starting the only plugin I use, and also when execute Smart History in unMenu I saw that message before -beta1 release and solved it in webGui by adding this line to template.php: date_default_timezone_set($var['timeZone']); The messages you are seeing are issues in the plugins you are using. Quote Link to comment
peter_sm Posted February 13, 2014 Share Posted February 13, 2014 maybe, I do not have this messages in unmenu / apcups on V5 but on V6 I have it, I can disable my plugin and see what happen. Perhaps unmenu need to be fixed as well for V6? //Peter Quote Link to comment
limetech Posted February 13, 2014 Author Share Posted February 13, 2014 maybe, I do not have this messages in unmenu / apcups on V5 but on V6 I have it, I can disable my plugin and see what happen. Perhaps unmenu need to be fixed as well for V6? //Peter From the very first post of the thread: Also: please disable/remove all add-ons and/or plugins, except for any updated webGui as it becomes available. Quote Link to comment
peter_sm Posted February 13, 2014 Share Posted February 13, 2014 @Tom, Can this help ? see here http://stackoverflow.com/questions/20451719/cannot-set-date-timezone-in-php-ini-file its's about to add timezone to php.ini //Peter Quote Link to comment
limetech Posted February 13, 2014 Author Share Posted February 13, 2014 @Tom, Can this help ? see here http://stackoverflow.com/questions/20451719/cannot-set-date-timezone-in-php-ini-file its's about to add timezone to php.ini //Peter Yeah that's one way to do it. Quote Link to comment
tallnerd1985 Posted February 13, 2014 Share Posted February 13, 2014 Is there any protocol to mount a share from Dom0 and DomU without using NFS or SMB? I would Google it but unsure of what terminology to use to find it. Sent from my LG-VS980 using Tapatalk Quote Link to comment
needo Posted February 13, 2014 Share Posted February 13, 2014 Is there any protocol to mount a share from Dom0 and DomU without using NFS or SMB? I would Google it but unsure of what terminology to use to find it. Sent from my LG-VS980 using Tapatalk I am looking into xen block-attach but have not yet had time to experiment. Quote Link to comment
dlandon Posted February 13, 2014 Share Posted February 13, 2014 Tom, I have found a hang up when shutting down unRAID for a reboot. I have unRAID with Xen running and no plugins installed. I have installed Ironicbadger's ArchVM and it is running. It has some unRAID samba shares mounted and I have the Logitech Media Server running in the VM. If I run a "shutdown -r now" command without shutting down the Arch VM, the system hangs after switching to runlevel 6. The syslog before initiating a shutdown is attached. The attached picture is what the console shows when shutting down and where it hangs. If I shutdown the VM first, everything proceeds as normal. Let me know if you need any further information. Ok. I'll investigate this at some point. Thank you. Quote Link to comment
ironicbadger Posted February 14, 2014 Share Posted February 14, 2014 Is there any protocol to mount a share from Dom0 and DomU without using NFS or SMB? I would Google it but unsure of what terminology to use to find it. Sent from my LG-VS980 using Tapatalk Nope. If it existed I'd have used it. Sent from my Nexus 5 using Tapatalk Quote Link to comment
PeterB Posted February 14, 2014 Share Posted February 14, 2014 I saw that message before -beta1 release and solved it in webGui by adding this line to template.php: date_default_timezone_set($var['timeZone']); The messages you are seeing are issues in the plugins you are using. I have tried adding 'date_default_timezone_set' to the apcupsd plugin php code, specifically the apcupsdctl.php file. If I set the parameter to 'Asia/Manila' the warning message goes away, but $var['timeZone'] doesn't seem to work. What is the scope of timeZone, where is it set? Is it documented anywhere? I'm sure that there aren't many other people on here who want their time zone set to Manila! Quote Link to comment
peter_sm Posted February 14, 2014 Share Posted February 14, 2014 can you check Smart History in UnMenu ? Quote Link to comment
MrLondon Posted February 14, 2014 Share Posted February 14, 2014 Yes i Formatted the key to ensure all was vanilla but when it gotten into the state it was booted into xen but I had since rebooted a few times always without xen Right, found the bug. The problem will show up if on Settings/Share Settings page, under Cache Settings, you set the "Min. free space:" field to blank. This is fixed in 6.0-beta4 and 5.0.6, but a workaround is to set that field to a numeric value. If your intent is have no min space floor, put a 0 in that field. Then stop/start array. TOM you are a STAR, my shares are finally back!!!!! Quote Link to comment
jumperalex Posted February 14, 2014 Share Posted February 14, 2014 [phew] that is great to hear. An unresolved problem like yours could have been a major stumbling block to 6.0 release Quote Link to comment
tallnerd1985 Posted February 15, 2014 Share Posted February 15, 2014 Is there any protocol to mount a share from Dom0 and DomU without using NFS or SMB? I would Google it but unsure of what terminology to use to find it. Sent from my LG-VS980 using Tapatalk Nope. If it existed I'd have used it. Sent from my Nexus 5 using Tapatalk Are you sure, after researching a bit, it seems like iSCSI or FCoE might be the way to go for block level sharing along with the Xen Block Attach method. Sent from my LG-VS980 using Tapatalk Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.