disk/storage_device_{} fails on a un-partitioned disk

[jeremyszu]

* Steps to reproduce
$ /usr/lib/plainbox-provider-checkbox/bin/storage_test.py sdb
Testing disk sdb
identified as a disk...
ERROR: No partitions found on device /dev/sdb

* Description
The system is installed on sda.
```
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 64.8M 1 loop /snap/gtk-common-themes/1514
loop1 7:1 0 51M 1 loop /snap/snap-store/498
loop2 7:2 0 97.9M 1 loop /snap/core/10444
loop3 7:3 0 55.4M 1 loop /snap/core18/1932
loop4 7:4 0 217.9M 1 loop /snap/gnome-3-34-1804/60
loop5 7:5 0 162.9M 1 loop /snap/gnome-3-28-1804/145
loop6 7:6 0 118.4M 1 loop /snap/chromium/1424
loop7 7:7 0 55.4M 1 loop /snap/core18/1944
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512.1M 0 part /boot/efi
├─sda2 8:2 0 4.2G 0 part
└─sda3 8:3 0 461G 0 part /
sdb 8:16 0 465.8G 0 disk
sr0 11:0 1 1024M 0 ro
```

The sdb is a empty device.

If checkbox expects there are some partitions could be found then checkbox needs to create them first.
If checkbox would like to check the system partitions then checkbox needs to know which storage is using for booting.

[Sylvain Pineau (sylvain-pineau)]

I understand it can be annoying, but we won't partition anything from that job. Just ignore or skip that test.

[jeremyszu (os369510)]

@Alex,

As our discussion, please format drives in something like prepare-checkbox?

[Alex Tu (alextu)]

with this MP(https://gitlab.com/canonical-mainstream/prepare-checkbox-sanity/-/merge_requests/1), the 2nd disk on FIO-PIL-C9_202005-27873 can be recognized well.
But it failed with `sudo bonnie++ -d /mnt -u root -r 8000` but passed with `sudo bonnie++ -d /mnt -u root -r 800`

ubuntu@CANONICALID:~$ free -h
              total used free shared buff/cache available
Mem: 62Gi 830Mi 60Gi 377Mi 1.2Gi 60Gi
Swap: 2.0Gi 0B 2.0Gi

[Alex Tu (alextu)]

by following #3,
this is the latest 100 lines of `sudo strace -t bonnie++ -d /mnt -u root -r 8000`
https://paste.ubuntu.com/p/MXP59dhQ68/

So, looks there's something wrong with the target storage.
I prefer to skip the case of #3, it looks a single hardware issue.

[jeremyszu (os369510)]

https://bugs.launchpad.net/plainbox-provider-pc-sanity/+bug/1905378