Re-Boot Loop F2-221 [Running TOS6 Beta]

[Gremlin]

Came in last night to find my F2-221 stuck in a re-boot loop/crash (?) condition. Would not respond to power switch so only recourse was to pull power supply. (no apparent output to HDMI so no viable error messages to work on.)

Just started to surface test hdd's (which were Traid config) so that will be a while

Been here: viewtopic.php?p=29456&hilit=boot+loop#p29456
but don't see much else on the forum of a similar vein. I will check the power supply though at some point.

[TMroy]

Please describe the specific phenomenon. Is the device rebooting repeatedly on its own? If so, it's possible that the power button of the device is malfunctioning, and warranty service may be required.

[Gremlin]

No warranty on this 2nd hand .... but no matter.

Exact symptoms? Well, I wasn't present when it started. But when I did see it I would have to guess "red hhd lights on, red hhd lights off, reboot start red hdd lights on, red hdd lights off, reboot,.... etc, etc," faster than you can say all of that. Tried long press on power switch, tried short press on power switch - quicker than that - pulled power cord.

Quite noisy too, or seemed so at that hour.

This unit is only used as a test-bed, so just letting things take their course. Drive testing will be a couple of days at the current rate.

[TMroy]

During a normal system startup process, the hard drive should not have a red light on. There is likely a hardware failure in your device, possibly with the motherboard, power adapter, or even the hard drive. Please check each one to identify the issue.

[Gremlin]

Just for the .... of it.

Will an otherwise functional unit boot without the initboot USB inserted?

Bought a new power supply rated at 7.5amp/12v DC (although I'm sure the Powertron 3.33A/12V DC that came with the unit was adequate). No Change.

Occasionally see TM bios flash screen mostly with code A2 (bottom right) but have seen B4/A2/99 on occasions.

[TMroy]

Yes, you can boot from the previous HDD in the new device, and you have to set in BIOS boot from HDD.

[Gremlin]

OK, so old F2-221 left for dead (for now anyway)

Set up a new F2-424 (standard, no 'extras') and checked boot into bios = OK. Just changed Bios date.

Set up old Tos 6.0 disks (Traid) and booted.
Everything appears OK except previously unseen error message(s)

BTRFS error (device dm-0): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]
BTRFS error (device dm-0) failed to run delayed ref for logical .......... mum_bytes 65536 type 176 action 1 ref_mod 1: -5
BTRFS: error (device dm-0: State A) in BTRFS_run_delayed_refs error=-5 IO failure
BTRFS info (device dm-0:) State EA: forced read only
BTRFS error (device dm-0: State EA): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]
BTRFS error (device dm-0: State EA): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]

Should I be concerned about these messasges? Nothing apparent in control panel. Should these clear on reboot? I am happy to re-install system if that is needed.

[DigitalAnalog]

OK, so old F2-221 left for dead (for now anyway)

Set up a new F2-424 (standard, no 'extras') and checked boot into bios = OK. Just changed Bios date.

Set up old Tos 6.0 disks (Traid) and booted.
Everything appears OK except previously unseen error message(s)

BTRFS error (device dm-0): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]
BTRFS error (device dm-0) failed to run delayed ref for logical .......... mum_bytes 65536 type 176 action 1 ref_mod 1: -5
BTRFS: error (device dm-0: State A) in BTRFS_run_delayed_refs error=-5 IO failure
BTRFS info (device dm-0:) State EA: forced read only
BTRFS error (device dm-0: State EA): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]
BTRFS error (device dm-0: State EA): parent transid verify failed on logical ........ mirror {1,2} wanted 8966 found 8933 [2 messages total]

Should I be concerned about these messasges? Nothing apparent in control panel. Should these clear on reboot? I am happy to re-install system if that is needed.

Here's a breakdown of what these messages mean:

BTRFS error (device dm-0): parent transid verify failed on logical ... mirror {1,2} wanted 8966 found 8933

• parent transid verify failed: This means that Btrfs detected a mismatch in the transaction ID. The filesystem expected a transaction ID of 8966 but found 8933 instead.
  logical ... mirror {1,2}: Refers to the logical address on the disk and the specific mirror (1 or 2) being checked.
  This error often indicates corruption or inconsistency within the Btrfs metadata.

BTRFS error (device dm-0) failed to run delayed ref for logical ... num_bytes 65536 type 176 action 1 ref_mod 1: -5

• failed to run delayed ref: This means that Btrfs encountered an error while processing a delayed reference, which is part of its internal mechanism to manage metadata updates.
  num_bytes 65536 type 176 action 1 ref_mod 1: These are details about the specific reference that failed.
  -5: Indicates an I/O error (Input/Output error).

BTRFS: error (device dm-0: State A) in BTRFS_run_delayed_refs error=-5 IO failure

• BTRFS_run_delayed_refs: A function within Btrfs that processes delayed references.
  error=-5 IO failure: Again, this indicates an I/O error occurred.

BTRFS info (device dm-0:) State EA: forced read-only

forced read-only: Btrfs has switched the filesystem to read-only mode due to the encountered errors to prevent further damage.

BTRFS error (device dm-0: State EA): parent transid verify failed on logical ... mirror {1,2} wanted 8966 found 8933

• This is a repeated error indicating ongoing issues with the transaction ID mismatch.

Possible Causes:

• Disk Failure: The underlying storage media might be failing.
  Metadata Corruption: The Btrfs filesystem metadata could be corrupted.
  Driver Issues: There might be bugs or issues with the Btrfs driver or related kernel components.

[Gremlin]

Thanks for the analysis

The bit that worried me was the 'force read only' but without any indication in the GUI of a problem. I did notice, however, that an attempt to update the 'snapshot' app did fail.

I do think that the filesystem has repaired itself. Reboot does not show those messages and the snapshot app has had a successful update.

Given the numerous "ups and downs" this went through when the old device failed (Disk swaps, disk checks, raid recovery, system crashes, etc, etc) says a lot for the system's ability to recover and also for the simplicity of swapping a TOS system to a new device.

[Gremlin]

Hmmmm, Interesting (maybe, maybe not!)

After a couple of days of normal running, on this mornings scheduled start after a couple of minutes suddenly 1 hdd disappears from TRAID storage volume. (Buzzer alert was only clue). a simple reboot has fixed whatever issue was present and no time expended with a raid rebuild.

My previous words come back to bite me!