ptmuldoon

Success!!! For anyone else, accessing with the username and password like this did the trick //xxx.xxx.xxx.xxx/MediaServer /mnt/MediaServer cifs username=nasuser,password=nasuserpassword,iocharset=utf8,uid=emby,gid=emby,file_mode=0770,dir_mode=0770,vers=3.0,_netdev,nofail

I'm not sure if this an issue with my Emby setup or Unraid share permissions. In Unraid, i have a shared called "Public" and that share is set for SMB Share also with Public Security. I can read and write to that share from my Windows machine just fine. I also run Emby in a Proxmox LXC container, and have my fstab set there to map to those shares like such. //192.168.XX.XX/Public /mnt/UnRaid cifs guest,uid=1000,gid=root,iocharset=utf8 0 0 In the Emby container and can successfully mount and read the drives with no issues. And I can also create a directory into /mnt/UnRaid from within my Emby LXC container as well. But in Emby, when I try to set a recording path for live tv, I am always told Emby Requires write access to the folder. Is there something I need to change in fstab or UnRaid settings?

I am new to Tdarr and just set it up as a docker in UnRaid, but keep getting an error when it attempts to transcode a file 2022-05-10T13:29:04.150Z Rn_pYtCKu:Node[MyInternalNode]:Worker[le3-Fni9L]:[4/5] Running plugin 2022-05-10T13:29:04.151Z Rn_pYtCKu:Node[MyInternalNode]:Worker[le3-Fni9L]:Error Error: Cannot find module '../methods/lib' 2022-05-10T13:29:04.151Z Require stack: 2022-05-10T13:29:04.151Z - /app/Tdarr_Node/assets/app/plugins/Community/Tdarr_Plugin_MC93_MigzImageRemoval_cOnQ4C8ERO.js As far as I know everything is setup correctly regarding the server and node. I added 1 Library (as a test) with 1 file in it. But when it runs, I get the above error. I also believe it is not related to any specify plugin as I first have the same above error on the reorder streams plugin as well. Then removed that plugin and still get the error. Has anyone seen this before or any ideas on where to troubleshoot?

I currently am running Proxmox with Unraid as a VM within my homelab setup. And my current MB is an AsRock E3C224D4I-14S which works fairly well. And I really like this MB in that has 2 onboard SAS connectors that I could configure into a JBOD in using with Unraid. But the only limitation about my current MB is the 32MB max RAM it supports. So I'm looking/planning for my next future build and hoping to find a very similar board, one with onboard SAS but supports 128MB or larger ram. Does anyone have any recommendations of any out there?

I am working to move my VM's and containers from Proxmox over to Unraid, mainly to make better use of docker. And I am trying to get a cards against humanity docker clone from here installed but get an out of memory error when the script runs? I did have this working as a VM in ubuntu server in proxmox, so pretty sure its not a memory issue. I do have 32GB of memory in the machine also. https://github.com/olback/cah and the error i get is: root@UnRaid:/mnt/appdata/cah# ./scripts/angular.sh ✔ Node version OK ./scripts/angular.sh: line 13: npm: command not found ./scripts/angular.sh: line 14: [: -lt: unary operator expected ✔ NPM version OK ✘ Not enough memory available!

No I do not. just the qcow2 file. I was originally on vmware esxi and have older backs up the vmdx vm's from there that i had used in moving them and converting for proxmox. So I may be able to get the Win10 machines going from those. But have not given that a try yet. In my older vmware backups, there is both the vmdk and the vmdk-flat files. The flat file is the larger xxGB file

Thanks for the help guys. I don't have access to the proxmox VM anymore, and only have the qcow2 file. And I don't think its as simple as just editing the xml and changing the disk to point that file? I did try that and get an unbootable disk error.

I am finally getting my system back up and running, and now trying to move a Windows10 VM from Proxmox over to Unraid. From what I remember (had an earlier system crash issue), I had converted the Proxmox image over to qcow2, and have that file. I'm just not sure what steps I need to take to use that file. Do I just copy that file over to the VM's folder location and then edit the xml to point to that file? I'm not even sure where to locate the xml file as I when I go to edit the VM, it opens up the parameters in the unraid GUI.

OK, Thanks I'm hoping nothing is wrong with the Parity Drive, but I just checked on it and its showing an Input/output error. It shows dd: error reading '/dev/sdb' : Input/output error 5429+1 records in 5429+1 records out It copied roughly 500GB of the 4TB drive. I don't think this is normal and should expect it to be copying over the full 4TB? The other 2 data disks went well. But unsure if the parity copy failed or not. If the Parity failed, I could possible attempt to recover my 3rd data disk, and then start the parity from scratch. But trying to work with what I have available.

Thank you for the instructions. I hope to report back sometime tomorrow or next day with some success. But a question I'm hoping someone can confirm. Can you actually mount the parity disk outside of the array? For my first 2 data disks that I was able to recover after a bios chip swap on the hard drive PCB boards. I have confirmed I could see the drive in the motherboard bios, and then also successfully mounted the drive in unraid (command line) to see its data. Then unmounted that drive and copied the data over new HDs. For the parity drive, the motherboard also sees the drive. But in unraid, when I try to mount it I get get an error of: "mount (2) system call failed: Structure needs cleaning" And I think/hope that is normal since the parity drive does not actually have any data on it? I am going to start the dd process now to copy the parity to a new identical size drive. And then hope to get the rebuild with above instructions completed tomorrow.

