Jump to content
XPEnology Community

visuel

Member
  • Posts

    11
  • Joined

  • Last visited

Everything posted by visuel

  1. visuel

    DSM 6.1.x Loader

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

    DSM 6.1.x Loader

    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?
  3. 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 SYNORedBootUpdCheckAndApply(3128): Skip bootloader update, no uboot_do_upd.sh exists Mar 11 20:48:05 SYNOLOGY5 updater: updater.c:340 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:1477 Kernel Version: 3.2.40 Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:1557 failed to get old BIOS version Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:5245 fail to upgrade BIOS Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:592 Restore [hda1.tgz] fail, remove it from synoboot Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:592 Restore [updater] fail, remove it from synoboot Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:592 Restore [VERSION] fail, remove it from synoboot Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:5454 fail to rollback flash (restore) Mar 11 20:48:11 SYNOLOGY5 updater: updater.c:5490 Failed to accomplish the update! (errno = 21)
  4. 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!
  5. 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:41 SYNOLOGY5 scemd: disk_temperature_get.c:71 read value /dev/sdc fail Mar 7 11:30:41 SYNOLOGY5 scemd: SmartDataRead(107) read value /dev/sdd fail Mar 7 11:30:41 SYNOLOGY5 scemd: disk_temperature_get.c:71 read value /dev/sdd fail Mar 7 11:30:41 SYNOLOGY5 scemd: SmartDataRead(107) read value /dev/sde fail Mar 7 11:30:41 SYNOLOGY5 scemd: disk_temperature_get.c:71 read value /dev/sde fail Mar 7 11:30:41 SYNOLOGY5 scemd: external/external_fan_table_type_disk_temperature_ops.c:230 Invalid Disks temperature -1 Mar 7 11:30:41 SYNOLOGY5 scemd: external/external_fan_config_table_lookup.c:148 Temperature Get fail When Trying to install open-vm-tools-bromolow-9.4.0-1280544.spk of your google-drive: --------------------------------------------------------------------------------------------------------- entry.cgi_SYNO.Core.Package.Installation[1].install[21988]: pkginstall.cpp:386 Failed to run preinst script for open-vm-tools When Trying to install kexec-tools-bromolow-2.0.5-1.spk of your google-drive: ----------------------------------------------------------------------------------------------- Install kexec-tools 2.0.5-1 successfully Start kexec-tools: start 2.0.5-1 failed
  6. 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?
  7. 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.
  8. 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:
  9. 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.
  10. 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 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 64 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 81 194 Temperature_Celsius 0x0022 115 111 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 .. Where vSynology's /dev/sdb is RDM disk running on ParaVirtualSCSI controller. Also "short-test" worked, didn't try full test though. I'll see where I can get further with that, ideally would be to hack on DS's GUI so that it fetches tempriture and SMART status .. I suppose you rebooted the SYNOLOGY? All I get so far (without reboot): SYNOLOGY> smartctl -a /dev/sdc smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.30] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Vendor: VMware Product: Virtual disk Revision: 1.0 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Logical block size: 512 bytes Device type: disk Local Time is: Wed Jan 29 22:07:32 2014 CET Device does not support SMART Error Counter logging not supported Device does not support Self Test logging
×
×
  • Create New...