Jump to content
XPEnology Community

gfacek2

Transition Member
  • Posts

    19
  • Joined

  • Last visited

Posts posted by gfacek2

  1. Ja, das war es vermutlich bei mir auch.
    Leider stehe jetzt dennoch vor dem Problem, dass ich nichts mehr schreiben kann. D.h. ich müsste entweder die 10-12 TB irgendwo auslagern, die Platten formatieren und alles neu aufbauen, oder ich bekomme das Volume wieder beschreibbar.

  2. Hallo,

     

    nach einem wilden Tag gestern, hänge ich an einem scheinbar schreibgeschützten Volume und komme nicht weiter.

     

    Kurz zur Vorgeschichte:

    Seit ein paar Tagen bekam ich öfters die Meldung "Abnormal Power Failure detected on drive...". Ich hatte das vor ein paar Monaten schon einmal war dann aber weg. Nun war es aber so, dass das Volume in Read-Only gegangen ist. Ich hatte zwar keine wirkliche Lösung gefunden, habe aber in mehreren Foren die Meldung immer im Zusammenhang mit dem Update auf 7.0.1 gelesen, auch bei original Synology Geräten. Oft wurde gesagt, dass es nach dem Update auf 7.1 weg war. Also habe ich meinen Mut zusammengenommen, und auf ARPL 1.1beta2 und DSM 7.1.1-42962 Update 3 aktualisiert. Leider wurde hierbei keine Migration angeboten, und meine ganze Konfiguration war weg. Naja...egal. Zumindest konnte ich wieder schreibend auf meine Daten zugreifen. Ich habe ja noch ein Backup. Nachdem ich das Backup zurückgespielt hatte, war allerdings das Volume wieder im Read-Only. Über den Speicher-Manager konnte ich zwar wieder Lese und Schreibzugriff aktivieren, welcher aber scheinbar nicht greift. Auch über SSH kann nicht nicht schreiben.

     

    Was läuft da falsch?

  3. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: RedPill  TinyCore V.0.4.6 DS918+ DSM 7.0.1-42218 U3

    - Loader version and model: RedPill  TinyCore V.04.6 DS918+ DSM-7.1.0-42661

    - Using custom extra.lzma: NO

    - Installation type: Baremetal on ASRock J5040-ITX

    - Additional comments: Use official Synology .pat file. But had to follow the instructions here to build a new boot stick with 7.1.0 Loader. Before that I was stuck in recovery loop. Also, in my case, my UPS connected via USB is showing fine in DSM.

    • Thanks 1
  4. I'm sorry...I thought I had entered the specs in my signature...but there is no signature :D

     

    I'm using a ASRock J5040-ITX and no additional components (exept for the 3 HDD)

    I was on 7.0.1 U3 with RedPill 0.4.6 DS918+ BareMetal ... no extra.

     

  5. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 7.0.1-42218 Update 2

    - Loader version and model: Tinycore-Redpill 0.4.6 - DS918+

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - ASRock J5040-ITX

    - Additional comments: Made a new Boot-Stick with updated Tinycore-Redpill 0.4.6 prior to Update (before I had Version 0.4.4), but I don't know, if this was needed.

  6. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.3-25426 Update 3 - Jun's 1.04b bootloader

    - Loader version and model: RedPill DS918+ v7.0.1-42218 update 2

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - ASROCK J5040-ITX

    - Additional comments: build image with UEFI support

  7. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.2-24922 Update 4

    - Loader version and model: JUN'S LOADER v1.04b - 918+

    - Using custom extra.lzma: No

    - Installation type: BAREMETAL - ASRock J5040-ITX

    - Additional comments: 2x Reboot required

  8. Thats right. I had a driver issue...
    You could check the BIOS. I think that there is an option in some BIOS to keep the PC always on. Also, I once had a customer PC with exactly this issue, whose motherboard was defective.

  9. - Outcome of the update: SUCCESSFUL

    - DSM version prior to update: DSM 6.2.1-23824U6

    - Loader version and model: Jun v1.04b - DS918+

    - Using custom extra.lzma: Testversion 0.7 from IG-88

    - Installation type: BAREMETAL - ASRock J4205-ITX with a Intel i210 NIC (OnBoard Realtek disabled)

    - Additional comments: I had to delete the /usr/lib/modules/update/* folder and also drm.ko, drm_kms_helper.ko and i915.ko

  10. 11 hours ago, IG-88 said:

    if you want to test it i can send you a link

     

    Sure, I can test this. Should I test something specific, or just, if it works for me?

     

    So, I replace the extra from real3x with your extra/extra2 like I did before and after a restart I update to the latest 6.2.2 via Update-Precedure of DSM?

  11. Sounds great. I will try the one from real3x first.

    <EDIT>It's working fine...many thanks!</EDIT>

     

    So, when you release your set, I can update to 6.2.2?

     

    Many thanks for your effort!

  12. I've got this here:

     

    [  192.282450] BUG: unable to handle kernel NULL pointer dereference at           (null)
    [  192.290303] IP: [<          (null)>]           (null)
    [  192.295352] PGD 69fb0067 PUD 6a899067 PMD 0
    [  192.299681] Oops: 0010 [#1] PREEMPT SMP
    [  192.303666] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel cdc_acm ppp_async aesni_intel ppp_generic slhc glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common uusu(OE) [last unloaded: apollolake_synobios]
    

     

  13. Hi,

     

    for me, the shutdown and reboot doesn't work. Right now, when I'm initiating the shutdown, I wait about 5 minutes and disconnect the power.

     

    my Specs are as followed:

    - DSM version prior update: DSM 6.2.1-23824 Update 6

    - Loader version and model: Jun v1.04b - DS918

    - Using custom extra.lzma: NO

    - Installation type: Baremetal - ASRock J4205-ITX

    - Additional comments: Disabled internal NIC to Intel I210-T1

     

    As I read multiple threads, where it was reported that after disabling the internal NIC, the startup and shutdown worked better, I gave it a try...but no luck for me.

     

    I thought, maybe I get more clues, when I get the output via serial comport. The last message is "kvm: exiting hardware virtualization". I think, it has something to do with how Jun got DSM working on non Synology Hardware.

     

    Here is the whole output I get after shutdown:

    The system is going down for power off NOW!
    [295447.135209] init: synonetd main process (5729) killed by TERM signal
    [295447.145979] init: synostoraged main process (9941) terminated with status 15
    [295447.155948] init: hotplugd main process (10750) killed by TERM signal
    [295447.166121] init: smbd main process (11030) killed by TERM signal
    System is going to poweroff.
    [295449.732602] init: pkg-WebStation-userdir main process (7587) terminated with status 1
    [295450.160273] init: synoscheduler-vmtouch main process (14043) killed by TERM signal
    [295450.679320] init: skip respawn pkg-webstation-php-844257d5-dd27-4885-8fd8-96cf320e39ac during shutdown
    [295450.959726] init: synoscheduler-vmtouch main process (7953) killed by TERM signal
    [295451.185987] init: pkg-synovncrelayd main process (17196) killed by TERM signal
    [295451.921139] init: synoscheduler-vmtouch main process (8042) killed by TERM signal
    [295452.597916] init: pkg-synohostcmdd main process (17159) killed by TERM signal
    [295452.836134] init: synoscheduler-vmtouch main process (8148) killed by TERM signal
    [295453.351309] init: pkg-synohostcommd main process (17105) killed by TERM signal
    [295453.634719] usbcore: deregistering interface driver snd-usb-hiface
    [295453.676241] usbcore: deregistering interface driver snd-usb-audio
    [295454.357243] init: pkg-AudioStation-pgbouncer main process (16193) terminated with status 1
    [295455.261301] init: pkg-WebStation-fcgiwrap main process (13537) killed by KILL signal
    [295455.366257] docker8744de1: renamed from eth0
    [295455.373699] docker0: port 1(dockerfc0a3ae) entered disabled state
    [295457.216540] docker0: port 1(dockerfc0a3ae) entered disabled state
    [295457.223355] device dockerfc0a3ae left promiscuous mode
    [295457.229318] docker0: port 1(dockerfc0a3ae) entered disabled state
    [295457.495807] init: pkg-syno-etcd-logd main process (18944) terminated with status 2
    [295457.891192] init: skip respawn pkg-webstation-php-9f1e642a-0d20-4664-8934-c51d34f609de during shutdown
    [295458.103909] init: pkg-etcd main process (16002) killed by TERM signal
    [295459.541206] init: pkg-synocccstated main process (15984) killed by TERM signal
    [295464.396849] dockerc8371c4: renamed from eth0
    [295464.475758] docker0: port 2(docker3512175) entered disabled state
    [295465.822725] docker0: port 2(docker3512175) entered disabled state
    [295465.832829] device docker3512175 left promiscuous mode
    [295465.838437] docker0: port 2(docker3512175) entered disabled state
    [295467.979849] IPVS: [rr] scheduler unregistered.
    [295468.063584] IPVS: ipvs unloaded.
    [295476.577507] init: pkg-SynologyApplicationService-notification_send main process (15615) killed by TERM signal
    [295478.052793] init: pkg-SynologyApplicationService-pgbouncer main process (15733) terminated with status 1
    [295480.050889] init: pkg-SynologyApplicationService-VapidSendServer main process (15931) killed by TERM signal
    [295488.228206] init: Disconnected from D-Bus system bus
    [295488.528307] init: synoscheduler-vmtouch main process (8224) killed by TERM signal
    [295488.537591] init: synoovs-db main process (7746) killed by TERM signal
    [295488.582919] init: synoovs-vswitch main process (7762) killed by TERM signal
    [295491.621544] init: synosnmp-service-handler main process (10043) killed by TERM signal
    [295496.100379] iSCSI:target_core_configfs.c:4695:target_core_drop_subdev process [10124] '/usr/syno/bin/synoiscsihook --volume_umount_all' unload LUN(fileio_0/LUN_0958fe50-abb7-48bf-9c6c-0525362d9374), uuid(0958fe50-abb7-48bf-9c6c-0525362d9374)
    [295496.124073] iSCSI:target_core_rodsp_server.c:172:rodsp_server_sink_unregister SINK-UNREG(0958fe50-abb7-48bf-9c6c-0525362d9374)
    [295496.137420] iSCSI:target_core_configfs.c:5268:volume_drop_item unload volume(volume1)
    logout
    [295496.361132] init: skip respawn tty during shutdown
    [295496.876381] init: skip respawn syslog-ng during shutdown
    [295506.073868] md2: detected capacity change from 11992474714112 to 0
    [295506.080408] md: md2: set sda3 to auto_remap [0]
    [295506.085218] md: md2: set sdc3 to auto_remap [0]
    [295506.090036] md: md2: set sdb3 to auto_remap [0]
    [295506.094915] md: md2 stopped.
    [295506.098011] md: unbind<sda3>
    [295506.105546] md: export_rdev(sda3)
    [295506.109200] md: unbind<sdc3>
    [295506.116547] md: export_rdev(sdc3)
    [295506.120156] md: unbind<sdb3>
    [295506.127546] md: export_rdev(sdb3)
    [295506.606992] sd 4:0:0:0: [synoboot] Synchronizing SCSI cache
    [295509.581550] md: md0 in immediate safe mode
    [295509.582540] md: md1 in immediate safe mode
    [295509.592978] init: cgmanager main process (4722) killed by KILL signal
    [295509.599627] init: skip respawn cgmanager during shutdown
    [295512.521017] EXT4-fs (md0): re-mounted. Opts: (null)
    [295514.173819] kvm: exiting hardware virtualization
    

    I hope this helps?!

     

    Kind regards

    Tobias

×
×
  • Create New...