Jump to content

LordRaven

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LordRaven

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Thanks Trurl. It is a Ryzen, so I'll see if this helps.
  2. Okay, fair enough. Is there a way to figure out what caused it to switch? Its a brand new USB only a few weeks out of the wrapper, and given I've had 3 go in the last month, I'm guessing its a config or some corruption in my setup. I'm hoping to figure out what's causing it so I don't have to rebuild my entire system from scratch as if I was setting up a brand new machine.
  3. Does anyone know if there's a way to switch a USB back to read/write in Unraid? I'm assuming I could try the other method via a Windows that I've seen online, however I know with my previous attempts it didn't work and I'm kind of not wanting to risk shutting down my server if it means it won't atleast limp by like its doing now.
  4. Yup, its definitely a USB2 flash drive in a USB2 port.
  5. Hi guys, I'm been having an issue with my Unraid for about a month, and not sure what could be causing it. I'll apologize now if this is a bit long winded or rambles a bit, but I thought I'd document everything since this is driving me nuts. The situation is that I keep having USBs go to read-only. The first one was the original USB and after 6 years, I figure had done its time. The next was probably my fault for using a USB3 rather than 2, and fair enough. This one however, is definitely a USB2 and nothing was going on out of the ordinary. I'm attaching a copy of the diagnostics which hopefully someone can see something I've been missing. The latest USB was completely brand new about two weeks old. I am on Unraid 6.8.3 and all my dockers and various other sub-systems are typically up-to-date. Hardware wise, the only changes from the original USB going kaput is put in some new fans to keep the system cooler and moved a Video card in so I could use a VM as my main machine. Current specs are: Motherboard: Gigabyte Technology Co., Ltd. B450 AORUS ELITE Bios: vF50 (one less than current since I coudn't get that to install properly.) Memory: 64Gb Log from the USB Drive is only: Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] 30548096 512-byte logical blocks: (15.6 GB/14.6 GiB) Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] Write Protect is off Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] No Caching mode page found Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jun 17 23:54:21 DataStore kernel: sda: sda1 Jun 17 23:54:21 DataStore kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jun 17 23:54:56 DataStore emhttpd: Verbatim_ToughMax_1317110000000623-0:0 (sda) 512 30548096 Jun 17 23:54:56 DataStore emhttpd: import flash device: sda Jun 24 05:07:02 DataStore kernel: FAT-fs (sda1): error, invalid access to FAT (entry 0x0f7ffff7) Jun 24 05:07:02 DataStore kernel: FAT-fs (sda1): Filesystem has been set read-only I haven't rebooted the machine yet to see if that makes a difference since in the previous cases it hadn't and I thought I'd leave it on in case anyone has an idea I need to check. This latest case came up overnight and nothing apparently out of the ordinary was going on. I had just finished using the machine earlier, went to bed, and in the morning, my phone notified me the USB flipped. datastore-diagnostics-20200624-0746.zip
  6. Hi, Just for anyone who has a similar issue to what I had. I had a disk being unmountable. Disk is a default format of xfs. After checking the disk, I found that it had a metadata corruption. The fix was in maintenance mode to run the xfs_repair with the -Lv option. The L is for force the zeroing of the log file on the disk. I know that the in the xfs_repair screen (https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#xfs_repairmention that it isn't one of the options we probably need, however this was the only way to fix my disk and allow it to be mountable again. Thanks, Raven
  7. Just wanted to throw this out as a solution if anyone has the same issue I had. I'd put in the Syncthing docker on my machine and using the bridge connection mapped 8080 in the docker to my towers 8082. Unfortunately, what happened was that the system was not able to connect to any of my other Syncthing instances on other devices no matter how much I put the ID's on the tower instance or on the remote instances. The issue turned out to be needing to have 8080 mapped from the docker to the tower instance. Once I did this, the mappings started coming through. I had not originally done this because I was running unmenu on port 8080. I had to edit the unmenu.conf file to change the port there and everything is now up.
  8. Checking on it later, it seems that when the system did an update with the latest pull from git hub, it changed the permissions on my directories back to read/execute rather than read/write/execute. This could be part of the reasons why I was having issues earlier.
  9. Regarding that, I think the screen you're talking about is the plex sign in screen. I'd guess that they'd be able to theoretically access your data if they signed in with an account. Probably the better option is to setup a VPN to your home network and access your data via that. I've done similar things in the past.
  10. Solved But a slightly different solution. It seems that the system was downloading okay which I had waited before, but the default directories were unwriteable. Changing them seems to have solved my issues.
  11. I've been trying to go via the WebUI. http://10.42.1.115:32400/web/index.html http://[[server Name]]:32400/web/index.html
  12. I have been trying to access via the local name and the ip address. I have tried launching from the docker as well, but no real luck.
  13. Okay, I thought that had to be done within the app similar to the plugin. I made the change and no real difference in terms of the UI.
  14. So far its a pretty vanilla setup, but here are the screenshots
  15. Hi, I'm trying to play with dockers a bit and have put in Plex and SickRage. Both seem to okay on the docker page, but when I try to go to the webpages, nothing is available and I'm told the page isn't available. I had also installed Apache earlier but removed it when experimenting with VirtualBox. I've tried it with the Network type tested as both Hosted and Bridged with no difference. Just as background in case it makes a difference, I had installed Plex previously but during my tests, I've tried disabling the plugin as well as uninstalling it. I've tried rebooting but again no change in anything. I've seen some other people with questions but I didn't see any responses, so if it has been answered, sorry about the repost. Thanks When needo's plex starts up, it downloads the updated plex application (which may take a bit depending upon what else is going on), and then it still takes a bit for plex to get itself up and running.