So i'm getting closer here and could possible use some instruction on getting back up and running. To summarize, I originally had a 1 Parity, 3 Data drive setup, all with 4TB drives. In my server crash, I have been able to recover and copy the data of 2 data drives on to new 4TB drives. I expect to get my parity drive running later this week and then copied over to a new 4TB drive. So I will be placing all new drives in the server with clones of the parity and 2 data drives. And then plan is to rebuild the 3rd data drive. Is there specific instructions needed in making a new config and the invalid slot command?

Just want to report back on this as I slowly work to recover my data. I received a matching PCB board for my hard drive; same Model # and firmware. Doing a pure swap of the PCB board did get the HD to power up but could not read the drive. I then was able to find someone locally to swap the bios chip on the PCB board of the old one onto the new one. SUCCESS in that I could now read the drive and I am currently dd copying the data off to a new HD. Its a 4TB drive, and guessing the copy will take roughly 8 to 10 hours or more. I need to do this 3 more times (at least 1 more data and the parity) for my other HD's so now deciding if I want to wait it out for the other PCB boards to arrive (possibly 30 days) that shipped internationally. Or possibly use this working PCB board and and continue to swap the Bios Chip from the next HD onto the working board. I would prefer to wait, but I know the other PCB boards were not a 100% identical match either. So baby step progress, and hoping to get everything recovered in a few more days or weeks. Fortunately everything is mainly movies, tv shows and media, and no critical data that I need immediately. And I guess one possible question. I believe the parity drive is not actually a formatted drive correct? So will dd copying the parity to a new drive be the same process as copying a data drive?

@johnnie.black Thanks for getting back to me and I will let you know how it goes hopefully in a few days when the PCB boards arrive. As I look into some of the options in copying the data and seeing the progress, any recommendations for using dd and the block speed? I was reading also that pv is helpful in watching the status? Does unraid have pv installed and do either the below seem ok? I have 32GB of Ram in the MB to work with. Below assumes sdb is the old drive and sdc is the new drives to copy to. dd if=/dev/sdb of=/dev/sdc bs=100M status=progress dd if=/dev/sdb bs=100M | pv | dd of=/dev/sdc

Ok, so this is a hypothetical question as I read up more on PCB boards and my potential options. I believe 1 of the PCB boards I have coming is an exact match and will work without the need for a Bios Swap on the PCB. And that PCB board will match 3 of the my 4 drives, matching the Parity drive and 2 data drives. Would this work.... If I were to dd clone the Parity and the 2 data drives to new Western Digital Drives. And then attempt to start the array, would it be able to rebuild the 4th drive? The 3 drives would have new model numbers, but in theory they would be identical?

I am dealing with possibly my worse fear, which is a complete loss of all on my UnRaid data with no backup available. Potential loss of about 10TB of mostly movies and and tv shows. This is my own doing, and not Unraid's fault, but still keeping some small hope on recovering my data. Remember. Unraid is great, but when physical damage to HDDs occur, you could be screwed without an actual separate backup which i will plan for going forward. So... to explain In downgrading my server to a smaller case, what was suppose to be a hotswappable 5 bay cage was not what it appeared. This is/was a new build MB server, CPU, and I used the RAM from my older pc. When I added in one of the drives to the bay with the power on, there was a power surge that appears to have burned out the PCB boards on all 4 of my HDDS. None of these HDDs will power on. I have tried connecting these 4 HDDs direct to the MB with no luck, and can not feel any vibration from them when powering them. Other HDD's in the home do power up on the MB. Ironically, the MB and everything else seems ok. Unraid and USB devices all seem to work. I should have just turned the machine off first! So, in researching the PCB, i have ordered matching PCB's from these 4 HDDs. I think I may need to find someone locally to swap the BIOS chips on the PCB's from the original ones to the replacement ones. A lot of info seems to indicate that swapping the BIOS on the PCB is also necessary. Assuming I can get these HDD's alive and the data is OK on them, I plan to then transition the data off 1 drive at a time to new HDDs. The Unraid setup on the 4 HDDS were 1 parity; 3 data drives. So what would be the best way to possibly move the data from each old HDD to a new one? The easiest would be try and get all 4 drives going again in Unraid, and then swap them out one at time and let it rebuild. But i'm not sure if that will be possibly or not. But if I do get the drive's going, what would be best method to attempt to read and copy them to new HDDs. As a note. the current dead HDD's are Seagate 4TBs. And I am planning to use WD drives going forward. Nothing against Seagate, but going to go with a different manufacturer on the new HDs. I am still about 7 to 10 days away waiting on the replacement PCB boards. And can report back also on how things work out. But if anyone has any tips or advice it would be very helpful. Thanks, PT