altas
-
Posts
161 -
Joined
-
Last visited
Posts posted by altas
-
-
21 hours ago, pocopico said:
With the kind assistance of @buggy25200 and @yanjun i was able to create the required files and updated the loader for DS3622xs+ 7.01 u2.
is this already in the loader visible 7.01 u2 ??
-
i only re-created the Loader.. the DS3622XS installation was the same
-
shutdown is now working on DS3622XS+ on HP GEN8 Micro
-
I will do later a test
So loader need to be recreated, right? -
saddley the 3617xs will not workg on my HPGEN8 Micro, same as for some others.
thats why i look forward for your ACPI Fix for the DS3622XS- 1
-
-
same to me.. but i would say there is miss somthing in the update process, maybe a synoboot partition is gone or corrupt.
-
so long you have a version that is working why not Productiv.. never touch a running system so never try Update DSM.
-
same as usual... use the broadwellnk-7.0.1-42218
error ??
-
SynologyNAS login: [ 124.241961] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 124.394974] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 124.442649] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 124.495216] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 124.593152] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 169.797817] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 169.887183] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 229.989726] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 230.081895] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 230.265004] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 230.332759] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 230.385358] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 230.573577] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 230.637467] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 230.675400] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 279.714133] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 279.800995] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 296.101481] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 296.196747] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 339.905760] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 339.944086] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 356.294697] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 356.333374] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 388.822489] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 388.912093] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 436.468565] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 436.554132] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 448.999431] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 449.038142] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 496.660067] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 496.698494] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop [ 496.784944] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 496.879306] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 497.062403] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 497.130310] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 497.182796] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 497.250593] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 497.303221] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 497.370990] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 504.881419] ext2: synoboot2 mounted, process=updater [ 504.907038] vfat: synoboot2 mounted, process=updater [ 504.963077] synoboot2 unmounted, process=updater [ 504.997788] ext2: synoboot2 mounted, process=updater [ 505.023036] vfat: synoboot2 mounted, process=updater [ 505.079066] synoboot2 unmounted, process=updater [ 505.113789] ext2: synoboot2 mounted, process=updater [ 505.139415] vfat: synoboot2 mounted, process=updater [ 505.195816] synoboot2 unmounted, process=updater [ 505.230792] ext2: synoboot2 mounted, process=updater [ 505.256414] vfat: synoboot2 mounted, process=updater [ 510.712079] synoboot2 unmounted, process=updater [ 515.746145] ext2: synoboot2 mounted, process=updater [ 515.771893] vfat: synoboot2 mounted, process=updater [ 516.309141] synoboot2 unmounted, process=updater [ 516.351024] ext2: synoboot1 mounted, process=updater [ 516.376780] vfat: synoboot1 mounted, process=updater [ 516.441321] synoboot1 unmounted, process=updater [ 517.857360] <redpill/intercept_execve.c:82> Blocked ./H2OFFT-Lx64 from running [ 517.891909] Module [phy_alloc] is removed. [ 552.155601] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 552.247626] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) The system is going down NOW! Sent SIGTERM to all processes [ 553.401802] md: md0 in immediate safe mode [ 553.401806] md: md1 in immediate safe mode Sent SIGKILL to[ 553.440316] Module [usb_storage] is removed. all processes [ 553.461172] usbcore: deregistering interface driver usb-storage rmmod usb_storage Requesting system reboot [ 558.511884] <redpill/usb_boot_shim.c:98> Previously shimmed boot device gone away [ 558.547602] <redpill/override_symbol.c:250> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 558.603538] <redpill/override_symbol.c:250> Writing original code to <ffffffffa052e430> [ 558.641924] <redpill/override_symbol.c:250> Released lock for <ffffffffa052e430> [ 558.677601] <redpill/override_symbol.c:221> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 558.733769] <redpill/override_symbol.c:221> Writing trampoline code to <ffffffffa052e430> [ 558.772864] <redpill/override_symbol.c:221> Released lock for <ffffffffa052e430> [ 558.808172] <redpill/bios_hwcap_shim.c:66> proxying GetHwCapability(id=8)->support => real=0 [org_fout=0, ovs_fout=0] [ 558.858996] <redpill/override_symbol.c:250> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 558.915627] <redpill/override_symbol.c:250> Writing original code to <ffffffffa052e430> [ 558.953880] <redpill/override_symbol.c:250> Released lock for <ffffffffa052e430> [ 558.989236] <redpill/override_symbol.c:221> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 559.045347] <redpill/override_symbol.c:221> Writing trampoline code to <ffffffffa052e430> [ 559.083725] <redpill/override_symbol.c:221> Released lock for <ffffffffa052e430> [ 559.119358] <redpill/bios_hwcap_shim.c:66> proxying GetHwCapability(id=8)->support => real=0 [org_fout=0, ovs_fout=0] [ 559.170064] <redpill/override_symbol.c:250> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 559.225983] <redpill/override_symbol.c:250> Writing original code to <ffffffffa052e430> [ 559.264414] <redpill/override_symbol.c:250> Released lock for <ffffffffa052e430> [ 559.299473] <redpill/override_symbol.c:221> Obtaining lock for <GetHwCapability+0x0/0x100 [broadwellnk_synobios]/fffff fffa052e430> [ 559.355553] <redpill/override_symbol.c:221> Writing trampoline code to <ffffffffa052e430> [ 559.394677] <redpill/override_symbol.c:221> Released lock for <ffffffffa052e430> [ 559.430073] <redpill/bios_hwcap_shim.c:66> proxying GetHwCapability(id=8)->support => real=0 [org_fout=0, ovs_fout=0] [ 559.481198] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 559.513587] sd 0:0:0:0: [sda] Stopping disk
this is the Log after first Boot from USB Stick and upload the .pat File.
-
i play now with DS3622xs on GEn8... so far good but DSM Reboot/shutdown is broken
-
@Aigor did you try the update to 7.0.1-42218-2 ??
-
Update from syno website should work for the little updates, but bigger changes in dsm is not recommended to do without to be sure that the loader support it
-
-
which critical error and which fix?
The HDD incompatibility error- 1
-
Thx for the infos about critical error fix
Done and error gone -
Reboot from DSM not possible, looks like same as after the pat installation.
What i have to configure to get serial?!? -
Same to me
No manually Reboot, did hard reset
Current my 4TB HDD show me critial
Not verified Storage- 1
-
Test Done => Result successfully
Baremetal HP Gen8 Micro with DS3622xs
Networkcard => onboard
OnBoard HDD Controller- 1
-
Sure, when the kids sleeping
-
Can you add it to tynloader??
-
So then more info what network card you use is required
Or fix the IP with the MAC Address in DHCP
As you know the mac -
Correct
You have to search with find.Synology.com the NAS or on the DHCP Server if there is a new IP.
As the Console did not get you any additional infos- 1
-
TinyCore RedPill Loader (TCRP)
in Loaders
Posted
I can confirm that
Same to me empty 4TB storage
It reconised correctly in DSM