CiViCKiDD

I have the same issue on my "primary NAS." I got it working on my test system by changing the VT-d value (I forgot if I turned it on or off to get it working). It's not a selectable option on my current setup; it's disabled and listed as unsupported. I tried using the patched library files and reindexing but still no go. I'm toying with the idea of migrating from a DS918+ setup to a DS3622x setup (I read somewhere that that DSM OS has some differences and Photos is more reliable there). I would lose Intel Quicksync as a result so not sure how my circa-2015 i3 would handle transcoding as a result.

Awesome guide! I kept getting a "bad ports" message when I ran the satamap command and didn't really get any useful feedback from the community - and this is probably on me but I couldn't find much on how to deal with it in the forums when doing my research. I simply ignored it and manually identified how many onboard SATA ports and additional SATA ports I was using using satamap (for example, I have 5 visible onboard SATA ports and for some reason detected 6, and also said all 6 were bad; it detected my other SATA card just fine. I was about to destroy essentially my "production NAS" to put drives in a Synology DS220+, but I'm glad I backed up my important stuff and took the gamble lol. Now I can return the DS220+ I just bought as my dedicated photo backup solution (I'll probably pick up the refreshed model that's supposed to come out soon). Thanks again to all the devs that brought this to us!

I was using the DS918+ platform on Jun / DSM 6.x, and figured I would keep it simple and use the same DS918+ / apollolake platform (latest release) with DSM 7.x. I used the update / fullupgrade arguments up front, I'll use it again before retrying, are you saying I can just ignore the bad ports message, build the loader, and give migration a shot - or is there something special I need to do to use this patch? Thank you so much!

Thanks for the reply! I'm busy with work and family most of today, but hoping to try understand enough to tackle this again after hours tonight. A few ignorant questions on writing my own sataportmap: 1. Can I leverage anything from my working Jun / DSM 6.x install (either an existing sataportmap on the usb stick, or other information from storage manager?) 2. I have to get a better look but I think the reason satamap thinks I have 6 SATA ports is because I have an eSATA port on the back of my mobo. I definitely only have 5 internal SATA plugs. Do I just need to update the SataPortMap variable (and in my case I assume it would be SataPortMap=510 because I have 5 drives connected to the onboard SATA,and 1 drive connected to the secondary SATA card?)? When do I need to worry about the DiskIdxMap, sata_remap, and DiskSeqReverse variables? Closest I could find to a guide was this but I'm not sure I'm fully tracking the right way to do this:

I am also having a satamap issue trying to get tinycore set up to migrate my primary NAS. Here are my specs: ASRock H97M-ITX/ac motherboard, with 5 onboard SATA ports (I have another SATA card for a 6th drive) Intel i3 cpu 6x hdd's of varying sizes It works great with DSM 6.x using Jun's bootloader. I tested the migration process on my NUC - which went perfectly and runs great over a week later. Here is the error I am getting on my primary NAS: tc@box:~$ ./rploader.sh satamap now Found "00:1f.2 Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]" Detected 6 ports/5 drives. Bad ports: 6. Override # of ports or ENTER to accept <6> ^C tc@box:~$ I have tried enabling hotplug in the BIOS for each sata port, I've tried running this command with just one test drive and then again with all my primary drives connected, etc. I think I need to manually tackle this at this point but don't really understand how to generate the right information - help?

I am also having a satamap issue trying to get tinycore set up to migrate my primary NAS. Here are my specs: ASRock H97M-ITX/ac motherboard, with 5 onboard SATA ports (I have another SATA card for a 6th drive) Intel i3 cpu 6x hdd's of varying sizes It works great with DSM 6.x using Jun's bootloader. I tested the migration process on my NUC - which went perfectly and runs great over a week later. Here is the error I am getting on my primary NAS: tc@box:~$ ./rploader.sh satamap now Found "00:1f.2 Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]" Detected 6 ports/5 drives. Bad ports: 6. Override # of ports or ENTER to accept <6> ^C tc@box:~$ I have tried enabling hotplug in the BIOS for each sata port, I've tried running this command with just one test drive and then again with all my primary drives connected, etc. I think I need to manually tackle this at this point but don't really understand how to generate the right information - help?

Thanks, it’s been running since I posted it and will probably take a few hours. Is it common / normal to see checksum errors? Also - does the log identify what was repaired vs what couldn’t be?

I set up an Xpenology system a while back with their SHR solution and BTRFS, with six mostly mismatched-sized drives into one volume. So one drive is a parity drive. Every now and then I get checksum mismatch errors, which sucks because I built this primarily to have a robust and semi-reliable backup solution in parallel with a cloud backup solution. I'm on the latest DSM with Jun's loader. Googling has found no solutions - before I give up and plan my next move, any advice on things to look into? A few thoughts I have: -check hdd for bad sectors / issues (any bootable tools you guys recommend?) -check RAM for issues (Memtest86) While typing this I also realized I have not done "data scrubbing" in 4 months - is this something that can repair files that have been identified as having checksum errors?