indiana1938

Comments

  • I completed the process and …. tadaaaa! All data are still present and seved to a separate disk.🤗🤩 Thank you so much for your kind support and patience on a noob like me. 😉 Will send you a separate message later.
  • That's it, copied again and started process. ddrescue informed me to add "—force" to the command line, so I added it and process is running now. When copy process is done, what will be the next steps? Removing currend disk from slot 1, putting disk from slot 2 into slot one Replacing disks back into slot 3 and 4 Putting…
  • Just tried to execute " chmod a+x /tmp/ddrescue.armv7l " and got following message: chmod: /tmp/ddrescue.armv7l: No such file or directory What's wrong? I copied the file to /tmp directory by using WinSCP.
  • Here is the result of cat /proc/partitions: major minor #blocks name 7 0 146432 loop0 31 0 256 mtdblock0 31 1 512 mtdblock1 31 2 256 mtdblock2 31 3 10240 mtdblock3 31 4 10240 mtdblock4 31 5 112640 mtdblock5 31 6 10240 mtdblock6 31 7 112640 mtdblock7 31 8 6144 mtdblock8 8 0 1953514584 sda 8 1 1998848 sda1 8 2 1999872 sda2 8…
  • Ok, here is the current status: After reboot the NAS told me, that there is a degraded RAID and offered to repair it. I accepted and after the repair process was finished, the RAID was …. gone again. No RAID, no volume. Therefore I made a reboot again and the RAID was still gone. I made the analysis again via SSH and here…
  • Ok, got following message: mdadm: array /dev/md2 started. Now I started web interface and got following message: After klicking "OK", following window appears: Here is the window with volume information: And the last one with information about Disk Group: Shall I replace the defective HDD by the new one or what shall I do?…
  • Thanks a lot for your kind support. Just to be save: shall I leave defective HDD #2 in the NAS or shall I remove it physically from NAS housing before executing mentioned commands?
  • Ahh, now got it. Sorry for being dumb, but this is my first time working with such tools. Here is the result: mdadm --examine /dev/sd[abcd]3 /dev/sda3: Magic : a92b4efc Version : 1.2 Feature Map : 0x0 Array UUID : da05a358:f28cfe4e:303ab122:2e3ff7a7 Name : NAS542:2 (local to host NAS542) Creation Time : Sat Oct 23 20:27:27…
  • Tried again: login as: admin admin@192.168.178.21's password: BusyBox v1.19.4 (2021-04-01 13:06:33 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ $ su Password: BusyBox v1.19.4 (2021-04-01 13:06:33 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # ~ # mdadm -examine…
  • Now tried with Solar-PuTTY. here is the result: ~ # su BusyBox v1.19.4 (2021-04-01 13:06:33 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. ~ # mdadm ?examine /dev/sd[abcd]3 mdadm: An option must be given to set the mode before a second device (/dev/sda3) is listed ~ #
  • It's possible obviously: open 192.168.178.21 login as: admin admin@192.168.178.21's password: Remote working directory is /home/shares psftp> su psftp: unknown command "su" psftp> mdadm -examine /dev/sd[abcd]3 psftp: unknown command "mdadm" psftp> So what might be the problem?
  • Tried to enter mentioned commands by using Putty terminal )have no Linux), after loggin in on NAS but received error messages only (unknown command). Here is the directory of the NAS:
Default Avatar