Magix Audio Cleaning Lab 16 Deluxe, activation serial number related issues. Get free help, solutions & advice from top Magix experts. MAGIX Audio Cleaning Lab 16 deluxe DESCARGAR: http://www.taringa.net/posts/downloads/7277307/Magix. 
Click Here For Links........ **This video is for Educational. MAGIX Audio Cleaning Lab 2016 serial key download from here: Title: MAGIX Audio.
- Buffalo Linkstation Install Optware Corporation In California
- Buffalo Linkstation 520
- Buffalo Linkstation 220
FFMPEG is not working and probably won't work since the CPU on the Linkstation is not fast enough. Thanks to CuriousMark for the help with the Wiki entry. I hope this Wiki can help some of you. If you were lucky enough to get in on the Buffalo Linkstation fire sale a few weeks ago like I was, you should try doing this install. First, companies are required to comply with law enforcement if they want to do business in this country. Yes, it sucks to have to install yet another app, but they have reasons for it and it works well in conjunction with the original Facebook app. 2, ipkg install openssh openssh-sftp-server. Clicking “Restart service” or rebooting your Linkstation will resolve that issue and it didn’t surface afterwards. Most of the users must have waited for the Plex update as it introduces some interesting new features. The Buffalo update is something new, this time they went the extra length to update some of their libraries properly.
Quote I am more than happy to test as many images as you're willing to build. I think the new builds are great and I'm eager to roll them out. Thank you again, Jeff, for hosting davy's uboot and for this wonderful site!
When I first got my Dockstar the only reason was that it was so cheap ($30!), and that it was much more powerful than my Buffalo router so I could offload the web server from the router. But thanks to you and your site I was able to switch from OpenWRT to Debian, and then upgrade to the GoFlex Net when it came out! Your work is greatly appreciated by countless numbers of untold people like me who rarely, if ever, have a need to visit this forum. Quote It's official, Davy's images are the new default! Just awesome. @davy Thanks again for all your hard work! Your new uboot's have been working flawlessly for a good while now.
I have two GoFlex Net's with external 2Gb 3.5 SATA hdd's. They serve as MythTV backend and slave backend, and web server, media server etc. I retired the Dockstar and sold it on eBay.
But, unfortunately, it was returned in a bricked state as the guy tried, and failed, to reload the uboot. I reloaded the uboot via the and now it works fine again. Anybody trying that procedure needs to be aware that a relocatable uboot like Jeff's is needed during the 'boot from memory' portion. I decided to go ahead and keep the Dockstar. It's not worth the trouble to try and sell it again on eBay.
So I am going to use it as an ARM development platform. Compiling vanilla Kirkwood kernels and some small tools has already been a success.
My next project is to actually succeed in getting a working uboot compiled after my failed prior attempt. Edited 7 time(s). Last edit at 05:01PM by gnexus. I've just come to upgrade u-boot on my 4 Dockstar and on my GoFlex net. It works perfectly. Thank you very much for what you have done. I compiled a new u-boot with no problems.
I can use kwboot to load it and boot my kernel but I can not seem to get it properly loaded into flash. I followed this make mrproper make nsa320config make u-boot.kwb dd if=u-boot.kwb of=uboot.mtd0.kwb bs=512k conv=sync NSA320 tftpboot 0x800000 uboot.mtd0.kwb Using egiga0 device TFTP from server 192.168.1.101; our IP address is 192.168.1.120 Filename 'uboot.mtd0.kwb'. Load address: 0x800000 Loading: ####################################################################################################### done Bytes transferred = 524288 (80000 hex) NSA320 nand erase 0x0 0x80000 NAND erase: device 0 offset 0x0, size 0x80000 Erasing at 0x60000 - 100% complete. OK NSA320 nand write.e 0x800000 0x0 0x80000 NAND write: device 0 offset 0x0, size 0x88 bytes written: OK NSA320 reset resetting. And that is all. Even if I cycle power nothing happens.
Have lurked a year or so but joined up today so I could thank Davygravy for the great work. Also of course, Jeff for all he's done, too much to list. Installed the new uboot last night on my Dockstar and this morning began running the ArchArm 3.4.6 kernel, no problem.
Also, you guys have got that environment thing worked out it appears, just did a diff between my backed up env and current, there ain't no diff. I just simply answered N to the question at the end, as Jeff posted earlier. It was all really no muss no fuss. I really had no problem with the 'frozen' 3.10 Arch kernel, but I know how lonely it can get as you drift further & further out to sea on that tiny, melting iceberg:) Thanks guys! Sputnik Edited 1 time(s). Last edit at 07:33PM by sputnik.
I finally had some free time and decided to update the bootloader on my GoFlex Net. Everything went fine, such that now I'm running 'U-Boot 2011.12 (Apr 18 2012 - 23:08:20)'. At this point I'd like to thank davygravy and Jeff for their efforts to patch U-Boot for newer kernels and provide an easy install procedure.
Since this might be interesting to others, I'd like to describe my update procedure in more details. My GoFlex Net was running with UBIT v0.6 and Debian Squeeze. First, I wanted to update the bootloader using netconsole, but luckily I noticed that after doing 'tftp 0x8000 xxx.kwb' my GF Net accepted at most one or two commands before loosing connection.
I have no idea what the reason was, but such a behavior was surely not safe to perform an update. Then I noticed that Jeff already updated his 'installubootmtd0.sh' script and I decided to give it a try. That's what I did from Debian Squeeze su fwprintenv /root/fwprintenv.txt cd /tmp wget chmod +x installubootmtd0.sh./installubootmtd0.sh -no-uboot-check the '-no-uboot-check' key was neccessary because I had UBIT v0.6 and Jeff's script refused to recognize it. Here's the log of Jeff's script!!!!!!
Buffalo Linkstation Install Optware Corporation In California
DANGER DANGER DANGER DANGER DANGER DANGER!!!!!! If you lose power to your device while running this script, it could be left in an unusable state. This script will replace the bootloader on /dev/mtd0. This installer will only work on the following devices: Seagate Dockstar Seagate GoFlex Net Seagate GoFlex Home Pogoplug v1 Pogoplug Pink (v2) Do not run this installer on any other device. By typing ok, you agree to assume all liabilities and risks associated with running this installer.
If you agree, type 'ok' and press ENTER to continue: ok # checking for /usr/sbin/nandwrite. # checking for /usr/sbin/nanddump.
# checking for /usr/sbin/flasherase. # checking for /usr/sbin/fwprintenv. # checking for /etc/fwenv.config. # Validating existing uBoot. Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00080000.2012-08-03 21:54:21- Resolving jeff.doozan.com. 50.116.34.13 Connecting to jeff.doozan.com 50.116.34.13 :80. HTTP request sent, awaiting response.
301 Moved Permanently Location: following -2012-08-03 21:54:21- Resolving projects.doozan.com. 50.116.34.13 Connecting to projects.doozan.com 50.116.34.13 :80.
HTTP request sent, awaiting response. 200 OK Length: 1133 (1,1K) text/plain Saving to: `/tmp/valid-uboot.md5' 100% 1.133 -.-K/s in 0s 2012-08-03 21:54:22 (31,7 MB/s) - `/tmp/valid-uboot.md5' saved 1133/1133 ## Unknown uBoot detected on mtd0: ad2f48df8285fe9703b260c7e39ab2ad ## ## -no-uboot-check flag detected, continuing installation ############################################ Your device could not be auto-detected. You must be using a device listed below to run this installer. What device are you using?
Type the number of your device and press ENTER. 1 - Seagate Dockstar 2 - Seagate GoFlex Net 3 - Seagate GoFlex Home 4 - Pogoplug v1 5 - Pogoplug v2 - Pink 6 - Other 2 Selected Seagate GoFlex Net # Installing uBoot ## Installing goflexnet davygravy-2012-04-19 -2012-08-03 21:54:28- Resolving download.doozan.com. 50.116.34.13 Connecting to download.doozan.com 50.116.34.13 :80. HTTP request sent, awaiting response. 200 OK Length: unspecified text/html Saving to: `/tmp/uboot.mtd0.kwb.md5' 32 -.-K/s in 0s 2012-08-03 21:54:28 (1,08 MB/s) - `/tmp/uboot.mtd0.kwb.md5' saved 32 -2012-08-03 21:54:28- Resolving download.doozan.com.
50.116.34.13 Connecting to download.doozan.com 50.116.34.13 :80. HTTP request sent, awaiting response.
One more thing. I noticed that after upadting to the latest U-Boot the kernel was obviously unable to mount rootfs correctly such that the system didn't boot. After connecting serial console and monitoring boot process directly, I immediately was able to recognize the problem Waiting 10sec before mounting root device. One more feedback. Today I bought a second brand new GoFlex Net (not hacked) and decided to unlock it via direct serial connection. After booting to that crippled Linux GF Net has, I downloaded and executed Jeff's U-Boot script.
Bash cd /tmp wget chmod +x installubootmtd0.sh./installubootmtd0.sh Everything worked flawlessly. Of course I chose to disable Pogoplug Services and changed arcNumber to 3089.
Big thanks to Jeff for offering such an easy procedure to unlock GF Net. Arbie2 Wrote: - Thank you, thank you! Your new uboot procedure works with my GoFlex Net. With a USB stick and no SATA drive, it boots from the USB stick.
With no USB stick and one SATA drive, it boots from the SATA in either slot. With no USB stick and two SATA drives, it boots from the right-slot SATA. It's difficult to argue with success. However, I do note the following anomaly booting ArchLinuxARM: With a USB stick and one SATA drive, it boots from the SATA in either slot. With a USB stick and two SATA drives, it boots from the USB stick. With my Dockstars, I always carry an emergency USB stick to boot from for repairing a failed/ failing disk drive.
I though that the GoFlex Net would boot from the USB stick regardless of whether a SATA drive was present. Apparently not. For now, I'll carry a spare SATA drive for GoFlex Net emergencies. However, my (yet to be received) GoFlex Home has only one SATA, and my two SATA drive solution won't work for emergencies.
How are people handling SATA disk problems on their GoFlex Home? How can you do that? Could you post your fwprintenv seetings? Mine only boots from the right slot. I flashed this uboot to my dockstar using Jeff's script, and it appeared to flash ok. When I reboot, I get the following message when trying to start the kernel from usb (watching via serial): Loading file '/boot/uImage' from usb device 0:1 (usbda1) 1432436 bytes read Loading file '/boot/uInitrd' from usb device 0:1 (usbda1) 4702937 bytes read ## Booting kernel from Legacy Image at 00800000. Image Name: Linux-2.6.32-5 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1432372 Bytes = 1.4 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum.
OK ## Loading init Ramdisk from Legacy Image at 01100000. Image Name: initramfs Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4702873 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum. OK Loading Kernel Image. OK OK Starting kernel. Uncompressing Linux.
Done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x00000bb6). Available machine support: ID (hex) NAME 00000690 Marvell DB-88F6281-BP Development Board 00000691 Marvell RD-88F6192-NAS Development Board 00000692 Marvell RD-88F6281 Reference Board 00000a76 Marvell eSATA SheevaPlug Reference Board 00000831 Marvell SheevaPlug Reference Board 00000a63 Marvell GuruPlug Reference Board 0000085b QNAP TS-119/TS-219 000009c6 QNAP TS-41x 00000b44 Marvell OpenRD Ultimate Board 00000939 Marvell OpenRD Client Board 00000915 Marvell OpenRD Base Board 00000b1e HP t5325 Thin Client Please check your kernel config and/or bootloader. I assume this 'machine ID (r1 = 0x00000bb6)' is related to arcNumber. Bb6 hex is 2998 decimal.
At the 'u-boot' prompt, 'printenv arcNumber' gives 2097, which in hex is 831-one of the IDs listed for Available machine support. What do I need to do to be able to boot? Davygravy Wrote: - We know that folks running ArchLinuxARM and others use the u-boot that is piped out of this site, and we want to be a seamless change for them, as well. Any plans of Uboot supporting 'intelligent' boot choice on GoFlex Net, when both USB and SATA drives are hooked in? Currently it works on Debian by using LABEL env param, but doesn't work out of the box on ArchLinux ARM.
You were seemingly determined to support both OSs, since most folks would have difficulty fixing it on their own.:) Also, can you post a list of Hush Shell commands implemented in Jeff's & your Uboot version? Edited 4 time(s). Last edit at 03:49PM by sambul14. @sambul14: I've read some of your posts. The only solution I found is checking for the presence of an usb drive via trying to load the kernel from that place. If it is ok then root=/dev/sdb1, else root=/dev/sda1. If you remove SATA drive this approach doesn't work, but you DON'T really need to do that, or maybe yes?
The other option is install a little distro on nand space, this will avoid all your problems cause your GFN will boot everytime from nand, and just some shell scripting will be needed to handle your other mountpoints. Replying to my own previous post here, and to Handy1 who PMed me regarding this.
I will re-research the issue of GPT and 64bit support. IIRC, it requires at least two settings changed on the config.h file.
CONFIGEFIPARTITION (which may be a misnomer - perhaps GPT would be a better name for it) and CONFIGSYS64BITLBA. Once I roll some trial uboot images, and test that they will boot normal stuff, then I can put them out there for a few of you to try with 3TB drives and a GPT layout. The may of the rescue images that I built and posted lately have GPT support.
(via my Dropbox public folder). AFPDplug, SMBPlug, OWFSPlug, Cloudprint, Optware-DG, uBoot. Bodhi Wrote: - @RonIt's unusual that your prompt is 'ubit0-6:'.
Did you run installation script from Pogoplug stock OS ? How did you begin? Booting without USB, loged in with SSH? Also, why did you use the option '-no-uboot-check'? What happened before that caused you've decided to run the installation with this option?
Normally, this option is not needed. My Seagate GoFlex Home is freshly done from these instructions, installing ubit 0.6, etc. Etc: To install the new uboot script, it said you had to use -no-uboot-check -Jamie M. Toysareforboys Wrote: - bodhi Wrote: - - @RonIt's unusual that your prompt is 'ubit0-6:'.
Did you run installation script from Pogoplug stock OS ? How did you begin? Booting without USB, loged in with SSH? Also, why did you use the option '-no-uboot-check'? What happened before that caused you've decided to run the installation with this option? Normally, this option is not needed.
- My Seagate GoFlex Home is freshly done from these instructions, installing ubit 0.6, etc. Etc: flex-home#qt-platformtabs-ui-tabs3 To install the new uboot script, it said you had to use -no-uboot-check -Jamie M. You don't really need to install uBit. Installing uBoot will make it a little more straight forward, and works with both Debian and Arch (However, uBit should work, too). But not too many people run that to install Debian. We usually just run the installubootmtd right from the stock Pogo OS.
Buffalo Linkstation 520
Can you try to boot back to stock Pogo and run uBoot installation script from there. These errors should not happen (it indicates that the sed and head commands could not be found in the OS where you run installation):./installubootmtd0.sh: line 342: head: not found./installubootmtd0.sh: line 342: sed: not found. I might have found an issue with this uBoot: Either there's something wrong with the kernel patch or uBoot doesn't pass proper arcNumber to the kernel on some devices. There's was a post in this where somebody could boot the kernel and the arcNumber wasn't what he set it to. Moonman Wrote: - I might have found an issue with this uBoot: Either there's something wrong with the kernel patch or uBoot doesn't pass proper arcNumber to the kernel on some devices.
There's was a post in this where somebody could boot the kernel and the arcNumber wasn't what he set it to. It's been a while since I've hacked on my arm hardware, but I still have a couple of pristine PogoPlug E02s which need to be jail broken and have their uBoot reflashed so that they can eventually become the backup hardware for when my existing servers bite the dust. I am wondering what is the latest uBoot that I should use for this purpose. I am still running Squeeze here, not Wheezy, so I need a uBoot which will boot Squeeze, but I'd prefer to install one which will handle Wheezy and the later kernels for when I eventually upgrade. Is the top post of this thread by davygravy still the best version and the one I should be using? I can use tftp to install it, as davygravy suggests, but I'd prefer to use an installer if one is available.
(Fewer possibilities for cockpit errors.) So, can someone please point me to the latest and greatest uBoot and installer? Thanks in advance.
The new version of the firmware is going well, it’s time to look at what’s next. As a new year’s resolution I promised my family that I’m doing something creative with my free time that also benefits them. The Buffalo + Plex project will benefit them as soon as they can start using the Linkstation that I’ve been hogging for testing in the past few months.
Also, their main goal was to get Plex on it, which I’ve done. This completes the main goal of the project and I’ve also implemented a lot of features I didn’t even think would be needed. What will the Buffalo + Plex project provide in the future? I will update the components I’ve implemented with newer versions (Plex, Transmission, FlexGet) as these usually have new cool features that’s worth having. The auto-update feature will also be used to distribute these changes.
(If you have upgraded to the Chris version.) Obviously, I’ll try to fix bugs as they surface, however I might not be able to fix the bugs that Buffalo introduces by not updating the firmware with newer versions of applications. (OpenSSL avoided the heartbleed bug by being too old) I have uploaded the development/build framework I have created over the months, to GitHub. You can reach it. If you want to continue implementing things in the same manner, clone the repository and go ahead. (The README.md provides the necessary information to set it up.) If you want to understand how I implemented some features, look up the script and feel free to reuse that knowledge.
What will the Buffalo + Plex project NOT provide in the future? I will not implement new features in the foreseeable future. I’m looking into a new project that I want to take on and that will require most of my free time. (I’ll introduce that in due time.) I kept a short list of features that were requested, I’m going to try to list them here together with some guidance on how to implement them. With SSH enabled in the production version of the firmware, you can hack away at your NAS as much as you want.
BE ADVISED, I will NOT be able to provide regular support for hacking your NAS; in the black world of SSH, you’re on your own. (Except there’s a huge community that can help at.) I have put together a FAQ for the most common questions. (Don’t forget to clear your browser cache after upgrade.:)) Features NOT implemented Torrentexpander is neat little script that unzips or unrars your torrents after it has finished downloading. It has been requested by festol, but I never got around to implement it, most probably because as a script, eventually you’ll have to open it and configure it for your liking. Putting it on the admin interface didn’t really help with it, just like I realized the same with FlexGet. (I already implemented that, though.) To implement it, download the script and unzip it.
Set up optware if you want unrar to work and copy the script to somewhere under /opt. (So you keep it after flash upgrades.) Run the script and answer its questions.
Deluge is a torrent client, much like Transmission. It might or might not have better features than Transmission but for sure it didn’t have any ARM ports. Even with older ARM ports for Transmission it was hard to compile things from scratch for the latest version, so I didn’t even start with the Deluge source. To implement it, try. The only advantage I see is the socks5 proxy. You can also try the setup-compiler script from the source of Buffalo + Plex to set up a development environment for yourself.
FlexGet web interface I tried to set up the FlexGet web interface but it’s too experimental at this point and the “-c” option I use to redirect the config file didn’t seem to work with it. (Also you can edit your config file in your favorite editor through the network share.) To implement it, enable SSH, log in and run /usr/local/flexget/bin/pip install flexgetwebui New versions of core components (Twonky, PHP, MySQL, Lighttpd, PHPMyAdmin) I was thinking for a while to start upgrading some of the new core components of the firmware and objecttothis was also asking for it, but eventually it boils down to this: at one point you have to face the upgrade of the GLIBC library and together with that you have to upgrade the kernel. If you upgrade the kernel, you need to do a complete check of each and every setting of the firmware to make sure you didn’t break anything. Since I only have an LS-WVL, I wouldn’t possibly be able to test some of the firmware’s features, so I won’t do it. If I want to refrain from upgrading GLIBC and the kernel, I have limited options for upgrade. I can use the optware packages to upgrade MySQL, PHP, etc, but those are also a few versions behind and they are wired to look at /opt for their libraries which I also didn’t want to use.
I wanted /opt to be available for anyone to implement their own changes. I could check the which has newer versions of these items, but I’m afraid eventually I’d run into the GLIBC misery. I could have tried rebuilding these packages to run from elsewhere but I didn’t see the benefit. I am a security freak but to secure this device, it would take a lot more than to rebuild a few packages. If you want a newer MySQL, PHP, or lighttpd version, install optware and use ipkg to install the latest there is or check if you can run the OpenWRT version of OPKG. Or say goodbye to the web interface and install Debian ARM on the device.
That has some better features, newer GLIBC and new kernel. Older/different versions of Transmission I will only support the latest version of Transmission with the latest version of the previous branch. (2.84 and 2.77 at this time.) Festol was asking for transmission 2.03 for a a specific need, now with SSH you can do it for yourself. Optware has 2.03 in its repository, it shouldn’t be hard to upgrade. (Be aware that you need an older version of libevent as oxygen8 mentioned in a thread.) CrashPlan One of my dreams was to have CrashPlan on the Linkstation so I have an archive in the cloud. The first issue is that you have to install java which is not impossible, but not very easy either.
Then you have to face that CrashPlan has a requirement of 512Mb of RAM to run, while the Linkstation (LS-WVL) only has 256Mb. So I didn’t even try. If you’re interested head over and read about it. For what it’s worth 169-chris suits my needs more than enough, so I would never use any of what you mentioned above but that’s just me. I dont even use plex or any media server on it, just storage really and transmission/flexget.
I use a rasp pi with openelec for media needs. Which is why I wanted to try NFS on the LS-LHX but I could not get it to work and all examples I found didn’t really lead anywhere. Maybe you could do a little FAQ on how to set NFS up once enabled? Updating to newer versions of flexget/transmission if possible is about the only thing I would be keen on being able to do myself, i.e. Probably already possible via ssh but when I tried to update flexget it killed the daemon and I could not get it back up and now I have two PIDs in the status file while only one applies to the config.yml Maybe an option on the web interface to update the components (flexget / transmission) without having to flash the firmware.
Would also save you the hassle of pushing firmware updates out and rather use pip or easyinstall in the background for a single component “on demand” update so to speak. Don’t know if that is actually doable via webinterface though. BTW I tried posting to the previous entry but the website returned an error each time. Hi nuwonda, There were some issues with the hosting company earlier, hopefully it’s fixed now. It’s ok to post to new entries, more people will likely read it.
If there is a new version of FlexGet, you can update it through SSH with the command “/etc/init.d/transmission.sh updateflexget”. I didn’t put it on the web interface because if something breaks during the upgrade, you won’t know and less-tech savvy users can’t really fix it for themselves. (I don’t control what gets into the new version of FlexGet.) Restart your NAS so the PIDs get back to normal, stop FlexGet on the web interface, then do the upgrade and start FlexGet again. During development 1.2.248 was the latest version of Flexget but then 1.2.249 came out and I was able to upgrade without a hitch before creating the production package. As for Transmission, since I had to compile it from scratch and then make sure it works properly, I don’t think I’ll set up any updates through SSH. The source of the whole project is on GitHub already, when the new files get uploaded you can download them manually and unzip them so you don’t have to do firmware upgrades. I’m not planning to do firmware upgrades with each new version of FlexGet, because it’s quite often updated.
New Transmission and Plex versions are more likely as they were the main points for most of the users. There is a fix on the way for the transmissionrpc package though, that will be part of the next version. If you want to do totally different packages, you can always install optware and do it yourself, you might need to rewrite /etc/init.d/transmission.sh to point to your optware files and that’s it. As for NFS, it was implemented because of a request, but just like SSH, you’re mostly on your own using it. You need to know NFS properly before you start using it on the Linkstation. The only test I did with it was a basic setup like this: Enable NFS, set the network address. Network address is the “fix” part of your IP address.
Buffalo Linkstation 220
For example if your IP is 192.168.100.100 and your netmask is 255.255.255.0 (or “24” in short), your network address is “192.168.100.0”. The first three numbers are the same, the last one is zeroed out. “Subnet mask” is the netmask.
After you set this up, you have to add NFS folders for sharing. Just click the folders in the dropdown table that you want to share. On the client side you have to mount the NFS shared folders. In linux you can use mount -t nfs -o nfsvers=3 192.168.100.100:/mnt/array1/myshare /mnt. This will mount your “myshare” into /mnt. In other operating systems you have to find out how to mount NFSv3 shares. Fair points regarding updating!
Re NFS I was silly I don’t need to mount anything as it turns out nfs://192.168.1.48/mnt/disk1/share just works from OSX or Openelec (.48 = Linkstation) Browsing for “nfs://” alone just doesn’t work on it’s own as the folder is not broadcast on the network I guess. One thing though, it seems any USB disk connected to the Linkstation does not show up on the NFS tab and hence cannot be shared via NFS? /mnt/usbdisk1/) Oh yeah and as I replied to one of your older blog entries, your form here doesn’t like copy pastes with certain keywords in it I guess (etc // path maybe?) Keep up the good work! The NFS on USB got me thinking. The problem with USB is that any time you attach or remove a USB disk, all the services that access them will restart. (Including SSH for some reason.) So my guess is that the original implementation didn’t consider USB disks for NFS because then all NFS connections would get dropped each time you add or remove a USB drive.
For now, you can go into /etc/exports through SSH and modify it to your liking. Obviously if you change it on the web interface afterwards, it will get overwritten so change what you can on the web interface and then head over to /etc/exports and modify it. I’ll look into the comment problem (this is the standard WordPress comment window), thanks for raising it. I switched back to smb cause kodi library seems to have problems maintaining just one link for the media entries and with both smb (usbdisk) and nfs (nas disk) I ended up having all entries double arf. On a second note, I updated flexget as described above.
However, something seems to be amiss with the daemon. Flexget.log throws an Error: Daemon already running for this config. Any means of getting to reload the config file does not show up in the log and seems to go nowhere. Restarting the NAS, transmission, flexget etc, didn’t fix it either.
Maybe I need to reinitialize the daemon? Hmm I think the flexget update might have reset the loglevel for the daemon, since flexget.log is still logging critical stuff but e.g. Doesn’t show anything when you reload the config.yml from the webinterface, it does reload it though, just doesn’t log anything if it passes without errors.
I tried to set the loglevel via ssh: /usr/local/flexget/bin/flexget -c /mnt/disk1/share/transmission/config/flexget/config.yml execute -L verbose daemon reload but it doesn’t change the loglevel for the flexget.log, rather just on screen in the terminal. No biggie, just wondering how to set it so the daemon writes info stuff to the.log file again. Hi Will, The bad news is that this custom firmware is absolutely 100% NOT compatible with your Terastation. Someone tried it earlier and broke the Terastation, so DO NOT ATTEMPT.
The better news is that if your NAS has the Marvell 88E6281 CPU as I suspect (Terastation ES on the BuffaloTech webpage), then I think Plex is compatible with that processor. You just need someone with that NAS to hack the firmware and add Plex onto it. Unfortunately I didn’t get enough donations to buy another NAS device so you’ll have to look around on the buffalo.nas-central.org website, maybe someone has already done it. Hi hostet, The auto-upgrade feature has a glitch in the “Chris” release. You can find more information about it on my blog entry where I announce the new “Andimaginary” version which should fix the issue. You can download the “Andimaginary” release from the.
‘s a blog entry with all the changes. I’m not sure if Plex on NAS supports channels at all, search around on other forums and ask if Synology users can use channels on their NAS. I’ve never used that feature but I’ll try when I get a chance.
(My TV is still in a box after my move) – GaryT.