F2-220 dmaged

[chourmovs]

Hi, I'm sad that I have exactly the symptom described here

viewtopic.php?f=9&t=4457

I had a power failure at home beginning of the week, my device restarted and worked for 3 days but suddenly this morning, NAS was not accessible with fixed lights.
I tryed to reboot with no success, I tried the reinstallation procedure with no success (no beep, no disk rotation)
power led is green
lan led is tuned off
hdd leds are red

I tried to reset cmos with battery trick witout any success

May I buy another unit and hope recover my HDD data ? Can I consider upgrading to 221/222/223 ?

Any idea ? Thank you

[TMtina]

Recommended to purchase 221, the hard drive can be plugged in and started to continue using. If considering other models, it needs to be handled according to the situation. What RAID type is being used?

[chourmovs]

Hi TmTina thank you for your answer
I'm almost sure i was in JBOD (or RAID1 - the very basic situation one disk mirror of another))

[keyboardbaguette]

Purchase 221 is recommended, and the hard drive can be plugged in and used.

[chourmovs]

Hi

Waiting my new unit, I try to fix my F2-220 myself
I've dismounted it, removed the USB stick to try to reinstall the boot-loader

I've found the procedure here in the forum but this is not very clear and relevant

DO I really need to vmware ubuntu on windows ? or running the procedure in a native ubuntu is OK ?
My first attempts on the native usb stick say 60Mb is not sufficient disk space

Then I found another larger stick, retry and I get this : (I had to format my stick in FAT, mount it on /media and not /mnt but I get strange behaviour as follow)

Code: Select all

sudo sh make_install bzImage
[sudo] Cabbage Password:
Error: Error opening /dev/sdb: No media found
Error: Error opening /dev/sdb: No media found
#########mkfs ext4#############
mke2fs 1.46.5 (30-Dec-2021)
The file /dev/sdb1 does not exist and no size was specified.
e2label: No such file or folder when trying to open /dev/sdb1
Unable to find a valid file system superblock.
mount: /media: special device /dev/sdb1 does not exist.
#########install grub###########
Installation for x86_64-efi platform.
grub-install: error: Could not find EFI directory.
umount: /media/: unmounted.
#########done##################
umount: /media/chou/UTOSBOOT-X81: The target is active.
Error: At least one partition of /dev/sdc is in use.
Error: You want to establish a partition from 0.00B to 258MB (sectors 0..503551).
The closest manageable position is 512B to 1048kB (sectors 1..2047).
#########mkfs ext4#############
mke2fs 1.46.5 (30-Dec-2021)
/dev/sdc1 is mounted; won't do a file system here!
e2label: Invalid magic number in superblock when trying to open /dev/sdc1
/dev/sdc1 contains a vfat filesystem labeled "UTOSBOOT-X8"
#########install grub###########
Installation for x86_64-efi platform.
Installation completed, without errors.
cp: unable to evaluate '/media/chou/UTOSBOOT-X81/grub.cfg': No such file or folder
cp: unable to evaluate '/media/chou/UTOSBOOT-X81/bzImage': No such file or folder
#########done##################
################COMPLATE!!!###################

for the moment I get this and pluging my new stick on the nas lead to "doesn't boot"

Any relevant advise , reading ?

[chourmovs]

Recommended to purchase 221, the hard drive can be plugged in and started to continue using. If considering other models, it needs to be handled according to the situation. What RAID type is being used?

I've an opportunity on F2-420, is it ok for plug and play with my 2 hdds ?

[TMwuu]

{L_BUTTON_AT}chourmovs

Yes, it's OK.