mcdull

Hi, I was in the old 6.0.2 DSM but is now considering seriously to get the updated 6.1 because of the SMB bugs, etc. From older post, I know it is possible that I need to migrate to a new DSM instead of just upgrade to get it work properly. On the other hand, I have a very slow and big online backup task created by hyper backup. It told me 1 month to get everything to load it online and now the incremental backup working nicely. I would like to ask if I migrate to the new DSM, can I just resume the backup task, or if it will be removed and I need to recreate a new one? My environment is DSM 6.0.2 inside a ESXi 6.5 box with a passthrough 8 port SATA Card. Thanks.

May I know if it is possible to add support to an officially (Synology) unsupported DVB Tuner using the loader? On the other hand, there are supported tuner with the same chipset. So the driver should be available. Are there any hint in doing this? Thanks.

I just did everything again and set the boot drive to non-persistent before the first boot. It just did not work.

I just got it finally working and you have to put the VMDK and IMG file in the same datastore folder for it to work. I do see the 50MB drive now as a HDD in DSM and think I need to edit the grub file to hide it from there. But, don't know how to get the correct VID/PID For now, i only have 4 real disks so, no issue of having an extra drive in there. I am glad to see someone using the same setup as I do, and although I didn't get much respond when I faced the 50MB drive issue I solved it eventually by keep digging the web and trial n error. And I am here to provide a solution so you can save some time, and to make my 2 days of digging around more worthy! lol And I must say I don't like being asked to look up old post when I posted a question, but I do feel that it is more annoying if the same questions comes up every 4~5 pages. So please try your best to use the search function or take your time to read through the entire thread. I am confused. Do you mean that we still need to use a physical USB to boot from a VM environment to get rid of the 50MB hdd? In 5.2 age, I remembered I don't see this boot drive under DSM, yet I was booting from the vmdk directly. Could it be the rmmod / mod_del doesn't work in this loader? I am okay to leave this hdd in the system but it is annoying that it generate smart error once every few seconds.

Yes. DSM 6 supports SHR1 /2

I am using ESXi with image from OP. Is it possible to hide the /dev/sda from the Xpenology? My DSM is showing sda as an non-initialized disk and keep reporting smart error. Thanks

re BU again, I would like to disable it as well. And, I would also want to know if there are any alternative push service works for android. Thanks.

I had a SHR volume with 4 Drives. I never seen any of the disk idle. synodisk --get_idle /dev/sdd [/dev/sdd] idle 1 second Always 1 second.

doesnt work with the most recent synology 5.1 update?

go download winscp. initiate a connection to your synology box. You can use root as user, password is equal to your "admin" user under synology. Choose SCP protocol and you should be able to read the above structure. go /volume1 or 2 or 3 depends on your synology. Get your MOST important files first then others. The program works just like FTP.

I know it is a bit old. But I cannot found the solution, yet. I got the following error in system log:- pushservice_utils.c:386 GenerateDsToken Failed Failed to get ds token. I have no intention to abuse the Ds push service and I want to disable it completely in order not to generate message to pollute Synology server. Could it be done or is it part of the framework that cannot be changed? Thanks.

I dont think hibernation issue is caused by smart. The harddisk is actually controlled by ESXi instead of Synology even you used RDM. And there is no point to hibernate your synology when you are hosting it with ESXi. If you want your hdd to sleep, at least you should try a dedicated SATA adapter with passthrough.

what do you want to do with SMART under DSM (with RDM)? SMART has been always work under DSM with RDM, it was just that the DSM interface wont pull the SMART data. You can always obtain the smart detail with smartctl -a -d sat /dev/sdc. If you want notification, get smartd install optware. I just received an email of warning last month that one of my drive got high ATA command failure and noticed I got a bad SATA connection. So I have to switch the bay for temporary fix. It is not difficult to schedule short or long smart test with smartd as well. But now I changed my approach to passthrough the entire LSI controller and the smart status under DSM works like a charm. The email alert is attached for your info. ==================== This email was generated by the smartd daemon running on: host name: XXXXXXXX DNS domain: [unknown] NIS domain: (none) The following warning/error was logged by the smartd daemon: Device: /dev/sdf [sAT], ATA error count increased from 460 to 471 For details see host's SYSLOG (default: /var/log/messages). You can also use the smartctl utility for further investigation. No additional email messages about this problem will be sent.

My DSM was installed in ESXi (Gnoboot / 4458 update 2) and I am in this issue again. I experienced the same before but I cannot remembered how I got rid of it. My memory recalled it might be related to improper SN being use. Mine SN is now calculated with the v2 calculator in this forum and using kernel string to put it in. Can anyone please confirm if these are related? Or it is not sufficient to use kernel string where I must patch the vendor file to make it work? Now the machines is shutting down twice a day which is very annoying. Thanks..

