DaleWilliams

Members
  • Posts

    987
  • Joined

  • Last visited

Everything posted by DaleWilliams

  1. Doesn't sound like an unRAID problem... Sounds like something in the Windows 8 boot sequence has decided IT wants to be the local master.
  2. POWERDOWN script attempts to close all running processes, then unmount disks, and then shutdown cleanly. Not sure if it works correctly with BitTorrent Sync...but its worth a try.
  3. Agree with trurl. You've over thought it...its simpler than what you did. Try this: Start fresh. Install Dynamix. Then from within Dynamix choose the plugins you want (from the tab called 'Dynamix' in the GUI)...these plugins will install and update automatically. Then install CONTROL PANEL plugin as instructed in the Control panel-ikosa page. (note that once installed, in Dynamix, click on the 'SETTINGS' tab and you'll see Control Panel. Click on Control Panel and there's a button to install the other plugins.
  4. You're moving to v.5.0.5, correct? In unRAID v5, disk order is irrelevant...EXCEPT for the PARITY and the CACHE disk...its a good thing to keep your disk serial numbers, but there's nothing magic about the order of the DATA drives (in fact, their order can change on every boot up...basically, they become 'b','c','d' etc., in the order that they spin up and unRAID finds them and adds them to the array. Does unRAID boot and operate properly, otherwise? in other words, all is fine, except you can't get the disks assigned?
  5. 1. Start in SAFE MODE 2. Run a Parity Check. 3. Then Post a complete SYSLOG if there are Parity Check Errors. SYSLOG: http://lime-technology.com/forum/index.php?topic=9880.0 (SAFE MODE stops all plugins from loading. SAFE MODE is an Option on the Start Screen next to the MEMTEST option.)
  6. Backup data on it...reformat it...and store 'non-critical', but 'what a pain to recreate' data on it.
  7. Power failures or unclean shutdowns will cause files on the Flash to remain open...creating problems for the GUI's later on.
  8. I hate it when drives go 'click'. I've never had it be good news.
  9. See here: http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues#Drive_Interface_Issues Your errors start out a little like Drive Interface Issue #3.
  10. How about something else loading down your network at night? (not unRAID) Crashplan, or some such thing.
  11. Yeah. I'm afraid the Plex forums aren't as popular as ours. So if you want to be sure you're starting fresh, shut down unraid, put the flash in your pc, Run chkdsk on the flash (Disk Utility on the mac) just to be sure there are no file system errors on the flash. and then delete anything with 'plex' or 'pms' in its filename. (ON my flash, I have: /config/plugins/plexmediaserver /extra/plexmediaserver *most* of the plex stuff is in that first folder...) You probably don't have anything else. put the flash back in unraid and reinstall Plex.
  12. hmmmm... So it sounds as if your array's file structure is back to stable. (i'd run ReiserFS with JUST the 'check' option again, just to be sure) Unfortunately, it looks as if it deleted some data, and didn't have enough to even put it in Lost and Found.Pass 4 -
  13. One thought: The individual data drives are readable without being in the array. You just need the ReiserFS driver on your PC. Mount them in your PC. (note that there's no DRIVER file for Mac's...)
  14. You might have better luck on the PLEX forums, or start with a clean install. ..about all I can tell is, there's something wrong with your plugins-which don't appear to be installing... could just be an initial install gone awry. If you don't have a lot of shows in your database, Id start over with a clean install. If you have a ton o' movies, etc., in an existing PLEX database, there is a way to save that stuff. Where is your PLEX program and database? On a cache drive?
  15. What URL are you using to try to access it?
  16. Sorry. I saw this, but know NADA about NFS. I've not seen that behavior on SMB or AFP. (Could it be something with MythTV? (I don't use that, either). Sounds as if MythTV is closing the file frequently, so when the mover runs its sees the file as ready to be moved. But that's just a theory.)
  17. So before you bring the system down, save the current SYSLOG. You probably have ONE drive that's having errors. If you're feeling ambitious, run SMART on All your drives, post the entire SYSLOG and then bring down the system. Running memtest is fine...I'd be very surprised if it was the cause of the parity errors. Syslog: http://lime-technology.com/forum/index.php?topic=9880.0
  18. unRAID is very small. Mine with an assortment of plugins is 300k. A 4Gig flash should be big enough to last until unRAID v12! Besides, 8 Gig flash drives have become so cheap, they're nearly the least cost of all sizes at the local big box store. What I found is that the size isn't that important, but the BRAND and MODEL is key. Not every USB key has a unique serial number. A unique serial number in the flash key is needed to generate your license.
  19. Obviously, you're in a vulnerable situation, and going slowly and carefully your array should be able to be restored. Others have been in this position, and have been walked through the process. Above all, don't just guess or panic! 1. Do you have a Cache drive? For most of us, its the smallest drive in our array. 2. After that, in theory, (if the array were stable BEFORE the error) when you start the array in maintenance mode, you'll see all the drives as available to be assigned EXCEPT ONE that will appear unformatted. The unformatted drive is *probably* the parity drive, and all others (except the cache drive) can be assumed to be data. Probably the path forward is to assign cache, all the data drives (which are formatte) and the Parity drive (which is unformatted). BUT, the above is theory...I've never personally been in your situation...so you should wait for additional opinions. And if what you're seeing on the web screen is NOT as described, and it sounds like your array was NOT stable and parity may or may not have been valid when the array failed, so you definitely need to wait for more help than I can provide.
  20. Okay. NOW YOU NEED AN EXPERT...to quote the Wiki: "Important Note!!! Do NOT run reiserfsck with the --rebuild-sb or --rebuild-tree switches, unless you are instructed to, by the instruction of a previous run of reiserfsck, or by an expert user! They are last-resort options, to repair a severely damaged Reiser file system, and recover as much as possible. They almost always create a lost+found directory and place in it the files, directories, and parts of files it can recover. It will then be up to you to rename them and restore those files and directories to their correct locations. Many times it will be possible to identify them by their contents, or their size." I'd probably run "reiserfsck --rebuild-tree /dev/md4", but that's 'cuz I have backups and love living on the edge. But I'm not that expert to tell you to do the same. There are a number of experts here...they'll chime in shortly, I'm sure.
  21. http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems Just 'Check' don't try to FIX until you check back in with results...
  22. So, sure: 1. Create the new share 'kids movies' 2. Create 'disk shares' and authorize yourself to see them on SMB 3. You'll then be able to connect to: //tower/disk1 and //tower/disk2 4. You'll see the existing movie share is just a folder at the top of each physical disk. 5. One of your disks will have that folder for 'kids movies'. 6. Should be able to just drag and drop MOVE selected movies from adult folder to kids folder usinng finder/windowsexplorer on each physical disk 7. Where a 'kids movies' folder doesnt' exist, just create it at the top level of each disk. 8. you don't need to create a 'kids folder' on every disk...just those that need it.