Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: Driiper on November 28, 2015, 09:48:28 PM
-
Hello, ive customized the tinycore iso and ive got it to work in both Virtualbox and VMWARE, attaching it as an IDE disk (VHD file)
But i cannot seem to be able to get tinycore to recognize the hard drive in Hyper-V
ive tried 6.4.1 and 5.3. None of them are working.
Anyone know what i can do to solve this?
-
As per a forum search on "hyper", others seem to have managed it?
-
http://forum.tinycorelinux.net/index.php/topic,18039.msg109262.html#msg109262
v6.1rc reissued with hv_storvsc in the base - please test and let us know if it works
I've searched the forums already and can't really seem to find any thread related to getting 6.x to work.
I howeer found the above which should indicate that it "should" work?
-
The very next post by user Hadlock says:
This is resolved in the latest RC of 6.1 please close thanks
-
Okay, so i tested all following versions:
6.0
6.1
6.2
6.3
6.4
6.4.1 (Which is started out with)
All of the above worked except the most recent (6.4.1)
Guess thats called being unlucky ..
-
Did you get an error message from 6.4.1?
What command are you using to attach the hd?
-
I'm simply checking if the disks are listed with fdisk -l.
All disks (both IDE and SCSI) were listed in the working versions. The list was however empty in 6.4.1
-
When attempting to bind home and opt directory to sda1 it does not seem to work as intented.
The disks are "identified" by the OS before after the bootup.
You have probably already noticed that i'm clueless of what is happening here. I'm trying though..
(http://i.imgur.com/jcSNkUf.png)
-
I'm guessing you're attaching the hd with a command in bootlocal.sh, but this has not been processed before the boot sequence attempts to mount the persistant home?
-
In my virtualbox, the mounts happened out of the box without any entries.
I'm not sure how tinycore handles mounting the hard drives by default as it worked without any configurations.
What i know: i must have some kinda access to the drive at all times since it loads the kernel from /boot which are located on sda1
Where would you suggest i configure the drive to be mounted "pre-boot" ?
-
Oh, the module indeed disappeared from 6.4.1. I guess that was around the server break. No other files missing, checked.
Regarding the error in your screenshot: the driver was loaded, but was waiting for something, and so the HD was not detected in time. This could mean a bug in either the driver or in the host HyperV.
-
hv_storvsc module added back into base and 6.4.1 iso's/distribution files reposted
-
Oh, the module indeed disappeared from 6.4.1. I guess that was around the server break. No other files missing, checked.
Regarding the error in your screenshot: the driver was loaded, but was waiting for something, and so the HD was not detected in time. This could mean a bug in either the driver or in the host HyperV.
Is there any way of "forcing" a wait for the drives to be mounted?
After boot i get the following message aswell:
udevadm settle - timeout of 5 seconds reached, the event queue contains:
/sys/devices/LNXSYSTM:00/LNXSYSBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_1/host2/target2:0:0/2:0:0:0/block/sda/sda1 (1344)
by the way, if it helps: my boot options are:
kernel /boot/vmlinuz loglevel=3 opt=sda1 home=sda1 tce=sda1
-
I added the waitusb bootflag to grub and was successfully able to boot with mounted drives.
This works but are not optimal for the boot time. Is there any way for specifically waiting for a device?
-
waitusb=5:UUID="01234567-89ab-cdef-0123-456789abcdef"
Or
waitusb=5:LABEL="*YOUR*DISK*LABEL*"
-
waitusb=5:UUID="01234567-89ab-cdef-0123-456789abcdef"
Or
waitusb=5:LABEL="*YOUR*DISK*LABEL*"
Thanks! This works :)
-
Hi,
When installing TC 7.1 or 7.2 in Hyper-V Win10 Pro I got similar errors than the OP
"udevadm settle - timeout of 5 seconds reached...
/sys/devices/.../block/sda
..."
(see screen shot attached)
6.4.1 installed fine.
Please help.