In that case, can we declare xpenology project close?

Is this build for developers only? How can we contribute as a general user? Thanks.

Synology doesn't owe you anything & no one is forcing you to update. Just be glad that the previous version is working thanks to Gnoboot & Trantor. If you want a hassle free experience buy a real Synology! I own a real synology! duhh.. but i built one with more storage and bays, however if its going to be unsecured then thats a big problem. I am greatful, but knowing my data is at risk isnt cool, henceforth why i say fuck synology for releasing updates like microsoft every TUESDAY!.. You go fxxk synology if you lost your data on your real synology. Not the one you build.

350*1024 = 358400MB 12*60*60 = 43200s 8.3MB / s I dont see it is a very bad number in using USB port under VM

ESXi support only USB 2.0 on host device (SURE). it does support virtualized USB 3.0 on specific guest device via Vsphere client over ethernet. i.e. USB 3.0 on vsphere client connected to ESXi virtual machine. So it IS the limitation of ESXi 5.5

Thanks for your information, but I cannot get it to work, most likely that I was using Intel ICH SATA instead of your LSI. I'll just dump the .vmx file for you (fyi: the ISO-image belongs to the plpt boot loader which then boots a mapped USB-thumb-drive with gnoboot. I did this just for testing some stuff usually I go with the gnoboot vmdk approach). I also deleted my CPU-IDs from the config. The Virtual SCSI-HBA is the LSI SAS (see config for details), the Physical SAS-HBA is the LSI 9240-8i with stock ROM including Raid5-Support, although no Raids are defined. .encoding = "UTF-8" config.version = "8" virtualHW.version = "8" nvram = "DARK-NAS2.nvram" pciBridge0.present = "TRUE" svga.present = "TRUE" pciBridge4.present = "TRUE" pciBridge4.virtualDev = "pcieRootPort" pciBridge4.functions = "8" pciBridge5.present = "TRUE" pciBridge5.virtualDev = "pcieRootPort" pciBridge5.functions = "8" pciBridge6.present = "TRUE" pciBridge6.virtualDev = "pcieRootPort" pciBridge6.functions = "8" pciBridge7.present = "TRUE" pciBridge7.virtualDev = "pcieRootPort" pciBridge7.functions = "8" vmci0.present = "TRUE" hpet0.present = "TRUE" displayName = "DARK-NAS2" extendedConfigFile = "DARK-NAS2.vmxf" virtualHW.productCompatibility = "hosted" floppy0.present = "FALSE" numvcpus = "8" cpuid.coresPerSocket = "8" memSize = "4096" sched.cpu.units = "mhz" powerType.powerOff = "soft" powerType.suspend = "hard" powerType.reset = "soft" ethernet0.virtualDev = "e1000" ethernet0.networkName = "VM Network" ethernet0.addressType = "generated" ethernet0.present = "TRUE" guestOS = "ubuntu-64" toolScripts.afterPowerOn = "TRUE" toolScripts.afterResume = "TRUE" toolScripts.beforeSuspend = "TRUE" toolScripts.beforePowerOff = "TRUE" uuid.bios = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20" uuid.location = "56 4d a2 c8 42 80 fb 23-7a 78 f3 b3 38 ad d4 20" vc.uuid = "52 54 05 73 1b ad 11 cc-8e 2b cb d2 c3 37 a0 57" chipset.onlineStandby = "FALSE" sched.cpu.min = "0" sched.cpu.shares = "normal" sched.mem.min = "0" sched.mem.minSize = "0" sched.mem.shares = "normal" sched.swap.derivedName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/DARK-NAS2/DARK-NAS2-8686319e.vswp" replay.supported = "FALSE" replay.filename = "" pciBridge0.pciSlotNumber = "17" pciBridge4.pciSlotNumber = "21" pciBridge5.pciSlotNumber = "22" pciBridge6.pciSlotNumber = "23" pciBridge7.pciSlotNumber = "24" ethernet0.pciSlotNumber = "32" vmci0.pciSlotNumber = "33" ethernet0.generatedAddress = "00:0c:29:ad:d4:20" ethernet0.generatedAddressOffset = "0" vmci0.id = "950916128" hostCPUID.0 = "" hostCPUID.1 = "" hostCPUID.80000001 = "" guestCPUID.0 = "" guestCPUID.1 = "" guestCPUID.80000001 = "" userCPUID.0 = "" userCPUID.1 = "" userCPUID.80000001 = "" evcCompatibilityMode = "FALSE" vmotion.checkpointFBSize = "4194304" cleanShutdown = "FALSE" softPowerOff = "FALSE" tools.remindInstall = "TRUE" tools.syncTime = "FALSE" scsi0.virtualDev = "lsisas1068" scsi0.present = "TRUE" scsi0:0.deviceType = "scsi-hardDisk" scsi0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk00.vmdk" scsi0:0.mode = "independent-persistent" scsi0:0.present = "TRUE" scsi0:1.deviceType = "scsi-hardDisk" scsi0:1.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk01.vmdk" scsi0:1.mode = "independent-persistent" scsi0:1.present = "TRUE" scsi0:2.deviceType = "scsi-hardDisk" scsi0:2.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk02.vmdk" scsi0:2.mode = "independent-persistent" scsi0:2.present = "TRUE" scsi0:3.deviceType = "scsi-hardDisk" scsi0:3.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk03.vmdk" scsi0:3.mode = "independent-persistent" scsi0:3.present = "TRUE" scsi0:4.deviceType = "scsi-hardDisk" scsi0:4.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk04.vmdk" scsi0:4.mode = "independent-persistent" scsi0:4.present = "TRUE" scsi0:5.deviceType = "scsi-hardDisk" scsi0:5.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/RDM/SAS-Disk05.vmdk" scsi0:5.mode = "independent-persistent" scsi0:5.present = "TRUE" scsi0:0.redo = "" scsi0:1.redo = "" scsi0:2.redo = "" scsi0:3.redo = "" scsi0:4.redo = "" scsi0:5.redo = "" scsi0.pciSlotNumber = "160" scsi0.sasWWID = "50 05 05 68 42 80 fb 20" usb.present = "TRUE" ehci.present = "TRUE" usb.autoConnect.device0 = "path:1/0/1/1 version:2" usb.pciSlotNumber = "34" ehci.pciSlotNumber = "35" usb:1.speed = "2" usb:1.present = "TRUE" usb:1.deviceType = "hub" usb:1.port = "1" usb:1.parent = "-1" ide0:0.deviceType = "cdrom-image" ide0:0.fileName = "/vmfs/volumes/5352e725-811f3e01-62c9-0cc47a02033c/ISOs/plpbt.iso" ide0:0.present = "TRUE" usb:0.present = "TRUE" usb:0.deviceType = "hid" usb:0.port = "0" usb:0.parent = "-1" ide0:0.allowGuestConnectionControl = "TRUE" toolsInstallManager.updateCounter = "1" RDMP vmdk (used the -z switch when creating the RDMP) # Disk DescriptorFile version=1 encoding="UTF-8" CID=28a0f813 parentCID=ffffffff isNativeSnapshot="no" createType="vmfsPassthroughRawDeviceMap" # Extent description RW 7814037168 VMFSRDM "SAS-Disk00-rdmp.vmdk" # The Disk Data Base #DDB ddb.adapterType = "lsilogic" ddb.geometry.cylinders = "486401" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.longContentID = "323bbdda29c2ac0d5d1a90a828a0f813" ddb.toolsVersion = "0" ddb.uuid = "60 00 C2 9b e9 58 e5 17-a3 04 a0 93 23 fa 6f e8" ddb.virtualHWVersion = "10" bye, Darky

