JimPhreak

Members
  • Posts

    723
  • Joined

  • Last visited

Everything posted by JimPhreak

  1. So last night one of my disks reported a bunch of read/write errors and UnRAID disabled the disk and currently my array is unprotected. Is there any recommended procedure for confirming the disk is bad before I replace it? Syslog of the errors is here: Jan 29 23:57:15 SPE-UNRAID kernel: sd 2:0:5:0: [sdj] Synchronizing SCSI cache Jan 29 23:57:15 SPE-UNRAID kernel: sd 2:0:5:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Jan 29 23:57:15 SPE-UNRAID kernel: scsi 2:0:5:0: [sdj] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Jan 29 23:57:15 SPE-UNRAID kernel: scsi 2:0:5:0: [sdj] CDB: opcode=0x88 88 00 00 00 00 01 13 dc 8b 10 00 00 02 00 00 00 Jan 29 23:57:15 SPE-UNRAID kernel: blk_update_request: I/O error, dev sdj, sector 4628187920 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187856 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187864 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187872 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187880 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187888 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187896 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187904 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187912 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187920 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187928 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187936 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187944 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187952 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187960 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187968 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187976 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187984 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187992 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188000 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188008 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188016 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188024 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188032 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188040 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188048 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188056 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188064 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188072 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188080 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188088 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188096 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188104 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188112 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188120 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188128 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188136 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188144 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188152 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188160 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188168 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188176 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188184 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188192 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188200 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188208 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188216 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188224 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188232 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188240 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188248 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188256 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188264 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188272 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188280 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188288 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188296 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188304 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188312 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188320 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188328 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188336 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188344 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188352 Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188360 Jan 29 23:57:15 SPE-UNRAID kernel: mpt2sas0: removing handle(0x000f), sas_addr(0x5001e677b7db5fed) Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187856 Jan 29 23:57:22 SPE-UNRAID kernel: md: recovery thread woken up ... Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187864 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187872 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187880 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187888 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187896 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187904 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187912 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187920 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187928 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187936 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187944 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187952 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187960 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187968 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187976 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187984 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187992 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188000 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188008 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188016 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188024 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188032 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188040 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188048 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188056 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188064 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188072 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188080 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188088 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188096 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188104 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188112 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188120 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188128 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188136 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188144 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188152 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188160 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188168 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188176 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188184 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188192 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188200 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188208 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188216 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188224 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188232 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188240 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188248 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188256 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188264 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188272 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188280 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188288 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188296 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188304 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188312 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188320 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188328 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188336 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188344 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188352 Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188360 Jan 29 23:57:22 SPE-UNRAID kernel: write_file: write error 4 Jan 29 23:57:22 SPE-UNRAID kernel: md: could not write superblock from /boot/config/super.dat Jan 29 23:57:22 SPE-UNRAID kernel: md: recovery thread has nothing to resync
  2. Looks like it was a browser cache issue. I must have in the past logged into my main server from this computer even though it's on a completely different network. Once I cleared the cache and then launched the web app on the new server it launched the first time setup and I'm good to go.
  3. From what I've read you can have multiple Plex servers under the same username and manage them all from the same Plex Web account
  4. I decided it would just be easiest to setup a Plex docker on my backup server that's on a completely different network. However, upon setting up that docker and logging into the web app for the first time, it loaded all my libraries and settings from my main server instead and isn't letting me set up my new one. It's like it thinks I'm connected to Plex Web from plex.tv instead of being connected locally to the new server. Anyone have experience with this?
  5. Yes I realize that and I've done that multiple times. But the fact remains that I'd like to have a second Plex server accessing the same media that I can do testing with and take down as a I please without affecting my production server that often has 6-10 remote users streaming at a time.
  6. For test purposes. I'd like to have 2 Plex servers both with access to the same media libraries. That way I can upgrade the test one to the newest Plex Pass version and do some testing before I bring my "production" Plex server up to the latest version. I've had issues with Plex upgrades breaking Sync and other features that are a pain in the a$$ to explain to my users and I'd rather save myself the headache.
  7. Is it possible to setup 2 Plex servers on the same UnRAID server? Wondering if anyone has tried this.
  8. OK, I see. So all the script is doing is mapping drives for you. That doesn't really explain why you need mapped drives in the first place. Do you have some applications that can't browse the network? I don't need mapped drives, it's just a convenience thing because I browse to my shares multiple times a day.
  9. It's a very basic net share batch file. So it just looks like the following for each share: net use /del V: net use V: \\UNRAID\Videos
  10. That's what I was envisioning, thanks for that. Is there anyway to map in Windows the entire UnRAID server as opposed to each individual share? Like I can browse to my server by going to \\UNRAID which displays all my user and disk shares but I can't map UNRAID as a drive, only individual shares. Why do you want to map drives anyway? I always just use UNC paths. Mapped drives are a security risk. To answer your question you might be able to do something with smb-extra.conf but I will let you research that. I have a batch script that runs when I login to my windows profile. I realize using mapped drives is less secure but it's a lot more convenient then having to manually type in UNC paths every time. I created the batch file a while ago though so maybe it's time I update things. I can just create a shortcut to UNRAID on my desktop and get rid of the mapped drives.
  11. That's what I was envisioning, thanks for that. Is there anyway to map in Windows the entire UnRAID server as opposed to each individual share? Like I can browse to my server by going to \\UNRAID which displays all my user and disk shares but I can't map UNRAID as a drive, only individual shares.
  12. I currently have a "Videos" share that has a split level of 2. Inside that share I have the following two folders (as well as a few others): Movies, TV Shows. The original reason I did this was so that I could map a single share in Windows (Videos) and easily access every folder within. Now with the split level being 2 this keeps all my movie folder files together on the same disk. However the consequence of this it that it also puts an entire TV show (including ever season) on the same disk as well. This to me is a problem for 2 reasons: 1. Disks gets filled up disproportionately because new seasons will get added to a disk that is the most full or nearly full. 2. If I were to lose a disk I would lose entire series' instead of just a 1-2 seasons So the question is, should I create new shares (TV Shows & Movies) using different split levels and if so what's the best way to move all my current data to be spread evenly amongs my disks?
  13. I have the Samsung SM951 512GB AHCI version SSD in my server and i've tested that it does work in either the array or cache pool. However I currently have it sitting in my array excluded from all user shares until I figure out the best way to make sure of it.
  14. Lol just came back to edit my post. I found it but will have to wait till my server is not in use to create a new bridge. 5 people streaming right now...BASTARDS!! . Just do what I do to the wife.... powerdown -r Then just act surprised.... Haha, I feel bad cutting people off with no warning in the middle of movies/shows .
  15. Lol just came back to edit my post. I found it but will have to wait till my server is not in use to create a new bridge. 5 people streaming right now...BASTARDS!! .
  16. No problem, not to rub salt in the wound, but it'd probably have worked with any combination of those 3 Windows isos and virtio isos.... Well, I am rubbing salt in the wound.... Haha yea true. Now to figure out my networking bridge situation and how it's getting IPs in the 192.x.x.x subnet when my server is in the 10.x.x.x network. Coming from ESXi this KVM virtualization stuff is foreign to me.
  17. Grrrrrrrr...I had a feeling it was something stupid. I was only searching the root of E:\viostor\win7 but not any further. Once I selected x64 is worked with the 0.1.109.iso drivers. Thanks!
  18. I've tried 0.1.102, 0.1.109, and 0.1.112 drivers with 3 different Windows 7 Pro SP1 x64 ISOs and can't get storage to show up to allow installation. What am I missing?
  19. It's not related to bridge mode. The AP doesn't know where the controller is unless you have your DHCP server specifically set up to issue the controller address as an option in the lease. Normally you would use the UniFi discovery tool to find the AP and tell it the IP of the controller, but the UniFi dockers don't have the discovery tool as it is a separate app. To get the AP to show up in the controller so it can be adopted and provisioned, do the following: Determine the IP the AP was leased SSH to that IP Login as ubnt / ubnt mca-cli set-inform http://address:port/inform (where address is IP of controller and port is the port you are using for inform, default is 8080) Once you run the set inform command it should show in the controller. As soon as you click adopt you need to run the set inform command a second time on the AP. EDIT: Syntax correction Thanks so much dirty for these above instructions. Really came in handy to quickly move my AP off a controller I had setup in a Windows VM over to this new Docker.
  20. Just installed this plugin for the first time. Seems like a super useful plugin so thanks very much for creating it. I tried to do a dry run for the first time. Selected a specific TV show within my Videos share so the folder selected is Videos/TV/House. The folder is 210GB and I've selected 4 disks in my array to move the folder to. Each folder has over 2TB worth of free space however when I do a dry run it spits the following error: "There isn't available space in any of the target disks, to move the folders you selected. Check more disks in the TO column or go to the Settings page, to review the folders selected for moving or to change the amount of reserved space." Thoughts? EDIT: Stopping and starting the plugin seems to have fixed my issue.
  21. I've been having an issue over the past few months where every couple of weeks my Plex docker will appear to crash and it's unreachable until I restart the docker manually. It always happens when media is being streamed but I'm not always streaming the media myself so it's hard to determine if it's a specific type of file causing the issue. When it does crash, nothing shows up in the UnRAID syslog and also nothing shows up in the Plex Crash Reports directory (yes I check before restarting the Docker). With no logs to look at that I'm aware of I'm not sure what angle to hit this problem from. Has anyone else had any similar issues? It's not happening often enough to really be a pain but the fact that the server will stay down until I manually restart the docker is quite annoying.
  22. So I'm thinking hard about moving my virtualized UnRAID server on my ESXi box and going back to bare metal if I can get over the fact I'll lose VLAN support. I currently store all my ESXi VM's on a Samsung SM951 512GB M.2 drive attached to the motherboard and I run ESXi off a SATA DOM 16GB SSD. I'll be storing any VM's I use on my bare metal UnRAID server on my cache pool (4 x 480GB Intel 730s). Is there anything I could do to re-purpose my M.2 and SATA DOM drives in UnRAID or should I just sell them?
  23. I see. It's a shame because I was looking forward to moving to a bare metal instance of UnRAID and using VMs but I think I'll have to wait until that vlan support is available. Maybe I'll just play around with VMs on my backup server for now which has a c2558 in it and can probably support 1-2 VMs. I hear yah, but I think VLAN support may end up being only one of a few features that an IT professional needs. Snapshots and cloning are other big ones for a home lab, which are sooner on the roadmap than VLANs. Just trying to set good expectations. We will get there eventually... I think VLANs are pretty high on the priority list of all IT professionals who know networking but I understand that IT professionals as a whole isn't your market. You are more geared towards the home technology enthusiasts.
  24. I see. It's a shame because I was looking forward to moving to a bare metal instance of UnRAID and using VMs but I think I'll have to wait until that vlan support is available. Maybe I'll just play around with VMs on my backup server for now which has a c2558 in it and can probably support 1-2 VMs.