I am trying to install the 2021 ISO on a computer with multiple OS already installed (IDE 150GB HDD),
Hello,
Parodper, le jeu. 19 août 2021 16:58:26 +0200, a ecrit:
I am trying to install the 2021 ISO on a computer with multiple OS already >> installed (IDE 150GB HDD),
Note that as our FAQ says, our current IDE driver is limited to LBA28,
i.e. 128GB. It cannot access beyond that limit on the disk.
Samuel
However QEMU is too slow (takes quite a few hours to reach partman)
Please be very precise in explaining your problem, I couldn't reproduce
it in qemu. I tried in the debian installer:
- booted with a 10G disk
- use manual partitioning
- have it create a partition table
- create a 1G primary partition (assigned automatically for /)
- create a 1G primary partition (assigned automatically for /home)
- create a 1G primary partition (assigned automatically for /usr)
- create a logical partition with the rest (assigned automatically for /var)
and it proceeded just fine.
Remember that the devil is always in the details.
As an aside note, I was testing that second problem on QEMU, and in the
emulator I didn't have to call MAKEDEV to load the image from the partition. >> Any idea about that?
I don't understand what you mean, please be more precise.
Samuel
Parodper, le jeu. 19 août 2021 16:58:26 +0200, a ecrit:
However QEMU is too slow (takes quite a few hours to reach partman)
Did you make sure to enable kvm?
Samuel
- With a 20G test.qcow2: I created 3 1G primary partitions set as «do not use» and a 1G logical partition. The rest of the free space disappeared, and reappeared when I deleted the logical partition.
Aug 19 17:30:16 main-menu[1811]: (process:15055): /bin/partman: line 113: depmod: not found
Aug 19 17:30:16 main-menu[1811]: (process:15055): cat: can't open '/proc/modules': No such file or directory
Aug 19 17:30:16 main-menu[1811]: (process:15055): cat: can't open '/proc/modules': No such file or directory
Aug 19 17:30:16 main-menu[1811]: (process:15055): cat: can't open '/proc/modules': No such file or directory
Aug 19 17:30:16 main-menu[1811]: (process:15055): Cannot create FIFO: No space left on device
whenever they derive the slightest from the "just press enter to get
the default".
Parodper, le jeu. 19 août 2021 20:01:37 +0200, a ecrit:
Aug 19 17:30:16 main-menu[1811]: (process:15055): Cannot create FIFO: No
space left on device
That caught my eye: how much RAM does your machine have?
Optimizing the memory usage of the initrd is still on the TODO list.
Samuel
Samuel Thibault, le jeu. 19 août 2021 20:42:05 +0200, a ecrit:
whenever they derive the slightest from the "just press enter to get
the default".
(I meant deviate*)
Samuel
Parodper, le ven. 20 août 2021 20:15:09 +0200, a ecrit:
- Create 5 logical partitions. On the fifth partition the drive disappears
Ok, that I could reproduce :)
It seems the issue is merely that there are not enough free inodes in
the / FS, I'll fix that.
- Create 5 logical partitions. On the fifth partition the drive disappears
* The partition with the ISO would be hd0s6 (I did dd if=debian-hurd.iso
of=/dev/sda6 on Linux), but if I try to write /dev/hd0s6 directly it fails, >> and trying to mount the partition manually fails with a «Input Output
Error».
Ah! I hadn't understood that you were doing that.
You cannot do such thing with logical partitions: the dd call will wipe
the first sector which contains the logical partition chain cell. You
have to use a primary partition to be able to wipe out the first sector. Alternately, since isofs doesn't actually use the first sectors, you can
skip one and seek one, to avoid wiping the logical partition chain cell.
* Installer asks for drivers, choose to manually select the drive.
* Then I change to TTY2, cd /dev and ./MAKEDEV hd0s6
This last step was not necessary in QEMU, that is why I was asking.
That shouldn't be necessary at all, /dev is getting filled with device translator entries during the boot process, see attached snapshot.
O 19/08/21 ás 20:34, Samuel Thibault escribiu:
* The partition with the ISO would be hd0s6 (I did dd if=debian-hurd.iso of=/dev/sda6 on Linux), but if I try to write /dev/hd0s6 directly it fails,
and trying to mount the partition manually fails with a «Input Output Error».
Ah! I hadn't understood that you were doing that.
You cannot do such thing with logical partitions: the dd call will wipe
the first sector which contains the logical partition chain cell. You
have to use a primary partition to be able to wipe out the first sector. Alternately, since isofs doesn't actually use the first sectors, you can skip one and seek one, to avoid wiping the logical partition chain cell.
Tried using «dd bs=512 skip=1 seek=1 conv=notrunc if=debian-hurd.iso of=/dev/sda8». It still needs MAKEDEV to mount it, and does not recognize the partition table.
* Installer asks for drivers, choose to manually select the drive.
* Then I change to TTY2, cd /dev and ./MAKEDEV hd0s6
This last step was not necessary in QEMU, that is why I was asking.
That shouldn't be necessary at all, /dev is getting filled with device translator entries during the boot process, see attached snapshot.
I do get the same things on boot (see https://i.imgur.com/XGImhqK.jpg), but when I try to do «mount -t iso9660 /dev/hd08 /mnt», or even just «head /dev/hd0», I get a Input/Output error.
PD: Is there any way to tell the translators to be more verbose? Something like 'echo OPTIONS=--verbose >> /etc/translator.conf'?
Parodper, le lun. 23 août 2021 08:40:17 +0200, a ecrit:
O 19/08/21 ás 20:34, Samuel Thibault escribiu:
Tried using «dd bs=512 skip=1 seek=1 conv=notrunc if=debian-hurd.iso
of=/dev/sda8». It still needs MAKEDEV to mount it, and does not recognize >> the partition table.
I cannot reproduce the issue. In my test I could was able to just
provide the /dev/hd0s5 path and it'd just work.
I do get the same things on boot (see https://i.imgur.com/XGImhqK.jpg), but >> when I try to do «mount -t iso9660 /dev/hd08 /mnt», or even just «head* Installer asks for drivers, choose to manually select the drive.
* Then I change to TTY2, cd /dev and ./MAKEDEV hd0s6
This last step was not necessary in QEMU, that is why I was asking.
That shouldn't be necessary at all, /dev is getting filled with device
translator entries during the boot process, see attached snapshot.
/dev/hd0», I get a Input/Output error.
Ah, you mean that there really are some existing entries but they don't
work, and the entries created by MAKEDEV happen to seem to work?
About /dev/hd0 itself it's very surprising that it'd get Input/Output
errors since the entry that MAKEDEV create is strictly the same as the existing one.
As for /dev/hd0s8, d-i indeed uses the parted layer to access the
partition, while MAKEDEV creates an entry that uses the kernel-level
driver for partitions. It is very surprising that the latter would
work better than the former, since only the former is maintained. When
you open your disk with parted from a Linux system, does it complain
somehow?
PD: Is there any way to tell the translators to be more verbose? Something >> like 'echo OPTIONS=--verbose >> /etc/translator.conf'?
There is no such global thing since translators are allowed to be
implemented whatever the way they prefer. But you can start translators
by hand to make sure to get their output:
settrans -a /dev/hd0s8 /hurd/storeio -T typed part:8:device:hd0
Samuel
I still get the unknown partition table, and doing head /dev/hd0s1 fails
with a «Input/Output error». head /dev/hd0 works fine.
Tried doing settrans -a /dev/hd0s1 /hurd/storeio -T typed part:1:device:hd0; head /dev/hd0s1 and still getting IO error. The command also ends and does not output any error.
Side note, ls /dev is very slow (after a while I just cancel it), while echo /dev/* is instantaneous.
A quick calculation shows none of those are multiples of 4096.
Parodper, le sam. 28 août 2021 14:35:16 +0200, a ecrit:
A quick calculation shows none of those are multiples of 4096.
Then that's most probably why.
I don't know if we could just drop the checks. You said that it was installing fine with the MAKEDEV-created entries? Possibly the checks
are overzealous.
Samuel
Now that I think about it, it might be caused by the drive size
(150GB), because the 80GB slave driver appears fine, and it also has
a logical partition.
O 28/08/21 ás 11:33, Samuel Thibault escribiu:
Parodper, le sam. 28 août 2021 10:56:07 +0200, a ecrit:
I still get the unknown partition table, and doing head /dev/hd0s1 fails with a «Input/Output error». head /dev/hd0 works fine.
Tried doing settrans -a /dev/hd0s1 /hurd/storeio -T typed part:1:device:hd0;
head /dev/hd0s1 and still getting IO error. The command also ends and does
not output any error.
Looking at hurd/libstore/part.c, I see
if (run.start % source->block_size != 0)
err = EIO;
if (run.length % source->block_size != 0)
err = EIO;
could it be that your partitions are not aligned on 4096 bytes?
/dev/sda1 : start= 63, size= 4208967, type=b, bootable #FreeDOS partition
/dev/sda2 : start= 4209030, size= 71682030, type=a6 #OpenBSD partition
/dev/sda3 : start= 75891060, size= 30716280, type=81 #Minix3 partition
/dev/sda4 : start= 106607401, size= 205967877, type=f #Extended partition
/dev/sda5 : start= 106607403, size= 40965687, type=6 #HaikuOS
Something that I just noticed on this test was that, on boot, the kernel (I guess?) showed the hd0 disk and all the partitions.
The thing is parted does not recognize the partition table
Parodper, le sam. 28 août 2021 14:35:16 +0200, a ecrit:
/dev/sda1 : start= 63, size= 4208967, type=b, bootable #FreeDOS >> partition
/dev/sda2 : start= 4209030, size= 71682030, type=a6 #OpenBSD
partition
/dev/sda3 : start= 75891060, size= 30716280, type=81 #Minix3 partition
/dev/sda4 : start= 106607401, size= 205967877, type=f #Extended
partition
/dev/sda5 : start= 106607403, size= 40965687, type=6 #HaikuOS
I tried building this partition table, and didn't have any problem.
The thing is parted does not recognize the partition table
Does it have trouble when run from other OSes as well? Then I'd say
debug it from there.
Samuel
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 90:07:00 |
| Calls: | 6,658 |
| Files: | 12,203 |
| Messages: | 5,334,090 |