I'm using ESXi 5.5. I'm able to run and schedule SMART tests for the disks from the DSM web GUI. The disks' serial numbers also display within DSM. However, the temperature is shown as 0° C / 32° F what leads some nasty scemd.log entries every two seconds. My solution was just to delete scemd.log which prevents logging until the next reboot (or probably log rotation...). I also might just link scemd.log to /dev/null. bye, Darky I were only able to manual run smartctl under ssh. Could you please post your RDM setting and SCSI adaptor as well as SCSI address for our reference, please? Thanks.

Edit the file, change ethernetX.virtualDev value to "e1000". ethernet0.present = "TRUE" ethernet0.connectionType = "hostonly" ethernet0.virtualDev = "e1000" <---------- ethernet0.wakeOnPcktRcv = "FALSE" ethernet0.addressType = "generated" My next release will include more drivers, watch out for it later this week . Hi All, I am installing gnoboot-alpha-10.5 on a VMware Workstation 9. But i cannot seem to get the networking online. I found the setting (see above) and the daily root password to login (404-0f01) on the console, but vi (or another) text editor is missing... how do i proceed?? Tnx. This is the VMX file you need to edit under windows.

if it is a physical machine, you may need to change your BIOS setting to let it boot.

Yes, I am using MagicPro PCTV Dual under 5.0 update 2. It is however, I did not try it under 4.3 as the driver is firsly included in the 10.5 alpha build. Your DTV-01 should be compatible with build-in driver on DSM. Did you see any driver message upon inserting the DTV under dmesg?

what does it show on screen? It should start to boot if you select some item in the GRUB boot list.