[2.3, HWTv2] badblocks test has 17 badblocks, but test shows as passed.

Bug #1733923 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Lee Trager
2.3
Fix Released
High
Lee Trager

Bug Description

Badblock test showed as it had "passed", but after checking the log it actually had failed:

Running command: sudo -n badblocks -b 4096 -v -f -n /dev/sdb

Checking for bad blocks in non-destructive read-write mode
From block 0 to 732566645
Testing with random pattern: 49052
65718
65720
65722
65731
66004
66018
110009837
110010192
110010198
110010221
110010558
110010893
111574244
111574248
111574251
111574256
Pass completed, 17 bad blocks found. (17/0/0 errors)

Other things that need to be improve:

Improve the logging similarly to the smartctl logs

INFO: Running command: sudo -n badblocks -b 4096 -v -f -n /dev/sdb

FAILURE: Test FAILED! 17 bad blocks found (17/0/0 errors)
SUCCEES: Test PASSED

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

Checking for bad blocks in non-destructive read-write mode
From block 0 to 732566645
Testing with random pattern: 49052
65718
65720
65722
65731
66004
66018
110009837
110010192
110010198
110010221
110010558
110010893
111574244
111574248
111574251
111574256

Related branches

Changed in maas:
milestone: none → 2.4.x
milestone: 2.4.x → 2.4.0alpha1
status: New → Triaged
importance: Undecided → High
assignee: nobody → Lee Trager (ltrager)
description: updated
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.