visuel

Was this on an already existing (5,2) xpenology VM, or did you create a new VM?

My Baremetal N40L working fine after upgrade from 5.2. Thanx very much for that!!! What to do best now for my N54L (AMD) with ESXi? Will loader v1.0 work?

Nope: Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:4890 Start of the updater... Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:4994 This is X86 platform Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:5008 The SynoBoot partitions exist. Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:2378 orgBuildNumber = 4418, newBuildNumber=4458 Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:2466 [CheckPackageSize] Find [1] internal volume, external volume count= [0] Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:2483 CheckPackageSize, err=0 Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:3128 SYNORedBootUpdCheck

2014/03/08 09:29:15 Install open-vm-tools 9.4.0-1280544-50 successfully 2014/03/08 09:29:15 Start open-vm-tools: start 9.4.0-1280544-50 successfully Thanx!

What do you mean with That's fine?

Running today's gnoboot-alpha-zImage with rd.v5.gz on ESXI 5.5 HP N40L --------------------------------------------------------------------------------------- After trying gnoboot-alpha-zImage of your google-drive every 2 seconds in log: -------------------------------------------------------------------------------------------------- Mar 7 11:30:41 SYNOLOGY5 scemd: SmartDataRead(101) open device /dev/sda fail Mar 7 11:30:41 SYNOLOGY5 scemd: disk_temperature_get.c:71 read value /dev/sda fail Mar 7 11:30:41 SYNOLOGY5 scemd: SmartDataRead(107) read value /dev/sdc fail Mar 7 11:30:

Can gnoboot-openvmtools-v4 be used with DSM 5 4418 update 1? If so, where to download? Running DSM 5 4418 update on ESXI 5.5 on HP40L with gnoboot-alpha5. My XPEnology now writes 2x faster than real QNAP 410p+. No issues Would it make sense to try alpha10?

Hi I created a VM with your boot-disk. Thanks for that. The VM boots, but can not be found by synology assitant. Can you give me the root password so I can login and see what is wrong.

Just thinking: I suppose that you have SMART option enabled in BIOS... After changing the Compatibility mode of the RDM-disks from virtual to physical I get the SMART information:

I had to wait for a few replication jobs but after restarting the VM still no SMART on my devices. Can't remember what "smartctl -a /dev/sdc" says about Vendor, Product, Revision (VMware, Virtual Disk, 1.0 or something else) but it does not work.

And you were .. right! [spoiler=smartclt -a output]syn> smartctl -a /dev/sdb .. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 228 197 021 Pre-fail Always - 3575 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 9 5 Reallocated_Sector_Ct 0x0033 20