How to fix a faulty USB initBoot for your TNAS?(x.86)
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
PS - I am guilty of making a presumption. Sorry! It is possible to turn off the 'Beep on boot' buzzer from with the OS (some/all not sure).
F5-221 5.1.67 (Since 01/09/23),
8Gb System Partition
on 3 x 4TB IronWolf in Traid
8Gb System Partition
on 3 x 4TB IronWolf in Traid
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
Thanks for the explanation @Gremlin
@TMqiky and @TMzethar
My device doesn't beep, also after doing what this post suggests for such a case:
In case of another TerraMaster device: would I be able to use the HDDs directly as they are, i.e. with all the data, or would they have to be initialized and emptied first, so that I would have to fill them with all the data again?
I have two HDDs. Both were installed as single disks, i.e. no RAID.
I'd named the latest config backup file "TNAS-002E8C_config_backup_20191020_JM33_4.1.03_294", so the installed TOS version must have been "TOS_S2.0_Update_JM33_4.1.03_294.bz2", in case it matters.
@TMqiky and @TMzethar
My device doesn't beep, also after doing what this post suggests for such a case:
So according to the conclusion of this post, the device is damaged and I need a new one?If not, please take out the battery of the device, connect the positive and negative terminals of the battery holder with iron wire for 10 seconds, then assemble the device.
In case of another TerraMaster device: would I be able to use the HDDs directly as they are, i.e. with all the data, or would they have to be initialized and emptied first, so that I would have to fill them with all the data again?
I have two HDDs. Both were installed as single disks, i.e. no RAID.
I'd named the latest config backup file "TNAS-002E8C_config_backup_20191020_JM33_4.1.03_294", so the installed TOS version must have been "TOS_S2.0_Update_JM33_4.1.03_294.bz2", in case it matters.
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
{L_BUTTON_AT}shad
You can consider the TNAS model with CPU J3355/J3455.
If the system configuration on the hard drive is still normal, you can directly start the TNAS and continue using it.
If you cannot start it normally, you need to reinstall TOS for it
viewtopic.php?f=76&t=423To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- andrewjs18
- Posts: 5
- Joined: 11 Sep 2023, 01:11
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
I just picked up a new usb drive from amazon to replace the corrupt/bad boot drive in my F2-223 NAS but I'm getting the following error, can anyone assist?
I have the new usb boot drive attached to my ubuntu web server to load the image onto it. not sure if that matters or not...
thanks in advance!
I have the new usb boot drive attached to my ubuntu web server to load the image onto it. not sure if that matters or not...
thanks in advance!
Code: Select all
/mnt# sudo ./make_install
mke2fs 1.44.5 (15-Dec-2018)
/dev/sdb1 contains a ext4 file system labelled 'UTOSBOOT-X86-S64'
last mounted on Tue Sep 12 01:03:35 2023
Proceed anyway? (y,N) y
Creating filesystem with 3753472 4k blocks and 938400 inodes
Filesystem UUID: 2d71ef13-1c00-4ac6-858f-149e97ad1743
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
#########install grub###########
./make_install: 28: ./make_install: grub-install: not found
cp: cannot create regular file '/media/boot/grub': No such file or directory
cp: cannot create regular file '/media/boot/bzImage': No such file or directory
#########done##################
################COMPLATE!!!###################