Page 3 of 4
Re: Conventional Repair Method of BTRFS/EXT4 Volume File System
Posted: 12 May 2022, 00:36
by gcok
TMSupport wrote:
>
>
> Yes, please prepare a hard disk with enough capacity to back up the data
> first.
While backing up my drives, the TNAS crashed several times as it has been doing since the last update and now the TNAS wants to go through initilization again. I can not login via TNAS anymore!!
How can I access my files to try and back up more stuff, so I can finally get this damned thing formatted to EXT4 ?
Device is F4-210
Re: Conventional Repair Method of BTRFS/EXT4 Volume File System
Posted: 12 May 2022, 17:57
by TMSupport
If it is convenient, you can contact our tech team to assist you in back up data.
Re: Conventional Repair Method of BTRFS/EXT4 Volume File System
Posted: 27 Sep 2022, 17:38
by q2lamer
my device Updated to newest software ist a
F2-420 my volume 2 is just gone yesterday when i double click in a folder it was empty so i restarted many times and then the volume 2 dissapear i get this after the command after several reboots the Hardrive is shown as Green Good but its not mounted and as you can see many error can anyone from the Techs help me please ?
Code: Select all
[61774.583246] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
in
[61774.591320] ata2.00: status: { DRDY SENSE ERR }
[61774.591326] ata2.00: error: { ABRT }
[61774.591615] ata2.00: configured for UDMA/133 (device error ignored)
[61774.592840] ata2: EH complete
[61774.599003] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.599017] ata2.00: irq_stat 0x40000001
[61774.599026] ata2.00: failed command: READ DMA
[61774.599039] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 13 dma 4096 in
[61774.599051] ata2.00: status: { DRDY SENSE ERR }
[61774.599057] ata2.00: error: { ABRT }
[61774.599415] ata2.00: configured for UDMA/133 (device error ignored)
[61774.600757] ata2: EH complete
[61774.607267] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.607282] ata2.00: irq_stat 0x40000001
[61774.607291] ata2.00: failed command: READ DMA
[61774.607304] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 14 dma 4096 in
[61774.607315] ata2.00: status: { DRDY SENSE ERR }
[61774.607321] ata2.00: error: { ABRT }
[61774.607656] ata2.00: configured for UDMA/133 (device error ignored)
[61774.608891] ata2: EH complete
[61774.615155] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.615169] ata2.00: irq_stat 0x40000001
[61774.615178] ata2.00: failed command: READ DMA
[61774.615191] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 15 dma 4096 in
[61774.615203] ata2.00: status: { DRDY SENSE ERR }
[61774.615209] ata2.00: error: { ABRT }
[61774.615534] ata2.00: configured for UDMA/133 (device error ignored)
[61774.616776] sd 2:0:0:0: [sdb] tag#15 FAILED Result: hostbyte=DID_OK driverbyt e=DRIVER_SENSE
[61774.616791] sd 2:0:0:0: [sdb] tag#15 Sense Key : Illegal Request [current]
[61774.616801] sd 2:0:0:0: [sdb] tag#15 Add. Sense: Unaligned write command
[61774.616813] sd 2:0:0:0: [sdb] tag#15 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[61774.616823] print_req_error: I/O error, dev sdb, sector 0
[61774.616832] Buffer I/O error on dev sdb, logical block 0, async page read
[61774.616857] ata2: EH complete
[61774.634786] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.634800] ata2.00: irq_stat 0x40000001
[61774.634809] ata2.00: failed command: READ DMA
[61774.676860] sd 2:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_OK driverbyt e=DRIVER_SENSE
[61774.676875] sd 2:0:0:0: [sdb] tag#20 Sense Key : Illegal Request [current]
[61774.676885] sd 2:0:0:0: [sdb] tag#20 Add. Sense: Unaligned write command
[61774.676897] sd 2:0:0:0: [sdb] tag#20 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[61774.676907] print_req_error: I/O error, dev sdb, sector 0
[61774.676915] Buffer I/O error on dev sdb, logical block 0, async page read
[61774.676942] ata2: EH complete
[61774.694706] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.694720] ata2.00: irq_stat 0x40000001
[61774.694728] ata2.00: failed command: READ DMA
[61774.694741] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 1 dma 4096 i n
[61774.694752] ata2.00: status: { DRDY SENSE ERR }
[61774.694758] ata2.00: error: { ABRT }
[61774.694943] ata2.00: configured for UDMA/133 (device error ignored)
[61774.696351] ata2: EH complete
[61774.704278] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.704291] ata2.00: irq_stat 0x40000001
[61774.704300] ata2.00: failed command: READ DMA
[61774.704313] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 21 dma 4096 in
[61774.704325] ata2.00: status: { DRDY SENSE ERR }
[61774.704330] ata2.00: error: { ABRT }
[61774.704585] ata2.00: configured for UDMA/133 (device error ignored)
[61774.705825] ata2: EH complete
[61774.712285] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.712298] ata2.00: irq_stat 0x40000001
[61774.712308] ata2.00: failed command: READ DMA
[61774.712320] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 22 dma 4096 in
[61774.712332] ata2.00: status: { DRDY SENSE ERR }
[61774.712338] ata2.00: error: { ABRT }
[61774.712610] ata2.00: configured for UDMA/133 (device error ignored)
[61774.713861] ata2: EH complete
[61774.720160] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.720174] ata2.00: irq_stat 0x40000001
[61774.720184] ata2.00: failed command: READ DMA
[61774.720197] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 23 dma 4096 in
[61774.720208] ata2.00: status: { DRDY SENSE ERR }
[61774.720214] ata2.00: error: { ABRT }
[61774.720617] ata2.00: configured for UDMA/133 (device error ignored)
[61774.721863] ata2: EH complete
[61774.728204] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.728218] ata2.00: irq_stat 0x40000001
[61774.728227] ata2.00: failed command: READ DMA
[61774.728240] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 24 dma 4096 in
[61774.728252] ata2.00: status: { DRDY SENSE ERR }
[61774.728257] ata2.00: error: { ABRT }
[61774.728633] ata2.00: configured for UDMA/133 (device error ignored)
[61774.729860] ata2: EH complete
[61774.736299] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.736312] ata2.00: irq_stat 0x40000001
[61774.736322] ata2.00: failed command: READ DMA
[61774.736335] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 25 dma 4096 in
[61774.736346] ata2.00: status: { DRDY SENSE ERR }
[61774.736352] ata2.00: error: { ABRT }
[61774.736603] ata2.00: configured for UDMA/133 (device error ignored)
[61774.737841] sd 2:0:0:0: [sdb] tag#25 FAILED Result: hostbyte=DID_OK driverbyt e=DRIVER_SENSE
[61774.737855] sd 2:0:0:0: [sdb] tag#25 Sense Key : Illegal Request [current]
[61774.737866] sd 2:0:0:0: [sdb] tag#25 Add. Sense: Unaligned write command
[61774.737877] sd 2:0:0:0: [sdb] tag#25 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[61774.737887] print_req_error: I/O error, dev sdb, sector 0
[61774.737896] Buffer I/O error on dev sdb, logical block 0, async page read
[61774.737922] ata2: EH complete
[61774.754535] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.754548] ata2.00: irq_stat 0x40000001
[61774.754557] ata2.00: failed command: READ DMA
[61774.754570] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 2 dma 4096 i n
[61774.754581] ata2.00: status: { DRDY SENSE ERR }
[61774.754588] ata2.00: error: { ABRT }
[61774.754773] ata2.00: configured for UDMA/133 (device error ignored)
[61774.756014] ata2: EH complete
[61774.762357] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.762367] ata2.00: irq_stat 0x40000001
[61774.762375] ata2.00: failed command: READ DMA
[61774.762388] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 26 dma 4096 in
[61774.762399] ata2.00: status: { DRDY SENSE ERR }
[61774.762405] ata2.00: error: { ABRT }
[61774.762628] ata2.00: configured for UDMA/133 (device error ignored)
[61774.763861] ata2: EH complete
[61774.768386] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.768396] ata2.00: irq_stat 0x40000001
[61774.768404] ata2.00: failed command: READ DMA
[61774.768417] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 27 dma 4096 in
[61774.768428] ata2.00: status: { DRDY SENSE ERR }
[61774.768434] ata2.00: error: { ABRT }
[61774.768707] ata2.00: configured for UDMA/133 (device error ignored)
[61774.769936] ata2: EH complete
[61774.776256] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.776270] ata2.00: irq_stat 0x40000001
[61774.776280] ata2.00: failed command: READ DMA
[61774.776293] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 28 dma 4096 in
[61774.776304] ata2.00: status: { DRDY SENSE ERR }
[61774.776310] ata2.00: error: { ABRT }
[61774.776630] ata2.00: configured for UDMA/133 (device error ignored)
[61774.777939] ata2: EH complete
[61774.785258] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.785272] ata2.00: irq_stat 0x40000001
[61774.785281] ata2.00: failed command: READ DMA
[61774.785294] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 29 dma 4096 in
[61774.785306] ata2.00: status: { DRDY SENSE ERR }
[61774.785311] ata2.00: error: { ABRT }
[61774.785637] ata2.00: configured for UDMA/133 (device error ignored)
[61774.786863] ata2: EH complete
[61774.793305] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.793319] ata2.00: irq_stat 0x40000001
[61774.793329] ata2.00: failed command: READ DMA
[61774.793342] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 30 dma 4096 in
[61774.793353] ata2.00: status: { DRDY SENSE ERR }
[61774.793359] ata2.00: error: { ABRT }
[61774.793611] ata2.00: configured for UDMA/133 (device error ignored)
[61774.794851] sd 2:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_OK driverbyt e=DRIVER_SENSE
[61774.794865] sd 2:0:0:0: [sdb] tag#30 Sense Key : Illegal Request [current]
[61774.794876] sd 2:0:0:0: [sdb] tag#30 Add. Sense: Unaligned write command
[61774.794887] sd 2:0:0:0: [sdb] tag#30 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[61774.794897] print_req_error: I/O error, dev sdb, sector 0
[61774.794906] Buffer I/O error on dev sdb, logical block 0, async page read
[61774.794932] ata2: EH complete
[61774.812753] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.812767] ata2.00: irq_stat 0x40000001
[61774.812776] ata2.00: failed command: READ DMA
[61774.812788] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 3 dma 4096 i n
[61774.812800] ata2.00: status: { DRDY SENSE ERR }
[61774.812805] ata2.00: error: { ABRT }
[61774.813007] ata2.00: configured for UDMA/133 (device error ignored)
[61774.814444] ata2: EH complete
[61774.819274] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.819284] ata2.00: irq_stat 0x40000001
[61774.819291] ata2.00: failed command: READ DMA
[61774.819303] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 i n
[61774.819315] ata2.00: status: { DRDY SENSE ERR }
[61774.819321] ata2.00: error: { ABRT }
[61774.819594] ata2.00: configured for UDMA/133 (device error ignored)
[61774.820847] ata2: EH complete
[61774.831004] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.831018] ata2.00: irq_stat 0x40000001
[61774.831026] ata2.00: failed command: READ DMA
[61774.831039] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 1 dma 4096 i n
[61774.831050] ata2.00: status: { DRDY SENSE ERR }
[61774.831056] ata2.00: error: { ABRT }
[61774.831455] ata2.00: configured for UDMA/133 (device error ignored)
[61774.832700] ata2: EH complete
[61774.838237] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.838246] ata2.00: irq_stat 0x40000001
[61774.838254] ata2.00: failed command: READ DMA
[61774.838266] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 2 dma 4096 i n
[61774.838278] ata2.00: status: { DRDY SENSE ERR }
[61774.838283] ata2.00: error: { ABRT }
[61774.838595] ata2.00: configured for UDMA/133 (device error ignored)
[61774.839904] ata2: EH complete
[61774.845376] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.845385] ata2.00: irq_stat 0x40000001
[61774.845392] ata2.00: failed command: READ DMA
[61774.845405] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 3 dma 4096 i n
[61774.845416] ata2.00: status: { DRDY SENSE ERR }
[61774.845422] ata2.00: error: { ABRT }
[61774.845700] ata2.00: configured for UDMA/133 (device error ignored)
[61774.846922] ata2: EH complete
[61774.854002] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.854016] ata2.00: irq_stat 0x40000001
[61774.854025] ata2.00: failed command: READ DMA
[61774.854038] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 4 dma 4096 i n
[61774.854049] ata2.00: status: { DRDY SENSE ERR }
[61774.854055] ata2.00: error: { ABRT }
[61774.854440] ata2.00: configured for UDMA/133 (device error ignored)
[61774.855669] sd 2:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte =DRIVER_SENSE
[61774.855683] sd 2:0:0:0: [sdb] tag#4 Sense Key : Illegal Request [current]
[61774.855694] sd 2:0:0:0: [sdb] tag#4 Add. Sense: Unaligned write command
[61774.855705] sd 2:0:0:0: [sdb] tag#4 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[61774.855715] print_req_error: I/O error, dev sdb, sector 0
[61774.855724] Buffer I/O error on dev sdb, logical block 0, async page read
[61774.855750] ata2: EH complete
[61774.855753] Dev sdb: unable to read RDB block 0
[61774.872700] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.872714] ata2.00: irq_stat 0x40000001
[61774.872722] ata2.00: failed command: READ DMA
[61774.872735] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 4 dma 4096 i n
[61774.872747] ata2.00: status: { DRDY SENSE ERR }
[61774.872752] ata2.00: error: { ABRT }
[61774.872937] ata2.00: configured for UDMA/133 (device error ignored)
[61774.874638] ata2: EH complete
[61774.878427] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[61774.878437] ata2.00: irq_stat 0x40000001
[61774.878446] ata2.00: failed command: READ DMA
[61774.878458] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 11 dma 4096 in
[61774.878470] ata2.00: status: { DRDY SENSE ERR }
[61774.878476] ata2.00: error: { ABRT }
Please HELP me all my importend DATA is gone
Re: Conventional Repair Method of BTRFS/EXT4 Volume File System
Posted: 27 Sep 2022, 18:44
by TMSupport
The output information can see the obvious "I/O error". It is recommended that you find a data recovery company for help.
Re: How to repair a corrupted file system?
Posted: 09 Feb 2023, 17:45
by epsilonion
I would put posts like this as part of the documentation on the main website, that way repeated questions won't be asked.
It would be awesome to have documentation like this in a easy to find place like in a documents tab on the main website.
Also please sticky (pin) this to the forum
Thank you
Re: How to repair a corrupted file system?
Posted: 29 Mar 2023, 02:52
by user222333
Please help me.
I wanted to add an additional HDD. To do this, I turned off F2-221 and attached HDD_2 to slot 1.
Now I know what to do wrong.
As a result of adding HDD_2, Terramaster F2-221 replaced TOS 5.1.29 installed on HDD_1 with TOS 4.2, which was contained on HDD_2.
I have lost access to my data on HDD_1.
I have administrator passwords and logins for both TOS 5.1.29 and TOS 4.2. (HDD_1 and HDD_2)
But the accounts of former users on HDD_1 are now inaccessible.
There is no data on HDD_2, I was going to format it as an additional HDD.
How can I get back access to TOS 5.1.29 on HDD_1 or at least save the data?
Should I use the instruction posted in this section: "How to repair a corrupted file system?"
Re: How to repair a corrupted file system?
Posted: 29 Mar 2023, 11:33
by TMSupport
Two hard disks installed with different TOS version cannot be used together. Please try to shut down, pull out HDD2, and power on with HDD1 only. You need to connect HDD2 to the computer and format it before inserting it for use.
Re: How to repair a corrupted file system?
Posted: 29 Mar 2023, 18:51
by user222333
Thanks for the answer.
I followed your advice, but the problem didn't get solved.
After incorrectly enabling two HDDs with different TOS, I tried to enable Terramaster F2-221 with only one HDD_1.
As a result, I saw that Terramaster F2-221 rewrote TOS 5.1.29 installed on HDD_1 to TOS 4.2
Thus, I lost access to user accounts and their data on HDD_1.
They are not displayed now. Now TOS 4.2 is installed on HDD_1, former accounts are not displayed.
I have administrator passwords and logins for both TOS 5.1.29 and TOS 4.2. (HDD_1 and HDD_2)
How can I get back access to TOS 5.1.29 on HDD_1 or at least save the data?
Re: How to repair a corrupted file system?
Posted: 29 Mar 2023, 19:20
by TMwuu
You can use HDD1 alone to boot up the system. Or insert all the hard drives and reinstall the TOS system.
Re: How to repair a corrupted file system?
Posted: 29 Mar 2023, 19:47
by user222333
Thanks for the answer.
Will I be able to access previously recorded data as a result of reinstalling TOS?
At the moment, TOS 4.2 is recorded on HDD_1, it is operational.
I have an admin username and password.
But the user data that was on it before the incorrect inclusion is now inaccessible.
I think that user data is saved, but not displayed.
I want to return access to TOS 5.1.29 on HDD_1 or at least save the data.
It's also not clear how I can use HDD_5? I have a Terramaster F2-221