Dvalin21

I do have another question. On the Diskid I've seen so many variants of this being posted and shared. What is the conversion from what to what to get the Diskid? If there is nothing exact, then what would be the closest thing to look at? Same thing with the Satamap? The satamap identify function seems to only work with onboard sata controllers and I have a perc h310 which it doesnt sees (unless something has changed all of a sudden). Either way Im thankful that I can install DSM on my device as I never could on 3617, 3615, and 918. Something with this has something to do with the system marking the drives as (null) Unsupported. I also noticed that after I install, DSM seems to change my hdd from gpt to mbr. I can understand the one of them as it needs to have a bootable, but all of them? Thanks

I appreciate the knowledge

Has anyone else experienced synology being installed directly to the hdd? I noticed it the other when I went to build again, reboot, expecting to use find.synology.com to locate it, but was able to still use the ip address to get to the login screen like it nothing happened. I would have figured it would show up as a migrate or something in the reinstall. I ended up reflashing the usb and tried again and got the same result. It wasn't until I formatted the hdd when I was able to do a fresh install. If you look at my previous post, you can see that it seems to install it to the my smallest hdd.

@IG-88 @pocopico Hey guys, quick question and I apologize if its already been answered. What configurations will cause for the system to say a hard drive does not reach the requirements to be used in the system? Ive also notice that if I want to start a fresh install (meaning wiping all the drives) some of them have been set to MBR vs GPT I originally formatted them in. Is this normal or is this an issue? I just rebuilt ds3622, since im already having to reinstall everything im taking the time out to see what would be the best configuration. I used 0F00 instead of 0A00 for diskid and now (although it detects all 4 hdd) it says none of them are in requirements and they show up as null. Every hdd is a good drive without any errors (all tested). Any help with this would be appreciated. Thanks.

I keep running into that after I try to build. You have to delete it every time. sudo ./rploader.sh rm -R home/tc/redpill-load/custom/extensions/thethorgroup.jg.boot-wait/thethorgroup.jg.boot-wait.json

I ran a fdisk -l and im getting a lot of zram partitions created. Is this right? Disk /dev/ram0: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 640 MiB, 671088640 bytes, 1310720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdf: 596.2 GiB, 640133946880 bytes, 1250261615 sectors Disk model: HD642JJ Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x18dbd415 Device Boot Start End Sectors Size Id Type /dev/sdf1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdf2 4982528 9176831 4194304 2G fd Linux raid autodetect Disk /dev/sdh: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: WD30EZRS-11J99B1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 7CDD0B2F-94F9-4DF4-AE76-D3DD01878F80 Device Start End Sectors Size Type /dev/sdh1 2048 4982527 4980480 2.4G Linux RAID /dev/sdh2 4982528 9176831 4194304 2G Linux RAID Disk /dev/sdi: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk model: HUA723030ALA640 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 41ECEF46-7A13-4E19-BE3C-924FC7E73D17 Device Start End Sectors Size Type /dev/sdi1 2048 4982527 4980480 2.4G Linux RAID /dev/sdi2 4982528 9176831 4194304 2G Linux RAID Disk /dev/sdg: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000DM008-2FR102 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x29bb22f8 Device Boot Start End Sectors Size Id Type /dev/sdg1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdg2 4982528 9176831 4194304 2G fd Linux raid autodetect Disk /dev/synoboot: 14.5 GiB, 15510536192 bytes, 30294016 sectors Disk model: USB Flash Drive Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf110ee87 Device Boot Start End Sectors Size Id Type /dev/synoboot1 * 2048 100351 98304 48M 83 Linux /dev/synoboot2 100352 253951 153600 75M 83 Linux /dev/synoboot3 253952 2097151 1843200 900M 83 Linux Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram0: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram2: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram3: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram4: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram5: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram6: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram7: 3 GiB, 3157262336 bytes, 770816 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 byte

Did you get yours to work? I've been using megaraid_sas for mine.

Just an FYI Acronis True Image is not supported on DSM 7.0.1, with that being said it removed the spk and now I have no way to access the backups I have on my drives. if anyone else has ran into this and can shed some light i would appreciate it. Thanks.

Has anyone who is using perc H310, can you share your satamap and diskid? I had to end of migrating my old system from the 6.2.3 to 7.0.1 from 3617 to 3622. Thanks in advance.

Last we check, this was more than a grub issue. I was getting this issue when trying to install ds3617xs. Switched to DS3622, didnt have a problem

You want to use broadwellnk I believe. You can verify by sudo ./reloader.sh and hit enter. It will show you Sent from my HD1925 using Tapatalk

What version of the img do you have? It's on 45 and above Sent from my HD1925 using Tapatalk

I can't remember, have you tried 3622? My build wouldn't work until I switched to it. And even then it was the default that worked first Sent from my HD1925 using Tapatalk

Have you tried the default, 58 0A00

Hey guys, I did a quick search on the GPU, kinda expensive. However I did find this link used and on sale for the moment. https://www.stomizef.com/product/portanyz-msi-nvidia-geforce-gtx-1650-super-4gb-gddr6-pci-express-3-0-graphics-card-black-gray/ use at your own risk. Just trying to pass on a good deal as I may be looking for myself at some point

That right there is the 10m dollar question. What is happening with the baremetal img that is or isn't happening with the vmdk image?

Nice catch!! lessons learned

Everyone having the 55% install error, take a look at this post

For those who are trying to get nvme seen try here

I would say try it, but it never worked for me when I was trying to install ds3617.

I didnt have that problem. Tinycore always found the ext for my lan (tg3)

Even so I would get the same thing. The only thing that finally worked for me was switching from 3617 to 3622.

I have the same server. You don't need to. I'm going to assume you have the h310 SAS. If so leave satamap and diskid at default. 58 and 0A00

I'm headed to church, but when I get out I'll try and help some more

The only thing different (besides the serial, Mac, and pid/vid, is I left the satamap and diskid at default. 58 for Sata and 0A00 for diskid. Sorry I don't remember, but what is your hardware setup?