mattyjasper

I'm getting the same Drive (3,4) errors no matter what I try (done basically the same you have, as well as setting the "internalportcfg" to 0x33 which should disregard drives 3 & 4 but it doesn't take any affect). My motherboard is a Gigabyte H81M-S2V - it has 2x SATA3 ports and 2x SATA2 ports. Any assistance grateful from the community to get this working on my hardware - it looks like a very common issue!

I've found the root cause - some files I was downloading at the time of the initial crash appear to be corrupt/causing the volume to crash. Trying to delete them causes the volume to go into the crashed state again, which can be resolved by rebooting. I've tried deleting the suspect files via SMB and File Station with the same result. Is there any way I can delete them via SSH or similar to bypass the issues? Or run a file system check somehow?

Ok so I just finished backing up all of the data I could (Docker and Downloads folders appeared to be inaccessible) - took over a week via USB onto multiple drives!! Rebooted the NAS after completing the backups before attempting a fresh install..... and everything now shows healthy!! What the hell 🤯😂 Is there anything else I should be checking? The only anomaly I know of on my install is that the "Data Scrubbing" task wont run - it gets to around 1.7% and then stops and shows "Never performed" as the status. Nothing I've tried has been able to resolve this, I even ran the scrub task via SSH. I'm wondering if the lack of data scrub could have been the cause for the potentially incorrect "Crashed volume"? Again - any assistance greatly appreciated

Thanks for the reply IG-88. Do you have any suggested commands to run that I can post output from? Thanks

Hi, Randomly yesterday I got an email from my Xpenology box saying my volume had crashed! After logging in to DSM I can see that the volume is indeed in a crashed state and appears to have been set to read-only. However, checking my HDD status all are healthy, as is the RAID5 Storage Pool. This is very out of the ordinary as everything has been running well for years on end now. I did recently attempt to update to TinyCore but couldn't get the past the correct drive mapping so gave up and went back to my Jun loader USB which booted fine as usual and everything has been working flawlessly since! I have been checking similar recent posts from search (https://xpenology.com/forum/topic/57921-volume-crashed-after-power-outage/?tab=comments#comment-269420 and https://xpenology.com/forum/topic/14337-volume-crash-after-4-months-of-stability/#comment-107979) but after enabling SSH and running some of the check commands I'm not getting the same results. I'm currently backing up data that I can to USB drive just in case, but with 12TB of data this is going to take some time. Some more details on my setup; Jun's 1.03b DS3615xs loader running DSM 6.2.3 u3 Core i3-4130 8GB RAM Gigabtye H81M S2V motherboard 4x 6TB HGST Enterprise HUS726T6TALE6L4 in RAID5 Btrfs Volume If anyone is able to offer some assistance on a possible repair of the volume that would be fantastic. I haven't tried simple things like a reboot yet as I wanted to recover as much data while I can! Thanks Matt

Can anyone help me out? I'm trying to upgrade my baremetal install running Jun's 1.02b DS3615xs loader to RedPill Tinycore. Current DSM is running version 6.2.3 Update 3. Hardware is as follows; i3-4130 Gigabyte H81M-S2V motherboard with 4x SATA ports (2x SATA3, 2x SATA2) 8GB RAM After running the SataMap command I get a SataMap of 6 (even though I only have 4 ports?). When booting up, I can find the installation via find.synology.com and it shows as Migratable. However, after continuing through I get an error saying "Disks 3,4 not detected and Sata ports have been disabled". Someone else has recommended changing the internalportcfg in the user_config.json file to "0x33". This should disable drives 3 & 4, as for some reason my system shows my 4 drives as 1, 2, 5 & 6 (confirmed by booting back into my old Jun loader and checking Storage Manager). Unfortunately, even after doing this I get the same Disk 3,4 error on the Migration wizard. Does anyone have any other ideas to get this to work? Much appreciated!

Bump! Anyone have any ideas on this? Or any logs I can check and provide? Thanks!

HDD cache mode settings make no difference. Still stops at the same percentage

It is a mix of SATA 3 and SATA 2 yes, but its the same hardware as what I previously had 6.1.7 running on and that had 0 issues. I'll try disabling (or enabling) cache and see if that makes a difference. The 3.3v thing you completely lost me?

Confirmed on WD's product page, Ultrastar DC HC310 uses CMR so that's good!

I don't think so, I'll do some more Googling though but appears to only be Reds/Red Pro not the enterprise stuff (I wouldn't imagine WD to scrimp on Enterprise either). What are the implications of using them? The only issue I have is the data scrubbing not working, haven't had any other issues at all (RAID healthy, SMART healthy, all functioning normally etc).

Bump! Anyone got any ideas? Or know a way I can check/run via SSH, or logs etc

Hi all, Recently upgraded my NAS to DSM 6.2.2 running from Jun's 1.03b Loader (DS3615xs). Also upgraded to 4x 6TB drives at the same time. I used Synology Migration Assistant to migrate all my data, packages etc from my old installation. Hardware as follows; Intel Core i3-4130 8GB DDR3 (2x 4GB) Gigabyte GA-H81M-S2V motherboard 4x WD/HGST Ultrastar 6TB drives (HUS726T6TALE6L4) The issue I'm now faced with is that I cannot get Data Scrubbing to complete! The normal scheduled run will kick in randomly and then go to a status of "Waiting for another task to finish" and then randomly start again later on. If I try to run a manual Data Scrubbing task, it gets to around 1.45% and then stops! I have tried rebooting, turning off all possibly packages and Docker containers etc, removing the schedule and running manually, nothing has worked! Does anyone have any ideas to resolve this? Or can i provide any logs somehow to help? I'm worried about the integrity of my data with it as it is. Thanks Matt

As an FYI to anyone else who needs to do this in the future. I have just done the following steps and used the Synology Migration Assistant which has migrated ALL of my packages (Synology official and 3rd party) and ALL of my settings for said packages, system config, Docker containers etc etc. The whole lot basically! The only thing I've had to do is set DNS name and IP address! Synology Migration Assistant gets a massive 10/10 from me! 1. Create new DSM 6.2.2 installation on new hardware using Jun's latest loaders. 2. Boot into DSM and verify basic functionality (all drives detected etc). 3. Create Storage Pool in Storage Manager as required. 4. Download and install Synology Migration Assistant in Package Manager. 5. Follow the Migration Assistant wizard 6. Wait for data/settings to transfer and have a good day!

Bump: Any more input on this please? Thanks all

Thanks for the reply IG-88. Unfortunately I'm not using a SHR, my RAID is configured using the normal RAID5 option. I'm not worried about how long it will take, just want to make sure I do it the right way!

Hi all, I currently have a working Xpenology unit that I have had for a while now running DSM 6.1.7 using Jun's 1.02b loader (DS3615xs) and the following hardware; Intel Core i3-4130 8GB RAM H81M Motherboard (can't remember the exact one now) with an additional SATA card 5x 2TB Hard Drives My issue is that I am running out of space. I have managed to acquire 4x 6TB drives that I want to move my data onto (this should give me ~18TB of space compared to current ~8TB). But I am aware that you cannot downsize a RAID array in DSM (from 5 disks down to 4). Over the years I have configured the NAS exactly how I want it and I have many apps, Docker containers etc configured working well. I don't really want to lose any of this config! What is going to be the best way to deal with this? I've seen that Synology now have a migration tool (Migration Assistant) that is only available on DSM 6.2, but will that do a 100% mirror of my current setup to the new? I can easily set up the hardware on a workbench with another motherboard, CPU, RAM etc to do this. Any assistance welcomed! :) Thanks, Matt