cooledspirit

Members
  • Content Count

    32
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cooledspirit

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Hi, I expanded a while ago my 8 disk raid 6 config to 10 disks (3 Tb disks). At that time I was given the posibility to "unfold" to 21.8 Tb, which I accepted. This worked well for quite a while... At a certain moment one disk failed and I now replaced it, but DSM refuses to repair, as there appears to be a 16 Tb limit. I get a popup stating that the limit is 16 Tb, so repair is not possible. My volume is stuck, I can't retrieve data, and I can't repair either. How on earth can I fix this ? Any ideas ? Many thanks !
  2. Hi, I have XPenology (6.1.4 update 5) booting from a USB drive, but I also have a separate HDD running Windows 10 on that same machine. I also would like to add an Ubuntu instance to be able to run file system repairs should I ever need to. I was wondering if I can combine the 3 options to a single disk (with a boot menu of course)? So upon boot get the possibility to select Jun's boot loader or run Ubuntu or run Windows 10. If yes, can you indicate how I can do that ? In terms of partitioning the disk carrying all this and getting the menu available ...
  3. I replaced the RocketRaid sata controller can report that all seems to be working fine now. I managed to upgrade to update 5 without any problem. Would it be ok to enable "write cache" again ? Or is that a bad idea ?
  4. I disabled write cache again (as re-installing DSM overwrote the setting, I forgot to disable it after reinstalling). I can't find any way in the Rocketraid bios to modify what you indicated. I ordered the following non-RAID sata controller (Syba sd-pex40099 4 Port SATA III PCI-EXPRESS 2.0 x) in the hope this will solve everything. By now, I assume it has something to do with the controller or its driver. I read on another place in this forum that the controller above appears to work. What I notice is: parity check with DSM 6.1, update 1 completes succesfully. The same wi
  5. This is what happens... last adding of the 2 disks worked (consistency check passed successfully) on 6.1.4 update 1, however as soon as I dare to install 6.1.4 update 5, the system partition appears to fail and the disks are rejected. That or simply rebooting is a problem.... Any ideas ?
  6. This is what happens... last adding of the 2 disks worked (consistency check passed successfully) on 6.1.4 update 1, however as soon as I dare to install 6.1.4 update 5, the system partition appears to fail and the disks are rejected. Any ideas ?
  7. So this time I have a log that indeed mentions timeouts (see attachment). Can somebody interpret and indicate what might be going on here ? Many thanks in advance ! Cooled Spirit dmesg.log
  8. In the mean time the Synology assistant is detecting the machine again. This topic can be closed.
  9. In attachment the dmesg results when booting with only 2 disks in the lowest SATA slots. dmesg - only the 2 disks.txt
  10. I notice that synology assistant doesn't find the station anymore, even when booting the regular way with the USB. I can access the admin webpage and use telnet though when booted normally...
  11. Please find the log (dmesg) file in attachment. Please also take a look at my questions in my prior reply regarding running re-install on the disks in the lowest 2 channels ? dmesg-log.txt I disabled the serial port (the USB with JUN's boot loader complained that 3F8 was disabled afterwards) I disabled "powernow" from AMD as well Perhaps running an fsck might help ? But how ? If I run syno_poweroff_task -d, my session gets closed.
  12. I see on my router that "diskstation" has gotten an IP address, but there appears to be no way to connect to it, nor via the assistant, telnet or ssh (connection refused)
  13. I rebooted my machine, selecting the "reinstall" option of Jun's loader, but the Synology Assistant can't find the machine so far. Seen the fact that I experienced some problems lately, is it possible that prior to coming available, a file systems check might be running ? Is there a way to validate that (what could be causing the delay of becoming available) ? Or is something else potentially wrong ? I just want to avoid forcing a shutdown in case a file systems check would actually be running. In that case I can wait until the machine becomes available again. In any other case, I
  14. Thank you very much for the suggestions. Currently another attempt is running, so I have to wait a few more hours before I can check what you suggested.