• Posts

  • Joined

  • Last visited

Everything posted by DaleWilliams

  1. http://lime-technology.com/forum/index.php?topic=9880.0 Post your syslog.
  2. Look in SHARES tab. Find the APPS share definition. Setting should be 'cache only'. If you don't have a defined APPS share, create one and set it as Cache Only.
  3. Turn off AFP if you've set it ON. Unless you're running TimeMachine, you probably don't need it.
  4. Thanks for the update, jonp. [me=DaleWilliams]applauds everyone involved! [/me]
  5. http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_interface_issue_.231 Your syslog shows both sdr and sdq having issues....and at first glance appear to be physical. Try the link above for details, but in summary, SATA cable may be bad/loose. Also could be a power supply problem, so check that all connections are solid. Perhaps those two drives share a common controller, are in the same drive cage, or share a SAS cable?
  6. There are settings in the PLEX GUI interface (not the PLEX VIEWER app, but at port #32400), look for the ADVANCED tab, and you should be able to limit the frequency with which PLEX checks your disks for new media in your library. You can turn them off and make the updates manual. I just do them once per day.
  7. What's on it? Did you install something like a torrent engine, or PLEX?
  8. check the web page of the card manufacturer (Syba and maybe Marvell) for a firmware update that supports drives > 2.2 TB.
  9. syslog Line #1684 = Jun 23 15:35:04 Server kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_interface_issue_.233 This is transmission error. Most common causes are power related or unreliable connection especially if backplanes are involved. Is the problem still reproducible? If so, can you please try to move it to different power connector and SATA port and see what changes? ATA4 is this disk, "ST3000DM001-1CH166"
  10. Without a syslog, I'd suspect simple file directory corruption because of the power outage. Shutdown the array, put the flash in a PC (Mac) and run chkdsk (Disk Utility) on it. If that doesn't fix the problem, then check back in and post your syslog. http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog (If you use a web Gui add on for unRAID ( like Dynamix or unMENU) the syslog may be on one of the web interface pages, too. Be sure to post the ENTIRE log, not just the little summary of the last 20 lines.)
  11. BOX.com There's no Linux Sync native cabability but they have webdav and some folks use copy.com http://seb.so/50gb-of-cloud-space-with-box-automatically-syncd-on-linux-with-webdav/#box_mountwebdav https://support.box.com/hc/communities/public/questions/200285268-Box-Sync-for-Linux-anyone-
  12. You have several disks showing errors. ata#15,16,17. Are they all on an add-in SATA card? There are CRC errors which can be bad SATA cables. The other possibilities (from the wiki at: http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues ) are: However, if a better SATA cable does not solve the issue, then it is probably a power problem (loose power cable or backplane connection, poor connectors, poor power splitter, overloaded power supply, too many drives on power rail, bad power supply, etc). Because you have THREE disks with errors, I'm wondering if its an add-in card?
  13. sorry, I bobbled the quote of the last line from the Wiki. It says, "If you get an error that says reiserfs_open: the reiserfs superblock cannot be found on /dev/sdX. Failed to open the filesystem. it usually indicates you attempted to run the file system check on the wrong device name. For almost all repairs, you would use /dev/md1, /dev/md2, /dev/md3, /dev/md4, etc. If operating on the cache drive that is not protected by parity you would use /dev/sdX1 (note the trailing "1" indicating the first partition on the cache drive) " So (again from the Wiki) your command to check the cache drive would be: reiserfsck --check /dev/sdh1 Assuming that the cached drive is 'h'. (That verification that cache=h was what is cut off at the beginning of the log.) A complete log may require that you Telnet into the box, and copy and paste it out by hand. If you're picking it up from a web gui, it may be truncating it. There should be a 1000 lines or so of 'setup', where unRAID is busy finding the drives, assigning them drive letters, loading your plugins, etc.
  14. I'm not as good at Syslog reading as most on the forums. It looks like you restarted the log, thus cutting off the startup sequence. The startup is where drive assignments show up...so drive 'sdh' is clearly in trouble...but I can't tell if that's cache or not. Later on, 'cache' has some open files and kicks out some errors, but they could be totally separate. What I would do is run SMART on all your drives, and post results as well as full syslog. Include your VERSION and SYSTEM LOG for support issues If you're sure that its the cache drive and SMART is clean, then run "Reiserfsck --check" on it to see if you can clean up the directory. Cache is a bit of a special case, so read the Wiki and mind the last sentence on the page: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems "If operating on the cache drive that is not protected by parity you would use /dev/sdX1 (note the trailing "1" indicating the first partition on the cache drive)"
  15. Oh! ....huh! I've no idea. Someone more in tune with unRAID innards will have to weigh in.
  16. I believe you can create a normal unRAID array WITHOUT a parity drive (some folks do this at initial setup/startup...they copy all their data over to the data disks and THEN assign a parity drive which then calculates parity on all the new data in one pass.) Use a FREE key...assign just one data drive...voila...instant one drive unRAID.
  17. They'll automagically use the other discs UNLESS you set 'Include' or 'Exclude' in your share definition.
  18. What you're essentially doing is deconstructing your unRAID. If you pull TWO drives out at the same time, your Parity becomes worthless and must be rebuilt from scratch to protect the remaining drives. Better is if you are able to get ONE drive fixed, that would allow the SECOND drive to be replaced and then existing Parity could attempt to rebuild the replaced drive. But, 'Yes', you can remove a drive (or drives) from the array, mount them on a PC (with a suitable REISERFS driver) and extract the data. That is, IMHO, one of the nice things about unRAID.
  19. Roku has a 'channel' that you can install for 'Plex'. A 'channel' is like, 'netflix', or 'youtube', 'amazon prime', 'PBS on the web', etc. The Roku PLEX channel uses standard DLNA for network transport. Your movies are on unRAID. PlexMediaServer(PMS) runs on the unRAID and it catalogs your movies, builds previews, creates metadata, etc. The Roku PLEX Channel then accesses (via DLNA transport) the PMS and paints on your TV what looks similar to a Netflix view of all your media, including metadata, etc.
  20. You might google the web for a Mac System Preference Panel called 'HOSTS'. It lets you specifically match IP addresses against names. So my hosts file says = tower.local and = tower ...takes all the worry away when I type an address in the browser.
  21. Bjp999, So following your logic, wouldn't this work: 1. Files are 'stuck' on the cache drive and may or may not have been written to user shares. 2. "movies" share is defined and is a top level folder on disk1, disk2, and disk3. 3. Using MC (or whatever) copy the top level folder contents FROM 'Cache/movies' into "DISKx Share/movies" (where x is 1,2,or 3) This is a specific copy from a specific physical disk (cache) to another specific physical disk. The problem is that the same file might end up in disk1/movies as well as disk2/movies, but that's usually better than losing a file. And there are tools to detect duplicate files.
  22. Stating the obvious: When you 'swap out' the cache drive, its not parity protected and won't be rebuilt. If you have Apps or other non-Movered data on your existing cache drive, be sure to copy them off.
  23. Is there anything on it? If not, I'd take the coward's way out (or is it just expeditious brute force?) ...anyway...you could copy the valid bits from cache to your PC/MAC and reformat the cache drive. reassign it to the array.