Problems with B3 rescue and disassembly

[matse]

Hi,

one of my dear B3s got unreachable after a likely misconfiguration of the network interfaces yesterday (tried to add a vlan interface).

After a few unsuccesful attempts to re-establish contact with the B3 using different rescue USB sticks, I have started suspecting a hardware failure and wanted to swap the disk with another of my B3s. But now hitting the next hurdle, not being able to get the boards+HD to slide out of the B3 chassi! I have unscrewed the four screws on the back plate and removed it, then tried to push the side locking tabs apart (and opposite way) to let the board plus front panel slide out from the the front side, but it does not come out more than 1mm.

I have once installed the disks in these B3s myself, and cannot remember having any problems with that.

Anyway, if someone has some hints for how to progress from here, would be immensly grateful!

KR
Mats

[matse]

BTW, when trying to boot with USB rescue stick (b3-bullseye-install, rescue only), the B3 LED ends up in a loop blinking: 1/2 sec yellow, out,1/2 sec purple/pink, out, 3 sec green, out, repeat.

Does this mean someting?

[MouettE]

BTW, when trying to boot with USB rescue stick (b3-bullseye-install, rescue only), the B3 LED ends up in a loop blinking: 1/2 sec yellow, out,1/2 sec purple/pink, out, 3 sec green, out, repeat.

Does this mean someting?

Yes, the rescue script on the key is supposed to spell relevant number from the IP configured (either statically or with DHCP) once it's booted ; in your case you have one yellow then one purple so that's 1,0 which describes an IP ending in .10 (for example 192.168.1.10 if your network uses the 192.168.1.0/24 prefix).

[matse]

Thanks for that! Are the LED signals on boot described somewhere?

In the meantime I was able to boot with a Gentoo rescue stick, access the configuration files on the disk and restore the previous network settings, and after that the B3 booted and connected successfully. All my data is available on the disk!

Still, the B3 seems to be a bit unstable at the moment. On some boot attempts with the rescue stick, the LED never went on at all. Other times when the booting was successful I was able to ssh into the B3, but the internal HD was not listed when running lsblk, and dmesg reported several errors.

Is this all normal, or I should better not rely on this particular B3/disk anymore?

[MouettE]

Thanks for that! Are the LED signals on boot described somewhere?

Nope and I admit I'm kinda lazy to write it.

Still, the B3 seems to be a bit unstable at the moment. On some boot attempts with the rescue stick, the LED never went on at all. Other times when the booting was successful I was able to ssh into the B3, but the internal HD was not listed when running lsblk, and dmesg reported several errors.

Is this all normal, or I should better not rely on this particular B3/disk anymore?

It depends on the type or errors dmesg reports (either from the disk or the controller) ; I guess that once your data is retrieved you could try a new disk and see if you still have errors.