wtfcr0w

Well, I've tried almost everything I can think of. Every type of VM, every type of machine (Q35-X.X), every bios, multiple different bootloaders and OS install files. I cannot for the life of me get xpenology to run on this. I even tried on my mac in vmware and still had issues. Farthest I have gotten is installed the OS .pat file, but every time it reboots it says it needs to recover. Other times it says there was an exception. Other times it says the file is corrupt. If anyone has any knowledge on this whatsoever I would really appreciate it. I used to have xpenology running on proxmox before running unraid and it was so useful to me that I would really like it back just for a few features. I would appreciate any suggestions so much.

I'm sorry to wake a sleeping thread, but I've been working at this for three days now and one time I was able to get the 'diskstation' found on find.synology.com, or the DS Finder android app, but like others in this thread, when trying to upload the DSM_DS3617xs_23739.pat, after using the 1.03b boot image, with a machine type of q35-2.9 (nothing else ever worked) I received the same error saying the file was corrupted. In order for it to be found, or even get an IP on my network I needed to use SATA for both the primary and secondary disks in the VM. Then I tried the 1.04b image with intentions to use DSM_DS918+_25426.pat. I tried using the same settings, and swapped around the machine type a bunch, even tried writing the image to USB and booting the VM with that directly. I cannot for the life of me get this to work. If I need to post my settings I will do, but if anyone has any recommendations I would appreciate it so, so much.

I was not trying to rebuild. The parity drive was bad so I pulled it so I can have it replaced. This morning I forgot that I pulled the defective parity disk and went to wipe it, but since it is the same model/brand as another disk in my array I wiped a disk in my array by mistake. I wanted to try to wipe the parity before sending it back to the manufacturer. I simply wiped a 4TB disk in the array containing movies/TV in a 2 disk array by using fdisk/mkfs.ext4 etc... I do not have access to the files I want to keep because I have not attempted to restart the array as the disk that I wiped by mistake is showing as disabled and I do not want to lose any of my personal data I keep in the shares on the disk that is still in tact. I wanted to make sure I got any advice from the pros here before making any move. Thank you for any help. You have no idea how grateful I am. Diagnostics: io-diagnostics-20210925-1110.zip

Having a rough morning. Sorry if I leave any details out. My anxiety is through the roof. Yesterday I started having issues with unRAID, got a message from my mac saying one of my shares were full even though I had more than 4TB available. Checked unRAID and saw an error that the parity was disabled due to errors. Diagnosed it to be a bad drive (brand new 5 months ago), disconnected it and packed it for warranty replacement. This morning, I totally forgot I packed it (sleep depravation) and went to format the disk in unRAID. Well, I have a second disk that is the same model and it is part of the array which is only two disks. I formatted a disk that was part of the array. Rebooted and now it is showing the disk as disabled and I don't want to move unless I can get files I desperately need. I kept only shares for movies and TV on the one that I formatted, so I am not too worried about that. I am worried about my personal photos and files on the other disk that was not formatted, this disk had shares only for things like this. How should I go about, if at all possible, getting those files backed up? Can I just use the new config tool and add that one disk to the array and it will have the files? Or is there a better/safer way of doing this? I am very desperate to get these files back as they are files/photos over the last decade+ of my daughter being born, family, financial docs, etc... Thank you for any help.

Thanks. Ill get with them. I appreciate it.

I cant find the correct forum to post this issue in. It if needs to be moved to another forum please feel free to do so. I've been trying to get Almond Server running on docker in Unraid but I continuously receive the same errors in the logs. Here is the command I am running (obviously running from the Docker gui in Unraid: docker run -p 3000:3000 -v $HOME/.almond-server:/var/lib/almond-server stanfordoval/almond-server:latest-portable And here is the log output with the error I receive each time: Frontend initialized in development mode Failed to load translations: The expression evaluated to a falsy value: assert_1.default(fs.existsSync(modir)) Snowboy initialized Home directory not accessible: Permission denied Uncaught exception: Not available I know that docker might not know the location of $HOME in the variable shown in the command, so I have also tried '-v /root/.almond-server' and '-v /home/.almond-server'. I've also tried to set that variable to the /mnt/user/appdata/ location. Does anyone know why this might be happening and how I might be able to fix it?? Thank you for any assistance in advance.