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.145, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 RIP 13/07/24
F2-424 TOS6.0.531 or later - depending on disk set selected - (Still a work in progress )
F2-221 RIP 13/07/24
F2-424 TOS6.0.531 or later - depending on disk set selected - (Still a work in progress )
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!!!###################
- andyw234234
- Posts: 1
- Joined: 28 Oct 2023, 16:38
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
HiTMSupport wrote: ↑20 Jan 2021, 15:59
Solution 2:
If you are not able to access TOS, you have to make a new USB initBoot and replace the failed one. To make a new USB initBoot, please follow the instruction below.
Download the instruction
I have a new U8-450
Tried to boot first time with 2 new NVMe installed.
Unit powers on, LAN blinks (orange only, not both), fans start, there's a single beep - I don't see the machine on the network, and TOS PC software doesn't find it.
Support chat suggested to try without the NVMe; same problem.
I've followed the instructions above for Solution 2, same problem.
I tried with both the original USB drive, and a quality spare drive I have; same problem.
I've tried Cleaning the drive with RMPrepUSB, then formating to FAT32, same problem.
I understand the customer support team will contact me today or Monday to provide a new USB drive.
Given the above, will this solve the issue?
To be clear - the new device has never got past it's current state.
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
{L_BUTTON_AT}andyw234234
It should be caused by USB initBoot failure. Using a new USB initBoot will solve the problem.
To 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)
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
I have made a new initBoot.
I have removed the ram.
I have put in a new battery and I have cleared the cmos settings.
When I start my F2-221 without hard drives the LAN light doesn't stop flashing. I have plugged in a monitor to the hdmi and nothing is displayed there.
Is it a brick?
Thanks
Robyn
I have removed the ram.
I have put in a new battery and I have cleared the cmos settings.
When I start my F2-221 without hard drives the LAN light doesn't stop flashing. I have plugged in a monitor to the hdmi and nothing is displayed there.
Is it a brick?
Thanks
Robyn
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
You can refer to the following link to determine if there is a hardware malfunction: viewtopic.php?f=82&t=4837
To 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)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement)
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
Hello,
I am trying to install the bzImage as instructed in this thread on my F2-422, but I keep getting a
See below screenshot (also image link, in case it doesn't show properly https://ibb.co/BGkBp5D): how can I fix the installation?
Any help is greatly appreciated, thank you.
I am trying to install the bzImage as instructed in this thread on my F2-422, but I keep getting a
Code: Select all
grub-install: error: /media/ doesn't look like an EFI partition.
Any help is greatly appreciated, thank you.
Re: How to fix a faulty USB initBoot for your TNAS?(x.86)
Look at the last line above the error. Mentions arm64. I suspect you have the wrong files. This instruction is for intel based platform.
F5-221 5.1.145, 8GB System Partition on 3 x 4TB Traid; 3TB EXT4
F2-221 RIP 13/07/24
F2-424 TOS6.0.531 or later - depending on disk set selected - (Still a work in progress )
F2-221 RIP 13/07/24
F2-424 TOS6.0.531 or later - depending on disk set selected - (Still a work in progress )