Forum Discussion
Deploying D4IoT Sensor to ThinkEdge SE40 - No Root Filesystem
- Jul 11, 2022
In case somebody else runs in to this problem I managed to find a solution in the end.
Basically, the problem is that when you boot from the installation USB media, it names the installation media sda and the internal harddrive sdb in /dev. This properly wouldn’t be the case if you installed from an optical media like AdiWeisberg suggested – but I didn't have access to one and I must admit it's a decade since i've used an optical disk for installation.
So the seed files for autopartitioning only looks for sda and not sdb.
So, by changing line 6 in the seed file corresponding to the solution you want to install (in my case the 100 GB solution, named: preseed/laptop-storage-layout.seed) from /dev/sda to /dev/sdb it installs fine.Edit:
Line 107 in preseed/general.seed should be corrected from /dev/sda to /dev/sdb as well. Else it will install the bootsector on the installation media instead of the installation drive. So when you remove the installation media it won't boot as i just figured out 😉
Hope this can help somebody else.
Hi AdiWeisberg,
Thank you for your reply.
I'm trying to install the OT Sensor to a ThinkEdge SE40 with these instructions: https://docs.microsoft.com/en-us/azure/defender-for-iot/organizations/how-to-install-software?tabs=sensor
I've attached log from failed installation as well.
(Maximum monitoring bandwidth 100 Mb/sec
Maximum monitored assets 800
CPU 4
Memory 8 GB
Storage 100 GB (150 IOPS)
- jeharaJul 04, 2022Copper Contributor
Hi AdiWeisberg,
Yes and I also tried the smaller architectures and even the bigger ones.
It works fine when I install it in a VM.
- AdiWeisbergJul 04, 2022
Microsoft
Are you using USB or portable DVD for the installation? I suggest using a portable DVD. and starting over per the defined steps. you can raise a technical support ticket via the azure portal in case your installation keeps failing. support will help with the troubleshooting.- jeharaJul 05, 2022Copper ContributorOk, I'll raise a technical support ticket in Azure Portal.