Description

This article shows one of the method to clear alarm 'Host 0 Disk 2 Labelled incorrectly'.

Symptoms

user@lab> show system alarms no-forwarding

 

1 alarms currently active

Alarm time        Class Description

2024-03-01 07:14:24 PST Minor Host 0 Disk 2 Labelled incorrectly

 

SSDs are detected which means disk is working fine. If there is a disk failure or hardware issue, the system would have thrown major error. 

 

user@lab> show chassis hardware detail no-forwarding

 

Hardware inventory:

 sda  100030 MB SFSA100GM2AK4TO-  000060214858970000CD Solid State Disk

 sdb  100030 MB SFSA100GM2AK4TO-  000060214858970000D4 Solid State Disk

 

Doing a 'request system snapshot' will not clear the alarm 'Host 0 Disk 2 Labelled incorrectly'.

 

user@lab> request system snapshot 

-------------------------------

node: re0

-------------------------------

e2label: Input/output error while trying to open /dev/sdb2

Couldn't find valid filesystem superblock.

 

start shell user root

[vrf:none] user@lab:~# journal ctl -a

Mar 07 03:05:27 lab kernel: [0;1;31m[0;1;39m[0;1;31mprint_req_error: I/O error, dev sdb, sector 0 flags 801[0m[m

Mar 07 03:05:27 lab kernel: sd 1:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK[m

Mar 07 03:05:27 lab kernel: sd 1:0:0:0: [sdb] tag#7 CDB: Read(10) 28 00 02 86 48 00 00 00 20 00[m

Mar 07 03:05:27 lab kernel: [0;1;31m[0;1;39m[0;1;31mprint_req_error: I/O error, dev sdb, sector 42354688 flags 80700[0m[m

Mar 07 03:05:27 lab kernel: [0;1;31m[0;1;39m[0;1;31mBuffer I/O error on dev sdb5, logical block 0, async page read[0m[m

Mar 07 03:05:27 lab kernel: [0;1;31m[0;1;39m[0;1;31mBuffer I/O error on dev sdb2, logical block 0, async page read[0m[m

Mar 07 03:05:27 lab kernel: [0;1;31m[0;1;39m[0;1;31mBuffer I/O error on dev sdb7, logical block 0, async page read[0m[m

 

Solution

Please take a maintenance window, format the sdb disk and perform snapshot.

 

start shell user root

[vrf:none] user@lab:~# mkfs.vfat /dev/sdb1         

mkfs.fat 4.1 (2017-01-24)

[vrf:none] user@lab:~# mkfs.vfat /dev/sdb2

mkfs.fat 4.1 (2017-01-24)

[vrf:none] user@lab:~# exit

 

user@lab> show system snapshot        

-------------------------------

node: re0

-------------------------------

e2label: Bad magic number in super-block while trying to open /dev/sdb2

Current snapshot device: /dev/sdb

Partitions doesn't exist

Looks like snapshot operation was not performed

sfdisk: /dev/sdb: does not contain a recognized partition table

 

user@lab> request system snapshot 

-------------------------------

node: re0

-------------------------------

e2label: Bad magic number in super-block while trying to open /dev/sdb2

........

Starting Snapshot in device /dev/sdb

List of software versions getting copied to Snapshot...

[1] junos-evo-install-acx-f-x86-64-23.2R1-S1.8-EVO

........

........

Software Snapshot completed.

 

user@lab> show system snapshot 

-------------------------------

node: re0

-------------------------------

Current snapshot device: /dev/sdb

Snapshot boot device: sdb

List of installed version(s) in Snapshot boot device sdb:

 

[1] -> junos-evo-install-acx-f-x86-64-23.2R1-S1.8-EVO - [2024-03-15 11:07:36]

 

  '-' running version

  '>' next boot version after upgrade/downgrade

  '<' rollback boot version

 

user@lab>

 

If system does not allow format and alarm does not clear, then based on investigation confirm whether it is a hardware. If confirmed, then provide an RMA for the faulty part.

Additional checks that can be performed:
1) Check whether /dev/sdb is present in output of lsblk
2) Check if "smartctl -i /dev/sdb" is successful. In the example below, /dev/sdb was unresponsive, RE restart didn't help and eventually this RE had to be replaced.

[vrf:none] root@rs1:~# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop15   7:15   0 143.9M  1 loop /run/initramfs/uswitch/data/hashes/f2e8e2a08fe41033a68a1150a11e802d1e6ceb81
loop1    7:1    0 548.6M  1 loop /run/initramfs/uswitch/data/hashes/43e582c14174eb935d8a2b5b412aea8dadc18caa
loop13   7:13   0   4.8M  1 loop /run/initramfs/uswitch/data/hashes/0ef038cd3fded4c03d2cd27bdeb47a0b5e52a9b0
loop11   7:11   0   7.1M  1 loop /run/initramfs/uswitch/data/hashes/0aeb289dfcadc2c5b1608166fd450c869e64d687
loop8    7:8    0  33.1M  1 loop /run/initramfs/uswitch/data/hashes/c7bd2af50f557a614b5239d97ed0d570296422eb
loop6    7:6    0   9.7M  1 loop /run/initramfs/uswitch/data/hashes/34bf3101d6f443f900e1842bbd3e9077d13d9069
loop4    7:4    0  11.4M  1 loop /run/initramfs/uswitch/data/hashes/6bf64dbe9e54550105934fb2ed99572ade15c026
loop16   7:16   0   9.4G  0 loop /tmp/snapshot/data/var/external
loop2    7:2    0    28M  1 loop /run/initramfs/uswitch/data/hashes/7a47afa9c45ee0b3d9c9498e9132e5a924511c03
loop14   7:14   0     4K  1 loop /run/initramfs/uswitch/data/hashes/5ace20f206905d4b3aba875872181940f0834ed7
loop0    7:0    0    15G  0 loop /data/var/external
loop12   7:12   0   4.4M  1 loop /run/initramfs/uswitch/data/hashes/fbaf9f26c4aa04989a3b679bca61bca5040a8d17
loop9    7:9    0   8.2M  1 loop /run/initramfs/uswitch/data/hashes/74184abbbc7eb978144856976e322dbdf2cc0b90
loop10   7:10   0  35.9M  1 loop /run/initramfs/uswitch/data/hashes/4573de814ba610c712c61ac5d1f02428e8dbc7a1
sda      8:0    0 186.3G  0 disk
|-sda4   8:4    0     1K  0 part
|-sda2   8:2    0    32G  0 part /soft
|-sda7   8:7    0 146.1G  0 part /var
|-sda5   8:5    0     3G  0 part /soft/uswitch
|-sda3   8:3    0     4G  0 part
|-sda1   8:1    0   199M  0 part /boot
`-sda6   8:6    0     1G  0 part /data/config
loop7    7:7    0  58.7M  1 loop /run/initramfs/uswitch/data/hashes/47b520605bdfcc235d23dc2f2dbd65423971d015
loop5    7:5    0  46.6M  1 loop /run/initramfs/uswitch/data/hashes/c30354eaf9573fa8d28a3004dc1dc462650dabae
loop3    7:3    0  35.5M  1 loop /run/initramfs/uswitch/data/hashes/c016ac5b62573dc443b6282732202e78e3f543d9
[vrf:none] root@rs1:~# smartctl -i /dev/sdb
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.28-WR2.2.1_standard-gad6c183] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[vrf:none] root@rs1:~# smartctl -T permissive -i /dev/sdb
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.28-WR2.2.1_standard-gad6c183] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Short INQUIRY response, skip product id

[vrf:none] root@rs1:~#

Modification History

22-07-24: Minor formatting changes, and expanded solution.
5/4/2024 Edited