singaplex

Members
  • Posts

    7
  • Joined

  • Last visited

singaplex's Achievements

Noob

Noob (1/14)

0

Reputation

  1. that was fast, thanks allot it seem to have been working.
  2. okay thank you for confirming, its running right now, I let you guys know about it.
  3. Currently I am freaking out, iIve been using unraid for less then 2 month and I had so many issue but now it seem to be more serious then ever. Everything was working fine until I attempt to delete a movie from my plex library. All my shares has disappeared so I restarted my array and everything went back online except for my disk 1 which says it unmoutable: no file system. I checked my log quickly and this error showed up May 11 20:24:47 Tower emhttpd: /mnt/disk1 mount error: No file system I found a forum post with a similar issue but not exactly the same, try to launch a repair which gave me that result: root@Tower:~# xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - block cache size set to 3062160 entries Phase 2 - using internal log - zero log... zero_log: head block 1150590 tail block 1149531 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. Right now I have no clue what to do and I don't want to lose my data, all my drives (4TB western digital red) are new (about 2 month old) Please can someone help me out here. tower-diagnostics-20180511-2030.zip
  4. Hi, I just had a big issue yesterday, my plex server had allot of issues and I did not understand why so I decided to shutdown the machine and restart it. When I shutdown the machine via the web panel, the panel crashed so I decided to run the command 'powerdown' directly from the server, it give the normal 90 seconds delay to shut down everything but nothing happen and I could not execute any other commands, after 15 minutes I decided to force the shutdown with the power button. When the machine came back online it ran a parity check automatically with ~5274 errors, this first fail experience really spooked me so I was wondering what happen, how can I prevent this to happen in the future, I've ran unraid for less then 2 months. The first attachments is the logs at the beginning of the parity check and the second is after the parity check was done. Thank You tower-diagnostics-20180506-0555.zip tower-diagnostics-20180506-1548.zip
  5. Alrite well now it's working, I think my cache from chrome was not letting me resolve it's for some reason, I am still confuse to why I had that issue, I've been playing with it for a few hours and just when I decide to post about it 5 minutes after it magically worked! Thanks anyway, I will definitely look for a better router or get a switch.
  6. yea indeed but that is not the issue I am having at the moment, I can't access my tower/ panel from external local source for example my current PC, I can only access it via my server.
  7. I apologize for my bad English in advance. I've recently been trying unraid on my server and I was very happy with it except that my router, for some reason limit my local data transfer to 10 MB/s so I decided to connect my PC directly to my server because I have 2 ethernet port. Everything works fine now, I am having 90 MB/s upload speed to my server which is plenty enough for me but now I cannot access tower/ anymore (I tried the IP also). I can access is from the server directly with the GUI mode but I can no longer access it from my Windows 10 machine but I am able to connect with putty to WinSCP (to transfer files) Does anyone has a clue why? I post a picture of my current unraid network settings. Hopefully someone can help me, cheers.