dead2me

Has anyone else experienced an issue getting the Serial to load and display? Mine works fine in a VM, but refuses to work in a physical box with DSM6. I have tried multiple Serials as well as different configurations in the syslinux.cfg but none result in the system displaying the serial in the Info Center. VID and PID values are correct in the config as well.

Has anyone had success with HP N54L and the AMD CPU? What error gives with build volume? Are you trying to build the volume as EXT4 or BTRFS? I have not seen BTRFS work yet in either a VM or a physical using DSM6. EXT4 works fine.

One I built with DSM6 decided to lose its' mind on me last week and could not be reached on any service port. I followed this basic process though I performed a full install of Ubuntu onto a thumb drive and installed the requisite drivers and LVM etc.. and was able to copy all of my data off to an external drive. It loaded the raid partition as a single volume and let me "see" all directories and shares. https://www.synology.com/en-us/knowledg ... using_a_PC I don't know precisely what happened, but after enabling Jumbo Frames and changing DNS on the box, it said F to the U, and no longer wanted to play nicely. After my data was recovered I just flattened the drives and started from scratch. I did find within the logs via reading them with Ubuntu that a particular file refused to load, but it was in usr\lib and even with it mounted in Windows using Paragon Software's EXT piece I was unable to rename or replace the file with the previous version, so I threw in the towel and smoked it. You might be able to locate the proper password repository on the box if you are feeling frisky.

Synology DSM has a default telnet password, and you can find generators online. It's unique each day per code that's part of the OS, so as long as you have telnet responding on the device, you can log in as root with the daily password. Here's one such site, and there are many others. https://wrgms.com/synologys-secret-telnet-password/

@hurlyhunk, you have to use ESXI 6.0 U2. It won't run on 6.0.... ask me how i know. Please review all posts as there is good usable info in this thread. I have it working in ESXI 6.0 U2. It would not operate until I upgraded from 6.0 to 6.0 U2.

So, the two I have done both like to wipe the USB drive after installing the .pat file. I just redo the thumb drive with the image again and it boots fine.

So, the two I have done both like to wipe the USB drive after installing the .pat file. I just redo the thumb drive with the image again and it boots fine.

I want to install it on virtualbox. I tried to boot from the Boot.vmdk. but it boots directly to run, can't choose install. It doesn't count down. You will need to edit the syslinux.cfg file in the VMDK to default to Install. Read a few pages back where Hostilian referenced the file and what to change.

Is this on hardware or as a VM? Try EXT4 vs BTRFS.

Thanks for the clarification. Very helpful.

Have not. Added an ISCSI Lun on a NAS via RDM but DSM doesn't want to see it properly, yet.... I have seen other articles on various sites about Passthrough when your Card is in IT mode. Might give it a look....

I must be missing something simple, but mine won't play nicely on hardware. I tried multiple versions of the boot.vmdk from the files within this thread, as well as trying the ISO method which refuses to use the .pat file from Synology. Using VMDK2Phys created the thumb drive, but the box just likes to keep rebooting. I am sure I will be told that something of value has been mentioned unlimited times about this, but so be it..

it's a good thing there's no limit, because you just said it again...

it's a good thing there's no limit, because you just said it again...

The Info Center data for your CPU is either simply hard-coded (to conform to the model used), or otherwise bogus. For instance, the Info Center tells me I have an INTEL Core i3-4130, with 2 cores, whereas 'more /proc/cpuinfo' correctly shows an i7 980X, with CPU 0 and CPU 1, each with 2 cores (exactly as I specified in the VM). Pretty much the same here. I gave it 4 cores of a Xeon and it shows two cores of an i3