johnieutah

Members
  • Posts

    330
  • Joined

  • Last visited

Everything posted by johnieutah

  1. Ok, need some advice guys Just bought a new 2TB Samsung F4. Naturally I want to make use of the preclear script to make sure all is ok. Here's the problem... I currently have a 750 (P), 750 (Data), 160GB (Data) array configuration. I don't have any spare sata cables. I thought I could use the DVD drive's cable, but thats SCSI. So I pulled the 160GB drive out and popped in the new drive. Won't work since preclear says it's part of the array... and of course the array is offline since Unraid is complaining the parity drive is no longer the biggest. So the question is, is there anyway I can preclear the drive without buying more cables? I'm not too fussed about the array being up and running during the preclear process - if it is, that's a bonus. Any ideas anyone (Joe!)? Can I remove the 160GB drive from the array, swap out the 2TB, preclear, then re-add the 160GB drive to array, swap out the parity drive for the 2TB, then re-arrange the data drives once parity has been re-built? Or something... Thanks, Matt.
  2. Hi Josh, think this is the same issue I had. Try omitting 'perl' from the startup command. So just 'slimserver.pl --user slimserver'. I'll double check my setup later but I'm pretty sure that if you're launching squeezecenter manually like this, the perl isn't required... Like I said I'll check later for you. Regards, Matt. Sorry Josh, I've just re-read your post more carefully So Squeezcenter is definitely running if your devices can find it. You must configure everything via the web interface: <server address>:9000. The first time you do this it will ask you where your music is and then scan it (which can take some time). Post any results. Good luck. Matt.
  3. Hi, just wondering... I keep my server constantly plugged in (but switched off). I have WOL on so that I can turn the server on from my laptop/squeezebox. Does this use much power since presumably the network card is always monitoring for magic packets? Thanks, Matt.
  4. I'll hold off for the time being, I'm not experiencing any system crashes or anything, just want to see if it'll improve the Squeezebox performance at all. Can I use DDR3 in a DDR2 system? Thanks.
  5. Hi, need some RAM upgrade advice. I use my Unraid box as a music/video server as well as of course for it's great RAID facilities. Currently I have 1GB RAM and a dual core AMD processor. Is there a limit on the amount of RAM that Unraid will see (like with Windows 32bit)?? Specifically I'm running Squeezebox server which can be quite processor intensive IMO, so I'd like to bump the RAM up. Is there any point sticking another 4GB in there or would another 2GB suffice? Also, slightly on topic, what's happened with RAM prices? I'm sure when I looked a couple of years ago they were cheaper than they are now! Crucial are quoting ~€50 for 2 x 1 GB sticks! Seems like a lot. Thanks, Matt.
  6. Yeah if only it was that easy on Linux
  7. Ok, after much fannying around, I've just successfully upgraded 7.4.2 -> 7.5.0, keeping all preferences, plugins (Music Info Screen setup) etc... in tact. Will post a guide tonight if I've time (World Cup!), but it's a straight-forward process once you know what files & directories it's looking for. Matt.
  8. Thanks for the reply. The log file is created and written to though (the whole "starting squeezebox" - but that's it), the server just dies when this perl loggin error pops up. I suppose I could add my own system out to see what it's trying to write to the log file! root@Tower:~# sed -n 180,200p /mnt/disk1/Programs/squeezeboxserver-7.5.0-30464/CPAN/Log/Log4perl/Appender.pm } $p->{message} = $self->{layout}->render($p->{message}, $category, $level, 3 + $Log::Log4perl::caller_depth, ) if $self->layout(); } $self->{appender}->log(%$p, #these are used by our Appender::DBI log4p_category => $category, log4p_level => $level, ); return 1; } ################################################## sub name { # Set/Get the name ################################################## my($self, $name) = @_;
  9. Thanks for the insight Joe. I did a "perl --version" and it seems I'm running 5.10.0 I'm sure it was 5.01.0... anyways I will look in to upgrading unMenu to the 1.3 version and re-installing perl from there. Cheers.
  10. Ok it's upgrade time and I'm trying to get Squeezebox Server 7.5.0 working... which is annoying since I did have it going a few months back but rolled back to a stable release I'm getting the error message when trying to launch the process:- root@Tower:/mnt/disk1/Programs/squeezeboxserver-7.5.0-30464# perl slimserver.pl --daemon --user slimserver perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_COLLATE = "C", LANG = "en_US" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Your locale was detected as C, you may have problems with non-Latin filenames. Consider changing your LANG variable to the correct locale, i.e. en_US.utf8 [10-04-13 15:30:43.5922] main::init (323) Starting Squeezebox Server (v7.5.0, r30464, Thu Apr 1 06:28:42 MDT 2010) perl 5.010000 root@Tower:/mnt/disk1/Programs/squeezeboxserver-7.5.0-30464# Can't call method "log" on an undefined value at /mnt/disk1/Programs/squeezeboxserver-7.5.0-30464/CPAN/Log/Log4perl/Appender.pm line 189. I've no idea how to sort it. I've sorted out the permissions and ownership issues but this one has me stumped Any ideas guys? Thanks, Matt.
  11. Are there any updates in this area since a lot of the links in this thread are dead. I've currently got Perl v.5.1.0 installed and want to update to a later version, but am having no luck what so ever finding the correct tgz package. Any help is much appreciated. Matt.
  12. Joe, thanks for explaining the differences. It now shuts down perfectly. I guess since the name is the same, I thought that Tom had simply included the powerdown script into the unraid build. Purko, that would make sense. Why anyone would want to use the stock powerdown is beyond me Regards, Matt.
  13. How does this work in contrast to the 4.5 final which includes powerdown? I thought that with 4.5 the included powerdown command did cleanly shut the array down - but it doesn't appear to. It stops SAMBA and that's about it - I guess because there are still files mounted or something. So my question is how do I override "powerdown" in 4.5 to use the unMenu version? Thanks, Matt.
  14. Did you install MySql, Perl and Slimserver on to the flash drive or on to one of your disks? Just wandering what was the best way to run things in the future. Thanks, Matt.
  15. Thanks for your help mate, the sleep 15 seems to work a treat. BTW, in my go script I'm launching squeezecenter without the perl command... seems to work fine but no idea why /mnt/disk2/Programs/squeezeboxserver-7.4.2-29389/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & It works so I'm not complaining. Cheers, Matt.
  16. Bump for the thread and if anyone can help me debugging and sortign out the squeeze server auto start it'd be much appreciated. Even adding the 2 lines of code to the go script doesn't work Matt.
  17. I have always had problems with the autostarting, for whatever reason. I usually just start it manually and be done with it. There must be a reason though The previous version of bubbaraid that I was using didn't have the auto-start feature, so it just started everytime. I can't figure out why it's not working. And I can't debug it either . I've asked bubba on his thread, but he doesn't seem to be around. But like I said, there must be a fairly simple reason why this isn't working firing it up. Matt.
  18. I am having this exact problem now, does any one know why it's not starting slimserver? Permissions or something?? Thanks, Matt.
  19. Ok, changed the slimstart.sh to point to the new slim center install and starting and stopping it works fine now through the bubba web interface. However, the autostart isn't working for me I've set it to autostart and bubbaraid creates a slimserver.autostart file. But it's not firing it up for some reason Any ideas guys? Matt.
  20. I will try this tonight, thanks for the tip. I left the original 7.2.1 SC on there (just in case things went tits up), so if I alter slimserver.sh to point to my new 7.4.2 install, all should be well no? Cheers, Matt.
  21. I was looking for something that was a little more automated for the girlfriend Anyhow, when the shutdown command is issued, doesn't it simply call kill on all the processes anyway?? Anyone? Matt.
  22. Hi, I had this exact issue with 7.4.2... I was previously running 7.5 as linked to by prostuff, but apparently that isn't recommended at the mo http://wiki.slimdevices.com/index.php/Nightly_Builds Anyways, whilst I had no problems getting 7.5 working, with 7.4.2 I had a load of fannying around to do. I figured it out in the end, but it was hassle. Basically the Cache directory should not be 777, it should be 775 I think. I had a few other directory permissions/owner issues as well. All seems to be well now. I will do an ls -l and post tonight if you're interested. Matt.
  23. Hi, when shutting the server down, is there a special shut down command for squeeze center? When using bubbaraid, did the powerdown command just kill all processes gracefully, or did it perform a specific shutdown of the squeeze center process? Cheers, Matt.
  24. Worked a treat matey, just re-scanning the library now Only today did I upgrade bubbaraid to a version that allows you to auto-start the various apps. However, the auto-start doesn't seem to work with slimserver 7.2.1 that bubbaraid supported. So I guess I'll have to add the start command in to the go script. When I get time I'm going to look in to getting rid of bubbaraid and doing a clean install of perl + squeezebox server... That way you can keep current with the updates to unraid. Cheers, Matt.
  25. Ok I have attempted installing squeeze center 7.5 but am running in to a few problems. I got this from the server.log... [09-11-21 19:13:49.6802] main::init (320) Starting Squeezebox Server (v7.5.0, r2 9380, Sat Nov 21 02:06:38 PST 2009) perl 5.010000 [09-11-21 19:13:49.7993] YAML::Syck::DumpFile (108) Warning: Cannot write to /mn t/disk2/Programs/squeezeboxserver-7.5.0-29380/Cache/plugin-data.yaml: Permission denied at /mnt/disk2/Programs/squeezeboxserver-7.5.0-29380/CPAN/YAML/Syck.pm li ne 108. So it's a permissions issue but I'm not sure if I need to chown something or chmod something. This is why I hate unix Any ideas? Cheers. Matt.