WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Can't see the volume that I booted from on Google Compute Engine  (Read 2680 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9543
Re: Can't see the volume that I booted from on Google Compute Engine
« Reply #15 on: October 26, 2015, 08:44:44 PM »
You need to use linux-3.16.6-patched.txz and config-3.16.6-tinycore64 from 6.x/x86/release/src/kernel

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9587
Re: Can't see the volume that I booted from on Google Compute Engine
« Reply #16 on: October 27, 2015, 01:28:32 AM »
You don't need to compile a new kernel - just remaster the module from scsi-3.16.6-tinycore64.tcz into your initrd.

Unpack the scsi extension, copy the virtio module into place, update depmod files. The wiki has more detail on this.
The only barriers that can stop you are the ones you create yourself.

Offline as

  • WikiUser
  • *
  • Posts: 29
Re: Can't see the volume that I booted from on Google Compute Engine
« Reply #17 on: October 27, 2015, 04:27:24 PM »
>> just remaster the module from scsi-3.16.6-tinycore64.tcz into your initrd.

OK great this worked thanks.  I can now see the hard disk on Google Compute Engine.

Currently however it only recognises the disk is I manually load the virtio_scsi module with insmod.  It doesn't seem to automatically get loaded.

What is the correct way to ensure the module is loaded at boot time?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9587
Re: Can't see the volume that I booted from on Google Compute Engine
« Reply #18 on: October 28, 2015, 12:53:10 AM »
If you updated the depmod files, it would get loaded if a device matching it was present.

Otherwise, load it in bootsync.sh.
The only barriers that can stop you are the ones you create yourself.