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.

[matse]

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

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

OK. (Is it the IP of the WAN or LAN port that is signalled this way?)

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.

Here is what demsg reported when internal disk did not show up in lsblk:

Code: Select all

b3 ~ # dmesg | grep -i sd
[    0.081111] Installing knfsd (copyright (C) 1996 [email protected]).
[    1.825143] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.753395] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    2.761209] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    3.282545] sd 0:0:0:0: [sda] Write Protect is off
[    3.287379] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.287723] sd 0:0:0:0: [sda] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    3.295490] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    3.301010] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.310231] sd 0:0:0:0: [sda] Write Protect is off
[    3.315049] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.933231]  sda: sda1 sda2 sda3
[    3.940143] sda: detected capacity change from 0 to 4000787030016
[    3.947915] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.739814] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    4.746041] sd 2:0:0:0: [sdb] 31457280 512-byte logical blocks: (16.1 GB/15.0 GiB)
[    4.754633] sd 2:0:0:0: [sdb] Write Protect is off
[    4.759436] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[    4.760299] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    4.774967]  sdb: sdb1 sdb2 sdb3
[    4.781801] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[    7.818450] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[   10.045740] sda: detected capacity change from 0 to 4000787030016
[   10.057510] sda: detected capacity change from 0 to 4000787030016
[   16.195203] sda: detected capacity change from 0 to 4000787030016
[   16.722430] sda: detected capacity change from 0 to 4000787030016
[   17.282314] sda: detected capacity change from 0 to 4000787030016
[   17.870155] sda: detected capacity change from 0 to 4000787030016
[   18.464439] sda: detected capacity change from 0 to 4000787030016
[   19.521833] sda: detected capacity change from 0 to 4000787030016
[   19.522531] sda: detected capacity change from 0 to 4000787030016
[   23.128096] EXT4-fs (sdb3): re-mounted. Opts: (null)
[   23.701687] sd 0:0:0:0: [sda] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   23.701699] sd 0:0:0:0: [sda] tag#27 Sense Key : 0x5 [current]
[   23.701707] sd 0:0:0:0: [sda] tag#27 ASC=0x21 ASCQ=0x4
[   23.701720] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd b0 00 00 00 08 00 00
[   23.701727] print_req_error: I/O error, dev sda, sector 7814036912
[   23.936331] Adding 1048572k swap on /dev/sdb2.  Priority:-2 extents:1 across:1048572k
[   26.801955] sd 0:0:0:0: [sda] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   26.801981] sd 0:0:0:0: [sda] tag#6 Sense Key : 0x5 [current]
[   26.802003] sd 0:0:0:0: [sda] tag#6 ASC=0x21 ASCQ=0x4
[   26.802031] sd 0:0:0:0: [sda] tag#6 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd b0 00 00 00 08 00 00
[   26.802046] print_req_error: I/O error, dev sda, sector 7814036912
[   26.802062] Buffer I/O error on dev sda, logical block 976754614, async page read
[   37.751763] sd 0:0:0:0: [sda] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   37.751775] sd 0:0:0:0: [sda] tag#17 Sense Key : 0x5 [current]
[   37.751783] sd 0:0:0:0: [sda] tag#17 ASC=0x21 ASCQ=0x4
[   37.751796] sd 0:0:0:0: [sda] tag#17 CDB: opcode=0x88 88 00 00 00 00 01 d1 a0 bf f8 00 00 00 08 00 00
[   37.751802] print_req_error: I/O error, dev sda, sector 7811940344
[   37.751860] sd 0:0:0:0: [sda] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   37.751870] sd 0:0:0:0: [sda] tag#18 Sense Key : 0x5 [current]
[   37.751878] sd 0:0:0:0: [sda] tag#18 ASC=0x21 ASCQ=0x4
[   37.751888] sd 0:0:0:0: [sda] tag#18 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 b7 f8 00 00 00 08 00 00
[   37.751893] print_req_error: I/O error, dev sda, sector 7814035448
[   41.401740] sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   41.401751] sd 0:0:0:0: [sda] tag#1 Sense Key : 0x5 [current]
[   41.401760] sd 0:0:0:0: [sda] tag#1 ASC=0x21 ASCQ=0x4
[   41.401772] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 a0 bf f8 00 00 00 08 00 00
[   41.401779] print_req_error: I/O error, dev sda, sector 7811940344
[   41.401787] Buffer I/O error on dev sda2, logical block 973870847, async page read
[   44.791942] sd 0:0:0:0: [sda] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   44.791969] sd 0:0:0:0: [sda] tag#12 Sense Key : 0x5 [current]
[   44.791991] sd 0:0:0:0: [sda] tag#12 ASC=0x21 ASCQ=0x4
[   44.792020] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 b7 f8 00 00 00 08 00 00
[   44.792035] print_req_error: I/O error, dev sda, sector 7814035448
[   44.792051] Buffer I/O error on dev sda3, logical block 261887, async page read
[  195.894269] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
[  195.894289] sd 0:0:0:0: [sda] Sense not available.
[  195.894554] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[  195.894572] sd 0:0:0:0: [sda] Sense not available.
[  195.894770] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[  195.894790] sd 0:0:0:0: [sda] 4096-byte physical blocks
[  195.894992] sd 0:0:0:0: [sda] Write Protect is on
[  195.895014] sd 0:0:0:0: [sda] Mode Sense: 60 66 f8 df
[  196.394606] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
[  196.394627] sd 0:0:0:0: [sda] Sense not available.
[  196.394886] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[  196.394905] sd 0:0:0:0: [sda] Sense not available.
[  196.900986] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
[  196.901008] sd 0:0:0:0: [sda] Sense not available.
[  196.901273] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[  196.901292] sd 0:0:0:0: [sda] Sense not available.
[  197.404230] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
[  197.404250] sd 0:0:0:0: [sda] Sense not available.
[  197.404513] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[  197.404533] sd 0:0:0:0: [sda] Sense not available.
[  197.406391] sd 0:0:0:0: [sda] Write Protect is off
[  197.406414] sd 0:0:0:0: [sda] Mode Sense: 48 4f 4d 45
[  197.904353] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00
[  197.904374] sd 0:0:0:0: [sda] Sense not available.
[  197.904634] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00
[  197.904652] sd 0:0:0:0: [sda] Sense not available.
b3 ~ #

A few more questions have popped up while revisiting my Bubba-based NAS setup, which includes three B3s - one from Excito with 2TB disk and two newer from Canada with 4TB disks, as well as a retired B2).

Would be grateful for any advice on these questions:

• Is it possible to still find the original Excito installers online? Both for the original pre-3TB version and for the later 3TB version? (I do have a zip file from 2021 containing a file intall/version = "2.4.1.1")
• Is there a detailed instruction somewhere for how to remove the internal disk? I am still struggling with this .
• Is the WiFi functionality hosted on its own board, separate from the mainboard, such that it may be moved from one unit to another, or is it integrated on the mainboard? (The two B3s which I ordered from Canada were supposed to be equipped with WiFi and intended to replace my first B3, but they came with no antennas (only predrilled holes) and the WiFi functionality is disalbed and greyed out in the WebUI. Wondering if it would be possible to move the WiFi from my first B3 to one of my newer ones...