Fabien Aurejac

I had the precise information about data-offset from "--examine" mdadm command, and also I was in raid1, that's far less sensitive to error than raid5 or raid0 for example. I would not have been surprised that the resync, if taken to the end, would have worked... But I will never know. As far as I know, I get the data back and I'm very lucky and happy. Thank you

Hello and thanks for your answer. Seems that no, I'm trying R-studio now and it's finding 7 superblocks, and for now it has found 5000+ files... Will try to get this back after the scanning.

I fixed in the past some problems with sata drive by setting to "rolling" the sources in armbian-config. A few day ago I wanted to upgrade to trixie (debian 13) sources. I forgot to set up again the armbian-config sources to "stable" and I went in a bad situation with my raid1 : it completely disappeared from /etc/mdadm/mdadm.conf, and was unable to mount. After several struggling with the command line tools, I managed to get it recreated by the following command : mdadm --create --force /dev/md0 \ --level=1 \ --raid-devices=2 \ /dev/sdc1 /dev/sdd1 \ --metadata=1.2 --data-offset=$(( 264192/2 ))K Now it seems to be syncing, but I think the filesystem was damaged... (though I don't now, perhaps all be ok again after sync) Is there a way other than photorec to get my data back ? Thanks a lot.

If I can in the near future make a step forward to join the community, I'll develop it and make a commit. Do you have some recommandations about the way to do it ? Where are the sources for this ?

All good ! I manage to fix myself my problems, there was several... I changed the sources to "rolling", and with latest kernel inside it, sata was working again. I had also several problems configuring samba, reassembling the raid, and so on... All is ok now. Just a side note, it could be great to develop a GUI to test and set the keyboard at installation, that seems needed (debian does it for example) And last but not least, when the system fails to load, there a strange behaviour with the password for root, I was always unable to log in.

To follow up my post, Werner, or anyone else reading this : My UART adapter was ordered, but the shipping lost its way to me. I have to place an order again. The situation went better for a time without updating the kernel... Then I updated to kernel 6.1.99 and the problem reappeared, now I'm stuck in this because I tried another kernel and it did not boot. For this step, I had to reboot on the SD to the lastest I downloaded at the time of install and installed this version with the root to the nvme, and the bootloader to the SD. It booted, but then after updating to latest, showed no sata anymore. I downloaded again an image under 6.1.99 kernel it worked, but still no sata. I then tried the OMV image, but after configuration, modification of the keyboard layout and reboot, root password typed in every combination possible (regarding QWERTY or AZERTY interpretation of the keyboard input) did not work... It's a problem I already encountered while being sure to have typed the password correctly. I tried also 6.12 images, but no boot (black screen) Someone please help, I'm ok to pay for support (I already did it, but will be grateful to the one who will help).

Thank you Werner I'll check this, I need to buy the equipement to get the logs, and additional information : this happens when I boot from the m2 socket only, not from the sd card.

Hello, here with a Radxa Rock 5 ITX I experience endless loading at reboot after some system upgrades... But not always. Am I doing something wrong by using the command reboot from ssh ? instead of shutdown and power up ? In that case the system loads to rescue mode, asking for the root password and even if entered correctly does not identify. All comes back to working state with a shutdown and a reboot. Notice : I've made a donation to support the team. Please help.