Lsblk: /dev/sda?: not a block device
-
Does this only happen on specific devices?
I ask because I’ve been testing imaging since working on many different changes. I haven’t seen this pop up.
-
I got it on a Toshiba Satellite notebook: M305D-S4830, an older computer with a K8T Neo-V MSI mainboard and a VirtualBox virtual machine.
-
just tried it with a new hard drive (on the old MSI computer) and the update from a few minutes ago - same /dev/sda? error
-
please update and try again, does the error still occur?
-
This time after updating…
trying to register older MSI computer with new hard drive connected to SATA (configured as SATA and not RAID)
Error: could not stat device mklabel - No such file or directory
** An error has been detected **
Failed to initialize disk
** Computer will reboot in 1 minute **
-
when you say “new hard drive”, do you mean a blank one? Or just a “newer” one that has some partitions on it ?
-
[quote=“Wayne Workman, post: 46765, member: 28155”]when you say “new hard drive”, do you mean a blank one? Or just a “newer” one that has some partitions on it ?[/quote]
It’s actually new and blank with no partitions or data
-
After a quick FAT32 format, the system seems to work. I formatted the blank drive and was able to register the host and deploy Windows 7 to the hard drive. It also registers the host when the drive is formatted for Linux.
-
Are you using 1.2.0 ??
-
[quote=“Wayne Workman, post: 46802, member: 28155”]Are you using 1.2.0 ??[/quote]
Yes - 1.2.0 revision 3356 - using Debian 7.8.0
-
This post is deleted! -
Then this is probably a Tom question.
I know he’s been doing A LOT of work with how HDDs are handled lately.
-
Just ran into this too. Giving it a poke.
EDIT:
The drive had Windows 10 on it before, and it worked. After running a fast wipe through FOG, I could no longer get any tasks to work (same error as above). More fiddling inbound.
