interwebtech

Members
  • Posts

    1209
  • Joined

  • Last visited

Everything posted by interwebtech

  1. when its trying to access that drive (during boot it will pause long time, from the web gui it will hang, etc) the whole machine freezes up and becomes unresponsive. The 5in3 cage drive light is on full when it happens. I was able to shut down from the command line. Will get a disk from Best Buy today and give that a try.
  2. Shutdown, removed the drive tray and restarted. unRaid loaded up with the array stopped (missing disk). Should I try a new disk? I can't see anything in the logs but it definitely had probs with disk12 after the rebuild.
  3. Rebuild finished without error but the drive is being slow and unresponsive. Trying a reboot right now but it seems to be stuck trying to read from the drive. I have a login prompt now at the console but Tower is not showing on the network or webgui loading either. Going to shutdown and pull the disk and then reboot see if I can at least get the syslogs. drive light is full on and getting a timeout error at the console. syslog-20141007-211515.zip syslog-20141007-213051.zip
  4. its running a rebuild back on the original disk12. Total size: 2 TB Current position: 217 GB (10.8 %) Estimated speed: 53.0 MB/sec Estimated finish: 9 hours, 21 minutes
  5. The whole process of initializing all the connected drives isn't displayed anymore? Goes straight to unRaid boot menu after the mainboard POST process. Anyone seen this before? Once unRAid boots I can see all the connected drives and the device is listed in unMenu PCI devices. I swapped in another AOC-SASLP-MV8 with no change. Very odd.
  6. I am pretty sure it was a loose data cable. Drive 12 is in slot next the one I added cache drive to couple days ago. May have jostled the cable connecting the cache disk (all 5in3 cages, bottom cage, furthest in the back connector). When I pressed on it got a click feel (locking connectors). Need some advise here. I power down last night and have done nothing since I posted above.
  7. Drive 12 failed during huge data transfer. Web GUI showed it red balled. Attempted a swap-disable (5TB in as new parity, 2TB parity as replacement) but nothing happened when it rebooted. Array started on its own and it still showed 2TB as parity and 5TB as unassigned. Not wanting to risk losing data, I shut down and swapped the disks back around (2TB back to parity and "failed" drive back in as disk 12, reseated the data cable on disk 12 (connected to AOC card) and restarted. One thing I noticed was the AOC-SASLP-MV8 didn't do its post on the screen! unRaid booted up and all the drives are visible but now disk 12 slot is "not installed" and suspect 2TB is "unassigned" (see pic). What is my next step? I am pretty sure "new config" will wipe out my data? Have attached 2 syslogs, one was of the disk fail, the other the reboot attempt at swap-disable. drive_failure_syslog-20141006-221302.zip syslog.zip
  8. thanks it works. Just tested it by opening in a browser that has never seen the web GUI and all the old servers are gone as well as the orphaned sync movies.
  9. Mine should ship today It will be my new parity replacing 5TB Toshiba I wish I had not bought so early. lol
  10. been there done that. I mentioned it in the first post
  11. newegg has it $10 cheaper with code: EMCWPPH33, ends 10/8 http://www.newegg.com/Product/Product.aspx?Item=N82E16822236737
  12. Just noticed something that may be a clue. If I open Plex Server web GUI using IP address (default if invoked from docker page), it shows 2 ghost "Tower" servers (see pic in fist post). However, if I open the GUI using netbios name i.e., http://tower:32400/web/index.html#, only ONE ghost is listed. Don't know what it means but maybe help?
  13. did that (mentioned in my post above). Only showing the live one.
  14. only have the one live server showing there.
  15. Any ideas on how to get rid of these "ghosts" of servers no longer registered (removed from plex.tv site too). "Plex_Server" was my Windows install (disabled) and the other "Tower" ones are missteps (removed, reinstalled, etc) to getting it running properly. I also have ghosts of web syncs stuck (files deleted off bitcasa, but persist in display). I know these are not specific to unRaid implementation of Plex but I can't get anyone to response on Plex forums. So much for "special" forums for plex pass holders lol.
  16. How much RAM is needed for that to be seamless process? I have 8GB now but still have 2 slots empty. Love to hear any optimization tips you have cuz ima Plex noob who has jumped in with both feet.
  17. Woo hoo!! So no need for plan B?? Moving forward with Plan B. I realized I still needed a way to transfer the movies between boxes. 2.5 hours into a 843 GB transfer right now with 6 or 7 batches of roughly the same size to follow. I actually do this over the network. Why not? You already have the mechanism in place with the mount that you performed. Here's what you can do: login via console on tower1 (I'll call them tower1 and tower2 for now). type "mc" to bring up midnight commander. browse to your "source" on the left and your "target" on the right. Select the items on the left you want to move to the right by hitting "ctrl + t" on the keyboard (you can tag multiple files / folders). Hitting F5 (on your keyboard) will then initiate a "copy" whereas F6 could be used to initiate a "move" There is even an option to have the job run in the background so you don't have to leave your terminal session open to do this. I've literally copied terabytes of data with this method and had zero problems. I was even still streaming movies and running VMs while the copies were going. no problems. yep. exactly what I am doing except I use INSERT to select folders from the left.
  18. Woo hoo!! So no need for plan B?? Moving forward with Plan B. I realized I still needed a way to transfer the movies between boxes. 2.5 hours into a 843 GB transfer right now with 6 or 7 batches of roughly the same size to follow.
  19. for the record, this worked. Found it on http://ubuntuforums.org mkdir /mnt/[localShareName] mount -t cifs //[netbios-servername]/[sharename] /mnt/[localShareName] -o username=root@[netbios-servername],password=[remote-tower-root-password],iocharset=utf8,file_mode=0777,dir_mode=0777 where values in [xyz] are replaced with your variables
  20. Thanks for all your help. I think I will opt for Plan B and consolidate all the movies on Tower. Tower2 was built back with v4.7 before I found out v5.x could handle larger than 2TB drives. Tower just got a CPU upgrade to a AMD FX-series 6 core for Plex capabilities (and a new motherboard while t.shooting the slow write speeds) so I think I will move what I can fit for now and order a couple 4TB drives and start the upgrade process. Part of that decision came from Googling the NFS mount commands last night and finding a lot of posts about how fragile these mounts can be. I am all for reducing complexity so it seems "all on one box" makes more sense. Thanks again for your help and patience with me.
  21. root@Tower:~# mount tower2:/mnt/Movies2 /mnt/Movies2 mount.nfs: access denied by server while mounting tower2:/mnt/Movies2 root@Tower:~# export: yes, security: public on Share tower2/Movies2 I turned NFS off on Tower. Turned it back onj, still same error.
  22. NFS was OFF on both machines. Have turned it on for the respective shares. Should setting "Export:" be Yes or No for NFS? I see SMB is set to Yes. Both machine/shares are set to Public. I have no users other than me on the internal network. All shares/disks on both machines are Public.
  23. thanks for the help. I have enabled cache, moved the folder/files for the share to cache disk and it now it shows "red" (thought that was bad at first lol). Restarted Plex and it seems to be okay.
  24. actually it is corrected for capitalization, I get to this new error root@Tower:~# mount tower2:/mnt/Movies2 /mnt/Movies2 mount.nfs: requested NFS version or transport protocol is not supported root@Tower:~#
  25. root@Tower:~# mkdir /mnt/Movies2 mkdir: cannot create directory ?Çÿ/mnt/Movies2?ÇÖ: File exists root@Tower:~# mount TOWER2:/Movies2 mnt/Movies2 mount.nfs: unrecognized mount point mnt/Movies2 root@Tower:~# same message using IP as well