cr0nis

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by cr0nis

  1. Regarding disk 8. Some had said that it was never formatted correctly. I will do this tonight. Is there a specific format i should use since some of my drives are reiserfs while others are xfs. Ive always just used the UI and selected format Thanks again folks. This has really helped me
  2. Looks like drive 5 and 6 are now up. Is there any way to recover the missing data from drive 5 or am i out of luck?
  3. Here are the results Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Is my only option to rerun with -L?
  4. Looks like drive 5 is up with a large amount of data loss (mostly media). Drive 6 doesn't offer a solution after running the check and I believe drive 8 just needs a new formatting. What should I do with drive 6. Also, what actions should i take to prevent this. I have a UPS attached thinking this would prevent such issues when I lose power but this is the worst i have seen since I've been running unraid. Thanks again for the assistance tower-diagnostics-20191030-1341.zip
  5. I'm running the suggestion on disk 5. I am seeing a ton of this: init_source_bitmap: Bitmap 12295 (of 32768 bits) is wrong - mark all blocks [402882560 - 402915328] as used should i be concerned?
  6. Booted in maintenance mode. Scanned both drives. Also attempted to unmount and remount disk 8. All 3 drives are now showing "Unmountable: No file system". Attached are the latest diags. A data rebuild has started (I believe on drive 8). Thanks again for the help. I am lost when it comes to troubleshooting this. tower-diagnostics-20191028-1339.zip
  7. Thank you. I am trying those steps now.
  8. Hi All, It seems i had a recent shutdown and my UPS forced a system shutdown. I didn't think anything of it and turned the server back on when i realized it wasn't running. Today CouchPotato start having errors when trying to move files and when I looked in my main dashboard I see 3 drives with issues. Before attempting anything I wanted to reach out here first to see whats the bets steps to take to resolve the issues. I have attached my logs. The server has been running since it was turned off after the forced shutdown. Any help will be appreciated. Thanks in advance tower-diagnostics-20191028-0110.zip
  9. Thank you. My kid can watch Moana again
  10. i'm getting the same error: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2017-11-27 23:46:10.539697 [info] Host is running unRAID 2017-11-27 23:46:10.557085 [info] System information Linux f5df9d3bc073 4.9.30-unRAID #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017 x86_64 GNU/Linux 2017-11-27 23:46:10.575669 [info] PUID defined as '99' 2017-11-27 23:46:10.593671 [info] PGID defined as '100' 2017-11-27 23:46:10.661496 [warn] UMASK not defined (via -e UMASK), defaulting to '000' 2017-11-27 23:46:10.680412 [info] Permissions already set for volume mappings chown: cannot access '/etc/conf.d/emby-server': No such file or directory chown: cannot access '/usr/lib/emby-server': No such file or directory chown: cannot access '/usr/bin/emby-server': No such file or directory
  11. Hi All, Not sure if this is the right place so apologies in advance if not. I'm looking to run a 7 Days to Die server and wanted to see if this is possible without virtualization. I see the following dockers but don't really know how to pull them to get this to work: https://hub.docker.com/r/zobees/7daystodie/ https://hub.docker.com/r/didstopia/7dtd-server/~/dockerfile/ I have added the URL's to the template repository but they don't show. What are my next options? Thanks in advance.
  12. All of my drives were re-purposed out of external hdd enclosures which i used for a hdd swap before i built the unraid server. Everything was spare parts but based on the success of the server i think i just might built for purpose now so i can get decent Plex transcoding while keeping temps at bay. I ordered a WD Red 2tb drive to make it a straight forward swap & rebuild. With the high amount of writes its running 12-20 degrees C less than all other drives. The Mrs has given me the thumbs up tp begin replacing the other drives so hopefully that helps with my overall heat issue.
  13. Thanks for the thread. Looks like I'll but a 2tb for now and justr by a lerger one next time and do a cleaner swap of the parity. As for the cache drive. is this guy a gonner as well?
  14. is there a way to rebuild and swap the parity at the same time. my parity is set at 2tb and i might as well upgrade the size if i need to get a new drive. Am I stuck having to buy a 2tb replacement drive for now?
  15. Hi All, im now seeing the thumbs down on the cache drive. At this point what are my next steps. Do I need to replace the 2tb drive that is being emulated? should i replace the cache drive as well? Any guidance is appreciated. Thanks in advance.
  16. I thought you asked to add a drive to see if it causes any errors. I'll have to wait and get a new 2tb drive for replacement. Attached are the two screen shots
  17. My dashboard only shows an issue with the 1 drive. the only other drive i have available for testing is a 256 ssd. Would that work or is it too small? Thanks again for your help
  18. Thanks for the reply. i've attached the full zip. I just assumed that since the rebuild has hit the 35% mark that it was working ok. In the meantime let me see if i have another drive to swap it out with for now. tower-diagnostics-20160225-1916.zip
  19. Hi Everyone, I recently began having issues with on of the drives in my unraid setup. I currently have 5 data sata drives, 1 sata parity drive and an older ide cache drive. within the last 2 weeks i noted that my second drive is listed with the red x next to it. After reading many posts I've tried a few things Stop the array change the bad drive to not installed [restart array stop array change he disk to the disabled drive start array let the rebuild complete The rebuild gets to 20-25% and stops. I have also replaced the sata cable, moved the hdd off the motherboard and onto a pci sata card and still no luck. Any help you can provide would be appreciated Thanks in advance! syslog.txt ST2000DM001-9YN164_S1E0XTBM-20160225-1916.txt
  20. Thanks ofr the quick replies. I think this make some sense. Adding the new hardware or upgrading forced me to remap my drives and verify the settings. i may have turned on use cache for shares which may otherwise not have used it in the past causing the drive to fill up whilst downloading. i changed my download folder to not use cache and am running mover now. Do you think i'm on the right path here?
  21. Hi All, i hope i dont ramble too much i've been trying to figure this out and am a bit tired at this stage so bear with me I'm using a combination of a Windows 7 HTPC which runs sabnzb & Emby and an Unraid server which ran Sickbeard, Couchpotato and Headphones. Earlier this week i upgraded by cpu/motherboard for the Unraid server and also upgraded from 5.x to 6.x. After the upgrade I reinstalled Couchpotato, installed Sickrage in place of Sickbeard and Headphones (have not configured this one yet) through Docker. i tried following the same setup i had in the past which was: All usenet downloads were sent to the HTPC server which ran Sabnzb Incomplete files were saved to a local drive on the HTPC and when completed were moved to an old \\tower\cache\appdata\sabnzbd\downloads folder that was set up on the Unraid Cache drive from a dormant Sabnzb setup that was really never used. Couchpotato & Sickbeard would then scan the \\tower\cache\appdata\sabnzbd\downloads\ folder and move/rename the file to shared drives called Movies and the other TV Shows. All movies and shows would then be deleted from the \\tower\cache\appdata\sabnzbd\downloads without issue What I'm seeing now is the movies are saved to the same place by Sabnzb, the files are unpacking correctly to the download folder and they are copied to the movie/tv show folder just fine. Once this happens the deletion of the folder from the download directory fails with the following error: Worse off there are new folders being created on the cache drive. It looks like the Download, Movie and TV Show folders are created on the cache drive root. Download share: \\tower\Downloads\Complete\movies\Sin City (2005) Cache folder version: \\tower\cache\Downloads\Complete\movies\Sin City (2005) Here is the weird part; changes made to the Download share replicate to the Cache download folder but not vice versa. I checked to see if symbolic links exist but don't see any. I'm stumped here. I changed the download directory to a share and the same thing happens. So what am I asking: - What is causing the deleting of files from \\tower\cache\appdata\sabnzbd\downloads to fail - What is creating the copy/link of the 3 folders to the cache drive? Let me know what additional info you need as my log knowledge is pretty basic. thanks in advance!