Search the Community

Buenas, Tengo un Proliant g8 montado con xpenology, DSM creo que el 6.0.1 haciendo un cambio en la interfaz bond1 que engloba la LAN1 y la LAN2 he perdido la conexión al DSM, estaba usando IP estática 192.168.1.88 y no tengo ping. He desconectado la lan1 y he dejado la lan2, seguía sin ping, he vuelto a conectar la 1 y he conectado la 2 mismo problema. DHCP no está pidiendo al Router porque en la tabla de DHCP no tengo asignada ninguna ip nueva. ¿Hay alguna manera de acceder localmente? cuando arranca con el usb, por la vga del proliant lo último que aparece es boting the kernel, creo que no había manera de acceder localmente conectando un teclado a la máquina, ¿verdad? Entiendo que el Bond no se ha debido crear correctamente, he reiniciado el servidor y nada, he probado con el wireshark a ver si veia algún arp de las mac del proliant pero no veo nada ¿alguna idea de qué puedo hacer?

Buenas, tengo un Acer Aspire X3960 con el ultimo loader de Jun y con DSM 6.1.5-15254 update 1, funcionando perfectamente en una red local de 100 mbps. Luego cuando lo traigo a casa, con mi red a Gigabit no hay manera de conectar. Pierde muchos pings y es imposible conectar. Si pongo un cable directo entre el iMac y el DSM funciona perfectamente. En cambio ponerlo en la red local no hay manera. He probado a cambiar la MTU a 1500, a 9000 y no hay forma. El resto de dispositivos de red funciona perfectamente con los dos switches que tengo actualmente. Esto es un ejemplo de perdidas de paquetes PING 192.168.10.224 (192.168.10.224): 56 data bytes 64 bytes from 192.168.10.224: icmp_seq=0 ttl=63 time=1.037 ms Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 64 bytes from 192.168.10.224: icmp_seq=4 ttl=63 time=1.055 ms 64 bytes from 192.168.10.224: icmp_seq=5 ttl=63 time=1.226 ms 64 bytes from 192.168.10.224: icmp_seq=6 ttl=63 time=1.237 ms 64 bytes from 192.168.10.224: icmp_seq=7 ttl=63 time=1.246 ms 64 bytes from 192.168.10.224: icmp_seq=8 ttl=63 time=1.128 ms 64 bytes from 192.168.10.224: icmp_seq=9 ttl=63 time=1.285 ms Request timeout for icmp_seq 10 Request timeout for icmp_seq 11 Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 Request timeout for icmp_seq 17 ^C ¿Alguna ideal? Gracias.

Hey, I'm running XPEnology DSM 6.0.2-8451 Update 11 on a self built computer. I started out with 4 x 1Tb older Samsung drives (HD103UJ & HD103SJ). These are in SHR2/BTRFS array (enabled SHR for DS3615xs). This setup hasn't had any issues and I intended to expand the array with other 1Tb drives, but I decided to go with bigger drives since I had the chance to do so. So I added a 3Tb WD Red and started expanding the volume. The main goal was to replace the 1Tb drives one by one with 3Tb drives and have 5x 3Tb WD Reds in the end. The expansion went ok and so did the consistency check. Then for some unknown reason the newly added disk was restarted, then degraded the swap system volume, then degraded the volume, was "inserted" and "removed" (although I didn't do anything) and finally it degraded the root system volume on the disk. I tried repairing the volume, but it didn't help. I shut the server down and no new data has been written on the array since this issue. Yesterday I finally had time to do something about this, so I removed the disk, emptied everything on the disk and re-inserted it in the XPEnology server. I also changed the SATA-cable and power cable for the disk. Repair was successful like the array expansion before and so was the consistency check. After this had finished, I started the RAID scrub. Even the scrub went through just fine at 3:28:01 and then it did just about the same as when I was expanding the array. Disk restarted due to "unknown error", volumes degraded and the disk 5 was inserted and removed from the array. This is the situation now along with: Next step is of course to run diagnostics on that WD Red, but for some reason I don't think it's the disk that is causing this issue. I also have a few other WD Reds which I could be able to try out, but I'd need to empty them first. If you have some inkling on what could be causing this, It'd be appreciated. Best regards, Darkened aka. Janne