Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

moretty's Achievements

Junior Member

Junior Member (2/7)



  1. Hi guys. I have a problem with my raid 5. I have my dsm in version 6 with jun's in a proliant g7 n54l with 5 hard drives. What happens to me is that from time to time it tells me that I have a disk with read and write errors. I once gave it repair from the gui and it worked by putting brand new disks. the case is that the disks have no problem. This week it happened to me again with a disk that gave me a read-write error and I let it go because the raid worked the same, but today when I got home I was surprised that it was dangerous and inaccessible from xpenolgy. I then proceeded to put ubuntu live and mount it with mdadm and it is accessible and it works. The problem is that it tells me that a disk is removed and that the raid started with 4 disks (out of 5). Could you help me fix it so I can use it with xpenology again. Thank you.
  2. First of all thanks for the information. I'm on 6.2.3 and today my certificate expires, use the command but it doesn't work, I have ports 80 and 443. do you know why it could be? Thank you
  3. I have an n54l with dsm 6.2.3 running for years, recently it gave me a disk failure. I bought a new one and replaced it and it tells me that I/O error, I returned the new disk to amazon and bought a new one and the result is the same. The disks that I bought new are fine without errors in smart. the solution that occurred to me was to save the data on another server and delete all dsm and install everything from 0. It worked for me for a few months and now the same errors again and it cannot be repaired. If you can help me I will be very grateful
  4. I already found the problem. Use ubuntu live and mount the disks and the md0 partition was 100% full. Delete any log folder and it worked. Now it would be good to know how to locate the problem of why md0 is filled. can someone help?
  5. Hello, good to all. I wanted to ask for help on the forum because I have a big problem with xpenology. I have a g7 with nic intel and I had it in 6.2.3, it had been running for years without problem but yesterday it gave me a warning of degraded volume due to a disk in bad condition, until then normal, but today there was a power cut and when it turned on Turn on it, it did not let me log in, it said that the memory was full and could not be accessed, again the electricity was cut off and now the access page no longer appears. Can you help me? Thank you
  6. To test, I replaced in the config file *. ovpn the line and I created the VPN on the DSM client side proto udp Replaced by udp6 proto and the connection was made ... between the NAS. * I did that which is quoted by user virouf and it works: https://www.nas-forum.com/forum/topic/69472-perte-connexion-vpn-entre-2-nas-synology/
  7. Thanks a lot. Fixed, use ncdu and delete 500mb file in var / log audio_debug_msg
  8. Hello, sorry for the inconvenience. I have the same problem / dev / md0 2.3G 2.2G 7.5M 100% / I don't know what it is due to and how I can fix it. can you help me?
  9. Thank you very much for the help. It was a permission problem on the ssh folder. Fix it
  10. Hello everyone. I have a problem since yesterday. Every time I try to access ssh it tells me connection refused. I can only access by telnet, can someone help me? Thank you
  11. Thank you. Install 6.0.8 and the usb appears working. The problem is that vm does not work for me, the screen remains blank. Does 6.0.8 work well for you?
  12. Thanks for the help. I did what you tell me but I am not able to recognize any usb. really what I want is to virtualize volumio and detect the correct dac. If you can think of something I would appreciate it
  13. 6.2.3- 25426 I think the problem is in vboxusers and the permissions but I don't know how to do this
  • Create New...