ziomekdjpl Posted December 14, 2020 Share #1 Posted December 14, 2020 hey, i have gen8, loader 1.03b, its works well a lot of time. 2 days ago its shutdown. Today i power on it but i cant ping it. i see on iLO that its boot up good. I SSH to iLO and turn on virtual serial and i see that: Quote [ 4.280536] synobios ioctl TCGETS /dev/ttyS1 failed [ 4.282280] synobios unable to set termios of /dev/ttyS1 [ 4.333351] md: invalid raid superblock magic on sda5 [ 4.359246] md: invalid raid superblock magic on sda6 [ 4.399273] md: invalid raid superblock magic on sdb5 [ 4.418213] md: invalid raid superblock magic on sdb6 [ 4.465834] md: invalid raid superblock magic on sdc5 [ 4.488919] md: invalid raid superblock magic on sdc6 [ 4.512475] md: invalid raid superblock magic on sdc7 [ 4.561532] md: invalid raid superblock magic on sdd5 [ 4.584669] md: invalid raid superblock magic on sdd6 [ 4.601128] md: invalid raid superblock magic on sdd7 [ 26.325082] synobios ioctl TCGETS /dev/ttyS1 failed [ 26.327320] synobios unable to set termios of /dev/ttyS1 [ 58.203416] synobios write K to /dev/ttyS1 failed [ 61.134682] synobios write K to /dev/ttyS1 failed [ 61.225906] synobios write K to /dev/ttyS1 failed [ 68.077822] synobios write K to /dev/ttyS1 failed [ 69.074314] synobios write K to /dev/ttyS1 failed [ 93.280528] synobios write K to /dev/ttyS1 failed [ 93.694885] synobios write K to /dev/ttyS1 failed [ 93.848005] synobios write K to /dev/ttyS1 failed RAID damaged? Whats happend? Im afraid of my data is lost Quote Link to comment Share on other sites More sharing options...
flyride Posted December 14, 2020 Share #2 Posted December 14, 2020 Invalid raid superblock magic in dmesg is "normal" for any Storage Pool array member device. At that point in the boot, the kernel is trying to start the /md0 boot and /md1 swap arrays that use a V0.90 superblock type, and reject the V1.2 superblocks for the data arrays. Later in the boot, it will start the Storage Pool arrays. tty devices are used for serial port console, and also to control the custom beep and led PCB's on a real Synology. It looks like perhaps DSM is generating an error message trying to write to that custom PCB port. Can you log in via serial and see if your arrays are started? If so, you just have a network issue. Quote Link to comment Share on other sites More sharing options...
ziomekdjpl Posted December 14, 2020 Author Share #3 Posted December 14, 2020 I login via serial, i see my volume1, so the problem is with network. this is ifconfig: Quote docker0 Link encap:Ethernet HWaddr 02:42:19:8A:5F:3B inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:26:55:DF:7A:24 inet6 addr: fe80::226:55ff:fedf:7a24/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:517 errors:0 dropped:0 overruns:0 frame:0 TX packets:125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:110423 (107.8 KiB) TX bytes:34518 (33.7 KiB) Interrupt:16 memory 0xfbfe0000-fc000000 eth1 Link encap:Ethernet HWaddr 00:26:55:DF:7A:25 inet6 addr: fe80::226:55ff:fedf:7a25/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:519 errors:0 dropped:0 overruns:0 frame:0 TX packets:127 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:109866 (107.2 KiB) TX bytes:35627 (34.7 KiB) Interrupt:17 memory 0xfbfa0000-fbfc0000 eth50 Link encap:Ethernet HWaddr 66:82:DB:A6:7C:94 inet addr:192.168.192.55 Bcast:192.168.192.255 Mask:255.255.255.0 inet6 addr: fe80::6482:dbff:fea6:7c94/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:287 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 B) TX bytes:61732 (60.2 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1514 errors:0 dropped:0 overruns:0 frame:0 TX packets:1514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:284282 (277.6 KiB) TX bytes:284282 (277.6 KiB) ovs_bond0 Link encap:Ethernet HWaddr 00:26:55:DF:7A:24 inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::226:55ff:fedf:7a24/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:546 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:128212 (125.2 KiB) Its look ok Quote Link to comment Share on other sites More sharing options...
IG-88 Posted December 15, 2020 Share #4 Posted December 15, 2020 at least on updates the bonds are often a source of problems also check you network hardware / cables and config if you have access by serial console you could shutdown and cut power to exclude temp. hardware related problems and if that does not work its possible to reset the network config files of dsm to default, it might also be possible to get network access with a added usb nic Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.