sheppp

An alternative way to do this without changing the static IP address on your UnRaid server is to go into your eero app, go to "Settings", "Network Settings", "DHCP & NAT", and click on "Manual IP". You can then do the following: -Ensure that your "IP address prefix" matches that of your old server (example: if your previous router's IP was 192.168.1.1, you should use the "192.168.0.0" default prefix for this eero setting). -Set the "Subnet IP" to that which was on your previous router (example: if your previous router's IP was 192.168.1.1, the "Subnet IP" in this eero field would be 192.168.1.0) -Set the "Subnet Mask" to 255.255.255.0 (the eero app default will likely be 255.255.0.0, but don't use it or you won't be able to save the eero app's manual IP configuration) -Set the "Starting IP" to that which your old router started with, PLUS a number which is more than the total of number eero devices that you plan to use (router and satellites). This is because the eero devices will automatically be given IP addresses starting with xxx.xxx.x.1 - and increase from there. (ex: if you plan to use 5 eero devices, you should set this "Starting IP" value ABOVE xxx.xxx.x.5 - I would set it higher than that in case you want to add more eero devices later. To be on the safe side, I would start at xxx.xxx.x.20, or in this case, 192.168.1.20). -Set the "Ending IP" value to the same number as your previous router ended with (example: xxx.xxx.x.254 or in this case, 192.168.1.254) -Click "Save", then "Reboot" when prompted - and wait several minutes. After this, you will see that you will be able to locate your UnRaid server by typing its old static IP address into your web browser. BTW, after being in the chaotically inconsistent and problematic Netgear Orbi world for many years, I have found the eero environment much, much more user-friendly and reliable. The eero Pro 6e night is still very young, though ...

Thanks!! That worked. For those like me that don't work much in Linux and can't remember anything about what was previously "learned" about using it, I used Putty to telnet in and used the command: ' reiserfsck --rebuild-tree /dev/md10 ' to repair the file system on my 10th drive. I really appreciate the help from you (itimpi, johnnie.black, and Constructor)!

I attempted to do this via telnet/putty with the command, "reiserfsck --rebuild-tree /dev/sdq" (where "sdq" is the Unraid-assigned name of the drive), however, I received the message, "Failed to open the device '/dev/sdq'". What am I doing wrong? Thanks.

I ran the check and received this message: I have never run --rebuild-tree before. Does anybody have any suggestions re how to do/fix this? Thanks.

Thanks. I'll do that.

I have had my Unraid server for many years with no major issues. Today, I found that I cannot write to my the server from any of my Windows machines. I get a "Error 0x8000FFFF: Catastrophic failure" whenever I attempt to do so - with my cache drive turned off on my shares (I can write to the server when the cache drive is on, however, my cache drive is not moving data onto the shares. I could, however, move files from my cache drive to a share via Midnight Commander. I checked the syslog (see attached) and found the following: "Sep 15 12:38:25 UR1 kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 15518 does not match to the expected one 2 Sep 15 12:38:25 UR1 kernel: REISERFS error (device md10): vs-5150 search_by_key: invalid format found in block 903401453. Fsck? Sep 15 12:38:25 UR1 kernel: REISERFS (device md10): Remounting filesystem read-only Sep 15 12:38:25 UR1 kernel: REISERFS error (device md10): vs-2140 finish_unfinished: search_by_key returned -2" and "Sep 15 12:56:14 UR1 root: Fix Common Problems: Error: Unable to write to disk13 Sep 15 12:56:14 UR1 kernel: REISERFS error (device md14): reiserfs-2025 reiserfs_cache_bitmap_metadata: bitmap block 753664 is corrupted: first bit must be 1" I have rebooted the server and NONE of the disks are red-balled. If you have any ideas re how to possibly resolve this, I would greatly appreciate it. Thanks. ur1-syslog-20190916-0321.zip

You have to use ntfs-3g to write. I do it all the time. Unassigned devices works for this. I just formatted a drive in my Windows box with "plain" NTFS and transferred it to my UnRaid box. I then mounted it via the "Unassigned Devices" plugin as a non-array drive. After this, I mapped the /var/lib/mythtv/ location to the NTFS drive (in the MythTV docker/container) with no issues. For a non-Linux guy like me, it's fantastic because I don't have to mess with the Linux command line AND all of my recordings are easily accessible/playable/archivable via my Windows boxes.

I finally found out what my problem was re not being able to record from the on-screen guide - and it was on my end. For whatever reason I never created a "Directory" in the "Default" group within "Storage Directories". Once I did this, I had instant success. I'm really sorry for wasting your time on this. Hopefully, however, somebody else will benefit from my idiocy. Thanks again for all of your help. Sparkly, at the risk of increasing the size of your already exploded skull, you are back to being brilliant. Sorry that I every doubted you!

One of my MythTV problems has mysteriously cleared up with a simple reboot of my UnRaid box! I'm sorry that I didn't try that earlier. I now get livetv to transfer to my non-array drive. Thus, the only problem that I have left to resolve is why I cannot record via my onscreen guide. Again, live tv records with no problems AND I when I switch over to my other Ubuntu MythTV stand-alone box, I can record via the onscreen guide from it. I am utilizing Kodi on the same client computer (I merely change the IP in the Myth add-on), so I doubt that Kodi is the problem. Again, when I remote into the MythTV docker, I don't seen any recordings from the onscreen guide in any of the var/lib/mythtv sub-folders (the live tv recordings are there so I know that something is working). Thus, I don't think that it is a docker mapping problem. Regardless, here are my current MythTV docker mappings (the "disks/ST31000340AS_9QJ0MD34-part2" partition is my non-array drive): /home/mythtv /mnt/cache/.docker/myth/ /db /mnt/cache/.docker/myth/data/ /var/lib/mythtv /mnt/disks/ST31000340AS_9QJ0MD34-part2/myth/ Thanks in advance for any suggestions that you might have.

Password: Linux 4.0.4-unRAID. Last login: Mon Aug 31 20:04:50 -0700 2015 on /dev/pts/0. root@UR2:~# ls -lah /mnt total 0 drwxr-xr-x 21 root root 420 Aug 31 20:04 ./ drwxr-xr-x 18 root root 380 Aug 31 20:03 ../ drwxrwxrwx 4 nobody users 32 Aug 30 15:13 cache/ drwxrwxrwx 7 nobody users 168 Aug 20 22:23 disk1/ drwxrwxrwx 7 nobody users 168 Apr 13 2013 disk10/ drwxrwxrwx 7 nobody users 168 Mar 1 2014 disk11/ drwxrwxrwx 7 nobody users 168 Apr 11 2014 disk12/ drwxrwxrwx 7 nobody users 168 Nov 21 2014 disk13/ drwxrwxrwx 7 nobody users 168 Aug 21 15:03 disk14/ drwxrwxrwx 3 nobody users 21 Aug 30 21:57 disk15/ drwxrwxrwx 6 nobody users 144 Apr 6 2014 disk2/ drwxrwxrwx 7 nobody users 168 Apr 6 06:51 disk3/ drwxrwxrwx 7 nobody users 168 Sep 28 2013 disk4/ drwxrwxrwx 7 nobody users 168 Apr 6 2014 disk5/ drwxrwxrwx 7 nobody users 168 Aug 24 2013 disk6/ drwxrwxrwx 7 nobody users 168 Mar 10 2013 disk7/ drwxrwxrwx 7 nobody users 168 Sep 7 2013 disk8/ drwxrwxrwx 7 nobody users 168 Feb 22 2013 disk9/ drwxrwxrwx 3 root root 60 Aug 31 20:04 disks/ drwxrwxrwx 1 nobody users 32 Aug 30 21:57 user/ drwxrwxrwx 1 nobody users 168 Aug 30 21:57 user0/ root@UR2:~# The "disks" drive is my non-array drive that I mounted with "Unassigned Devices".

No problem. In the big scheme of things and life this whole virtual TV thing is pretty meaningless. Nonetheless, now that I'm into it this far, I'm determined to figure it out somehow. Many thanks for your valuable time and input.

Yes, I re-formatted it last night as XFS and re-mounted it via "Unassigned Devices" - but nothing changed. It shows up as a separate drive when I go into my UnRaid box via Windows too. Yet, when I map to it via the Myth docker (by clicking in the box and navigating to it vs. manually typing the text, so as to avoid transcription errors), nothing transfers into it (which, because of my OS guide recordings issue, would only be my livetv files).

Thanks CHBMB. I saw Saarg's TVHeadEnd docker post/thread, but it looked as if there were still some loose ends, so I decided not to mess with it. Besides, I was somewhat familiar with the Myth interface. Perhaps I'll have to re-consider - after I figure out Sparkly's "smooth talking beast" ways to buy me some more time at home ...

CHBMB, my guess is that Sparkly likely has several tents - in addition to a sizable alimony payment - that he could loan to you. My stand-alone Myth box points to a separate drive as well. Are you using TVHeadEnd in a VM or a docker?

Trurl: I'll post my latest mappings when I get home tonight PST (provided that I still have a home and family to go back to - after wasting my life away the past couple of days trying to figure this out). Thanks for the cmd line text - when it comes to Linux, I'm a bumbling idiot (which is partially why I originally wanted to format my non-array drive as NTFS because it simplifies things for me). Johnodon: Thanks much for your volume mappings. They give me something else to try. If all else fails, I'll probably have to place my recordings on the array as well (provided that I can get them to record properly) unless somebody comes up with a way to successfully point to a non-array drive. CHBMB: I'm using 6.0.1 (not any of the 6.1 RC versions). You are correct re suspecting a setting in Kodi (v15.1), however, I have Myth working fine via a separate Ubuntu box AND when I point back to it, I have no problems with recordings. BTW, I merely copied most of those settings into the docker version of Myth - although it's certainly possible that I screwed something up when I did it. Again, thanks much to all of you for taking your time to help me. It is appreciated more than you know!

Thanks for the suggestions. I changed the mappings - but, still am unable to get recordings from the on-screen guide to work. Again, the "livetv" is working - files ARE created in the /var/lib/mythtv/livetv/ folder when I watch tv (and show up in the corresponding mapped folder - so long as I'm not using the non-array drive). However, despite the fact that Kodi displays "recorded" tv programs (made via the on-screen guide) within Kodi (under "TV Recordings"), whenever I click on them I get nothing AND I can find no actual files/recordings within the mythtv docker (or any mapped location). I also re-formatted my non-array drive as XFS and remounted it using the "Unassigned Devices" plugin, but that didn't change anything. Nothing shows up in the drives folders/subfolders - including "livetv" recordings.

Here are my docker mappings: /home/mythtv - /mnt/cache/.docker/myth/ /db - /mnt/cache/.docker/myth/data/ /var/lib/mythtv - /mnt/cache/.docker/myth/ All of the mappings within the MythTV docker backend "Storage Group" directories are: /var/lib/mythtv/livetv/ /var/lib/mythtv/db_backups/ /var/lib/mythtv/videos/ /var/lib/mythtv/trailers/ /var/lib/mythtv/coverart/ /var/lib/mythtv/fanart/ /var/lib/mythtv/sceenshot/ /var/lib/mythtv/banners/ /var/lib/mythtv/recordings/

Thanks. I now have a couple of issues: 1. Although my DVR is recording live tv (and I can see the files in the docker's var/lib/mythtv/livetv folder), it is not recording tv shows when I "start recording" via the OS guide (I'm using Schedules Direct and Kodi). I changed all of my permissions for the mythtv folder in my docker to full control, however, it didn't make any difference. Any thoughts? 2. I was able to mount a non-array drive, however, when I map the var/lib/mythtv to it, the live tv files no longer show up inside of the livetv folder on the non-array drive (they are still inside of the docker folder). The drive is formatted with NTFS. Could this be the problem? Does it to be formatted with either ext4 or xfs to map successfully to it?

Great idea! Thanks!!

This MythTV docker is fantastic!! Thanks much. I don't want to spin up my array every time that I use the DVR. Is there a way to point to a recordings folder on a non-array drive? If so, how do you do it? Also, is XFS the optimal way to format a separate drive? If so, is there a simple way/command to format a drive as such - without adding it to the array?

Bummer! I was afraid of that ... thanks. In the future do you know of a simple way to format a drive as XFS without adding it to the array?

I have a 1TB drive that I would like to permanently remove from my array. There is nothing on it (I merely formatted it as an XFS drive in UnRaid). Is there a simple way to do this in UnRaid 6 - without replacing the drive?

Yesterday, I decided to re-check my "hosts" file in C:\Windows\System32\drivers\etc to make sure that my server's IP address and server name were there. I discovered that I had a different IP and no server name. When I corrected it, I was AMAZED at how fast my client machines can now access the files. All is well after 24 hours, too. Bottom line: previous posts by linixguygary and sideband samuri (see above) are SPOT ON when it came to fixing my latency problem - many thanks for detailed instructions and the reminder! Again, all I did was the following: -Change the permissions on the "hosts" file in C:\Windows\System32\drivers\etc so that I could edit and re-save the "hosts" file (right-click the file, go to properties, security tab, add my user name, and give it "full control" to make changes to this "hosts" file); -Right-click the "hosts" file and select "Open with", "Notepad"; -Add a line at the bottom of the "hosts" file that contains the server's IP address, then a space, then the name of the server (so long as you are running a simple setup). The line should look something like: 192.168.1.8 Tower (of course your IP address and server name will likely be different than this). -"Save" the file. Sorry if I insulted your intelligence by being so basic with these instructions. I realize that there are some really smart Linux people in this forum. But, I figure that there may be a couple like me that can barely figure out how to open the command prompt.

I upgraded too. At first, it seemed somewhat faster. The problem is, however, as Daveeee noted, the speed is "intermittent". Sometimes it works fine, however many times the green ribbon of death appears - despite the fact that I was just in the SAME folder moments earlier. Like tr0910, I would use UnRaid exclusively (and Tom might sell a few more licenses) if somebody on the UnRaid side can figure this out - and, I can guarantee that even if Windows is the culprit, that MS won't be spending any resources fixing it.

Daveeee, the problem you describe is mine too. It occurs on all of my client Windows machines when I access my UnRaid server. It is exactly the reason that I still use WHS 2011 for stuff that I access frequently. I don't have the sporadic latency with it. BTW, I'm not advocating going to WHS - it definitely has its flaws. I'm merely noting that there is something about how Windows talks to UnRaid that is problematic to more than just you. And, I doubt that we are alone.