Need help please! Data Loss on my RAID1 after Migrating from 6.2.3 to 6.2.4

[drevil]

Hello, I had an XPenology NAS running 6.2.3 on a Thinkcentre M158 (the tower). It also ran wonderfully until I updated to 6.2.4..

 

The Jun Bootloader 6.2 1.03b for 3615XS is still loaded from the USB stick, but I can no longer connect to the NAS or its RAID1 hard drives. Attempts to enter recovery mode via find.synology.com or with Synology Assistant failed.

I have therefore prepared a new USB stick with the Jun Loader 6.2 1.03b for a 3615XS. In the  grub.cfg on the Bootload Stick entered the information for the USB itself and the MAC address of the Thinkcentre (edited and saved with OSF Mount).

This means that the NAS is found by the assistant or via the browser, but only the point of restoration remains. When I run this, a process also starts, the system reboots once. Then I just see a message saying "System is rebooting" for a few minutes. When this time has expired, I can no longer find the NAS via browser via IP or the Sysnology Assistant.

 

Alternatively, I installed an Ubuntu testwise on an extra HD to check the configuration of the RAID disks. I can mount the RAID but "unknown file system" with a question mark.

 

These are the RAID disks viewed in Ubuntu:

Disk

/dev/sdb - 4000 GB / 3726 GiB - WDC WD40EFAX-68JH4N1

Disk

/dev/sdc - 4000 GB / 3726 GiB - WDC WD40EFAX-68JH4N1

 

I am currently really stumped as to how I can get my data back or whether and how I can reset the NAS to a working 6.2.3. I am very grateful for help. All photos, music, etc. gone. Yes, a backup would have been good but not (anymore). There are 18 years of data on it.. Pictures of the children, etc. How could I have been so careless..

Is there any chance to get back my data?

[IG-88]

3 hours ago, drevil said:

It also ran wonderfully until I updated to 6.2.4..

The Jun Bootloader 6.2 1.03b for 3615XS

 

thats normal and to expect, 6.2.3 u3 is the last that works with jun's loader 1.03b

there is no data loss from that, you just can't boot the operating system aka DSM anymore, your data are on a separate partition

you can undo the unfinished 6.2.4 update or mount the raid with another linux to do a backup (better late then never, and as often to read, raid is no replacement for backup)

 

https://xpenology.com/forum/topic/42765-how-to-undo-a-unfinished-update-623-to-624-no-boot-after-1st-step-of-update/

 

https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/

 

it would also be possible to use a newer loader to update to 7.x but that would need some extra learning as its different from jun's old loader

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

 

its even possible to boot open media vault and access your data over network for backup (or stay with omv if you want)

https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475

 

 

Edited June 30, 2022 by IG-88

[drevil]

@IG-88 Thank you very much for explaining me. 

I tried one of you suggestions and installed the new tinycore redpill loader for a 7.0.1. Edited the files and tried only with the USB-Stick and one HD (none of the RAID1 HD but it was a 3rd "testing" HD of the old config 6.2.3). 

The DiskStation gets recognized and there is an option for migration/recovery. I used it but now i am into some loop. I used the "Keep my settings and my data" option before. It seems to have changed something because it uses my port in the browser i had the old configuration running. But with the old config port i can not reach anything. Its pingable and i did a portscan with nmap as well.

When i use the DiskStations IP in the browser with the standard port 5000 i get that loop. It wants to recover/migrate over and over again.. Not sure what causes this.

 

I am also not sure if it "misses" the RAID1 of the old config with my precious data on it. Maybe i should try again without keeping my settings..? But i am afraid i lose data then.

What would you suggest if i keep going the tinycore DSM 7.x.x way to avoid the loop? 

[drevil]

I installed Openmediavault and can see the following in my browser. Not sure how to fix that.

 

 

Edited July 4, 2022 by drevil

[drevil]

Here is the red message from the picture above  with the error message i get when trying to mount (apply) the BTRFS Filesystem with the personal Data:

 

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian:
----------
          ID: create_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863 for file /etc/fstab was charged by text
     Started: 21:01:20.727538
    Duration: 1.12 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-5bb7ea17-4ecf-4918-8110-73443220a01a
      Result: False
     Comment: mount: /srv/dev-disk-by-uuid-5bb7ea17-4ecf-4918-8110-73443220a01a: can't read superblock on /dev/mapper/vg1-volume_3.
     Started: 21:01:20.729335
    Duration: 6966.35 ms
     Changes:
----------
          ID: create_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344 for file /etc/fstab was charged by text
     Started: 21:01:27.696012
    Duration: 1.295 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-27edbd81-74e9-4628-b942-e5427cfbe489
      Result: True
     Comment: Target was already mounted
     Started: 21:01:27.697455
    Duration: 41.91 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: append_fstab_entries
    Function: file.blockreplace
        Name: /etc/fstab
      Result: True
     Comment: No changes needed to be made
     Started: 21:01:27.740511
    Duration: 4.878 ms
     Changes:

Summary for debian
------------
Succeeded: 4 (changed=1)
Failed:    1
------------
Total states run:     5
Total run time:   7.016 s

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian:
----------
          ID: create_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863 for file /etc/fstab was charged by text
     Started: 21:01:20.727538
    Duration: 1.12 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_2d41fafa-26d7-4594-a7fb-e50b192d7863
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-5bb7ea17-4ecf-4918-8110-73443220a01a
      Result: False
     Comment: mount: /srv/dev-disk-by-uuid-5bb7ea17-4ecf-4918-8110-73443220a01a: can't read superblock on /dev/mapper/vg1-volume_3.
     Started: 21:01:20.729335
    Duration: 6966.35 ms
     Changes:
----------
          ID: create_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344
    Function: file.accumulated
      Result: True
     Comment: Accumulator create_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344 for file /etc/fstab was charged by text
     Started: 21:01:27.696012
    Duration: 1.295 ms
     Changes:
----------
          ID: mount_filesystem_mountpoint_ac0e518c-ef16-42c0-8071-066f7e43d344
    Function: mount.mounted
        Name: /srv/dev-disk-by-uuid-27edbd81-74e9-4628-b942-e5427cfbe489
      Result: True
     Comment: Target was already mounted
     Started: 21:01:27.697455
    Duration: 41.91 ms
     Changes:
              ----------
              umount:
                  Forced remount because options (user_xattr) changed
----------
          ID: append_fstab_entries
    Function: file.blockreplace
        Name: /etc/fstab
      Result: True
     Comment: No changes needed to be made
     Started: 21:01:27.740511
    Duration: 4.878 ms
     Changes:

Summary for debian
------------
Succeeded: 4 (changed=1)
Failed:    1
------------
Total states run:     5
Total run time:   7.016 s in /usr/share/php/openmediavault/system/process.inc:197
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusns...', '/tmp/bgoutputNp...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Edited July 4, 2022 by drevil