Re: slint 2tb limit
The slint dvd turned into a coaster but I finally got an install on gpt to work. A three partition arrangement with boot being the first partition and having bios_grub set on. A second partition with type linux, and a third partition with type swap. With that setup, I was able to install lilo to the mbr it will not install to the superblock of the linux partition though. That boot partition was set primary and was 2MIB in size. I ended up with a 4GB swap partition and had a 2.8T linux partition by the time it was all done. The gpt install is more complex, but doing it gets you past the 2TB limit. On Thu, 15 Mar 2018, Linux for blind general discussion wrote: Date: Thu, 15 Mar 2018 16:58:35 From: Linux for blind general discussion To: blinux-list@redhat.com Subject: Re: slint 2tb limit Hello, Didier here. Could you please name yourself when you post, as this list does not name the sender and I am more comfortable being sure whom I speak to. Le 15/03/2018 ? 03:50, Linux for blind general discussion a ?crit?: although tools are on slint disks to handle gpt disks anyone attempting to have a gpt label on an efi disk will encounter insurmountable problems from lilo.? I was unable to install on a gpt disk with lilo the mbr was unuseable as a good place and the superblock of the / partition was also unuseable lilo threw errors in both cases. Well, there is no efi disks, only partitions of type EFI system partition aka ESP. A disk drive that has a GPT (GUID partition table) can include one or more ESP but this is optional. From your tests results I infer that lilo can't write the boot sector, neither on the MBR nor on the / partition of a disk equipped with GPT, if the / partition is greater the 2TB. I think that's because in this case: 1) the protective MBR is at the end of the disk, i.e. after the 2TB limit. 2) In case of the / partition this partition would need to be marked bootable, which is not possible AFAIK in case of GPT However lilo can write on the MBR of a GPT with partitions smaller that 2TB, I've done that many times and when using an UEFI firmware I even recommend to install both lilo and elilo, as this way the system can boot both in UEFI mode and in Legacy mode. ? In order to do this at all, I had to put a dos label on the hard drive and restrict myself to 2,044gb for / partition and I used 4gb for the swap partition as well. I assume that you actually you actually meant 2,044TB, is that right? Something else with lilo.? If I put the swap partition first and / as second partition lilo cannot install on the superblock of /dev/sda2 and cannot install on the mbr either.? So long as the / partition is first it's possible to install to the mbr and I have no idea if lilo will be able to install to the superblock of /dev/sda1 either since I didn't try that yet. I have no clue about this behavior, and unfortunately don't have a proper hardware at hand to test. Did you make the / partition bootable? Maybe it will be possible to take that 3rd tb and use it for a data partition eventually unless a tool can be used to break the dos barrier This is certainly what I would do. If a partition is not used for booting lilo won't care, at least if it is on another drive than the one on which lies the boot sector, and maybe even if all partitions are on the same drive on the condition that the big partition is the last one. Anyway if you use two separate drives there should be no issue. The only way I know to break the dos barrier is to format the drive with sectors of more than 512 bytes, at least 1024. But I am not sure it's worthwhile and never tried. Other label types are available than gpt and dos I just haven't studied them all that much except for ntfs just yet. Feel free to experiment and report the results, even though I am not very optimistic on lilo's ability to work with partition tables other than dos or gpt. Thanks for reporting so far. Best regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
Hello, Didier here. Could you please name yourself when you post, as this list does not name the sender and I am more comfortable being sure whom I speak to. Le 15/03/2018 à 03:50, Linux for blind general discussion a écrit : > although tools are on slint disks to handle gpt disks anyone attempting to > have a gpt label on an efi disk will encounter insurmountable problems from > lilo. I was unable to install on a gpt disk with lilo the mbr was unuseable > as a good place and the superblock of the / partition was also unuseable lilo > threw errors in both cases. Well, there is no efi disks, only partitions of type EFI system partition aka ESP. A disk drive that has a GPT (GUID partition table) can include one or more ESP but this is optional. >From your tests results I infer that lilo can't write the boot sector, neither >on the MBR nor on the / partition of a disk equipped with GPT, if the / >partition is greater the 2TB. I think that's because in this case: 1) the protective MBR is at the end of the disk, i.e. after the 2TB limit. 2) In case of the / partition this partition would need to be marked bootable, which is not possible AFAIK in case of GPT However lilo can write on the MBR of a GPT with partitions smaller that 2TB, I've done that many times and when using an UEFI firmware I even recommend to install both lilo and elilo, as this way the system can boot both in UEFI mode and in Legacy mode. > In order to do this at all, I had to put a dos label on the hard drive and >restrict myself to 2,044gb for / partition and I used 4gb for the swap >partition as well. I assume that you actually you actually meant 2,044TB, is that right? > Something else with lilo. If I put the swap partition first and / as second > partition lilo cannot install on the superblock of /dev/sda2 and cannot > install on the mbr either. So long as the / partition is first it's possible > to install to the mbr and I have no idea if lilo will be able to install to > the superblock of /dev/sda1 either since I didn't try that yet. I have no clue about this behavior, and unfortunately don't have a proper hardware at hand to test. Did you make the / partition bootable? > Maybe it will be possible to take that 3rd tb and use it for a data partition > eventually unless a tool can be used to break the dos barrier This is certainly what I would do. If a partition is not used for booting lilo won't care, at least if it is on another drive than the one on which lies the boot sector, and maybe even if all partitions are on the same drive on the condition that the big partition is the last one. Anyway if you use two separate drives there should be no issue. The only way I know to break the dos barrier is to format the drive with sectors of more than 512 bytes, at least 1024. But I am not sure it's worthwhile and never tried. > Other label types are available than gpt and dos I just haven't studied them > all that much except for ntfs just yet. Feel free to experiment and report the results, even though I am not very optimistic on lilo's ability to work with partition tables other than dos or gpt. Thanks for reporting so far. Best regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
Didier here. First, the maths: Actually the numbers on each line of the fdisk output are, from left to right: partition beginning sector (512 bytes per sector) partition ending sector partition size in sectors partition size in another unit to make it human readable In this case the unit is a Tib i.e. 1,099,511,627,776 bytes The computed size in sectors is end-beginning+1, here: 5860531119-4198400+1=5856332720 585633272*512/1099511627776 roughly equals 2.7 so yes, this is correct. Now about the issue. In the installer the Linux partition is called by a script that use the output of fdisk -l. Unfortunately, fdisk fails in case of a DOS (with a MBR) partition table if the partition size is too big, with an error like: DOS partition table format can not be used on drives for volumes larger than 2199023255040 bytes for 512 bytes sectors. Use GUID partition table format (GPT). You didn't hear this error messages because the installer doesn't display it, but this indeed prevented to detect /dev/sda3 as a linux partition. So you need to convert the partition table of this drive to GPT. This can be done using gdisk. Of course you'll loose all data in it, so make back ups first as need be. I have checked that fdisk can read partition on a GPT drive, so after that hopefully Slint installation will work. Greetings, Didier Le 13/03/2018 à 23:50, Linux for blind general discussion a écrit : > Okay that last number before 2.7t on the fdisk output is correct. It doesn't > make sense to me that it's smaller than the number before it, but I checked > and what was supplied is accurate. > > On Tue, 13 Mar 2018, Linux for blind general discussion wrote: > >> Date: Tue, 13 Mar 2018 18:26:39 >> From: Linux for blind general discussion >> To: Linux for blind general discussion >> Subject: Re: slint 2tb limit >> >> output from: >> lsblk -o model,name,size,fstype >> wdc wd30ezrx-00d sda 2.7t >> sda1 2m ext4 >> sda2 2g swap >> sda3 2.7t >> ihas124 w sr0 3.4g iso9660 >> >> >> output from: >> fdisk -l|grep ^/ >> /dev/sda1 2048 6143 4096 2m bios boot >> /dev/sda2 6144 4198399 4192256 2g linux filesystem >> /dev/sda3 4198400 5860531119 5856332720 2.7t linux filesystem >> >> The last number on last line before 2.7t is probably wrong. I can try >> running second command again and see if result differs. >> On Mon, 12 Mar 2018, Linux for blind general discussion wrote: >> >>> Date: Mon, 12 Mar 2018 11:13:51 >>> From: Linux for blind general discussion >>> To: blinux-list@redhat.com >>> Subject: Re: slint 2tb limit >>> >>> Hello, >>> >>> Didier Spaier, Slint maintainer, here. >>> >>> Le 12/03/2018 ? 15:48, Linux for blind general discussion a ?crit?: >>>> So far as I can tell, slint appears to have a 2tb hard drive size limit. >>>> I tried it with a 3tb drive and hope I haven't permanently trashed the >>>> drive.? What happens with slint is you set up a swap partition on the >>>> drive and a linux partition and it doesn't matter what you use to do it >>>> either.? Once done, you run setup and get the message that slint can't >>>> find any partitions on the hard drive.? I have a bad compatibility >>>> situation here since technology is 24 years old and back in those years >>>> all that was known about was bios, efi and uefi didn't exist then.? Last >>>> bios flash update for AMD k8 athelon computers I think was 2006.? So, >>>> I'll see if I can rescue the 3tb drive with archlinux then go from there. >> >>> I haven't such a big drive to check but am a bit surprised of such a >>> limitation. >>> >>> To help investigate, could you please start again the installer, then >>> after log in as root instead of running setup type this command, then post >>> the output: >>> lsblk -o model,name,size,fstype >>> >>> And also please post the output of this other command: >>> fdisk -l|grep ^/ >>> >>> That should allow me to understand why the installer doesn't see the >>> partitions. >>> >>> Best regards, >>> >>> Didier >>> >>> ___ >>> Blinux-list mailing list >>> Blinux-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/blinux-list >> >> > ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
slint 2tb limit
although tools are on slint disks to handle gpt disks anyone attempting to have a gpt label on an efi disk will encounter insurmountable problems from lilo. I was unable to install on a gpt disk with lilo the mbr was unuseable as a good place and the superblock of the / partition was also unuseable lilo threw errors in both cases. In order to do this at all, I had to put a dos label on the hard drive and restrict myself to 2,044gb for / partition and I used 4gb for the swap partition as well. Something else with lilo. If I put the swap partition first and / as second partition lilo cannot install on the superblock of /dev/sda2 and cannot install on the mbr either. So long as the / partition is first it's possible to install to the mbr and I have no idea if lilo will be able to install to the superblock of /dev/sda1 either since I didn't try that yet. Maybe it will be possible to take that 3rd tb and use it for a data partition eventually unless a tool can be used to break the dos barrier. Other label types are available than gpt and dos I just haven't studied them all that much except for ntfs just yet. -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
[message was sent but didn't appear on the list, sending it again] Didier here. First, the maths: Actually the numbers on each line of the fdisk output are, from left to right: partition beginning sector (512 bytes per sector) partition ending sector partition size in sectors partition size in another unit to make it human readable In this case the unit is a Tib i.e. 1,099,511,627,776 bytes The computed size in sectors is end-beginning+1, here: 5860531119-4198400+1=5856332720 585633272*512/1099511627776 roughly equals 2.7 so yes, this is correct. Now about the issue. In the installer the Linux partition is called by a script that use the output of fdisk -l. Unfortunately, fdisk fails in case of a DOS (with a MBR) partition table if the partition size is too big, with an error like: DOS partition table format can not be used on drives for volumes larger than 2199023255040 bytes for 512 bytes sectors. Use GUID partition table format (GPT). You didn't hear this error messages because the installer doesn't display it, but this indeed prevented to detect /dev/sda3 as a linux partition. So you need to convert the partition table of this drive to GPT. This can be done using gdisk. Of course you'll loose all data in it, so make back ups first as need be. I have checked that fdisk can read partition on a GPT drive, so after that hopefully Slint installation will work. Greetings, Didier Le 13/03/2018 à 23:50, Linux for blind general discussion a écrit : > Okay that last number before 2.7t on the fdisk output is correct. It doesn't > make sense to me that it's smaller than the number before it, but I checked > and what was supplied is accurate. > > On Tue, 13 Mar 2018, Linux for blind general discussion wrote: > >> Date: Tue, 13 Mar 2018 18:26:39 >> From: Linux for blind general discussion >> To: Linux for blind general discussion >> Subject: Re: slint 2tb limit >> >> output from: >> lsblk -o model,name,size,fstype >> wdc wd30ezrx-00d sda 2.7t >> sda1 2m ext4 >> sda2 2g swap >> sda3 2.7t >> ihas124 w sr0 3.4g iso9660 >> >> >> output from: >> fdisk -l|grep ^/ >> /dev/sda1 2048 6143 4096 2m bios boot >> /dev/sda2 6144 4198399 4192256 2g linux filesystem >> /dev/sda3 4198400 5860531119 5856332720 2.7t linux filesystem >> >> The last number on last line before 2.7t is probably wrong. I can try >> running second command again and see if result differs. >> On Mon, 12 Mar 2018, Linux for blind general discussion wrote: >> >>> Date: Mon, 12 Mar 2018 11:13:51 >>> From: Linux for blind general discussion >>> To: blinux-list@redhat.com >>> Subject: Re: slint 2tb limit >>> >>> Hello, >>> >>> Didier Spaier, Slint maintainer, here. >>> >>> Le 12/03/2018 ? 15:48, Linux for blind general discussion a ?crit?: >>>> So far as I can tell, slint appears to have a 2tb hard drive size limit. >>>> I tried it with a 3tb drive and hope I haven't permanently trashed the >>>> drive.? What happens with slint is you set up a swap partition on the >>>> drive and a linux partition and it doesn't matter what you use to do it >>>> either.? Once done, you run setup and get the message that slint can't >>>> find any partitions on the hard drive.? I have a bad compatibility >>>> situation here since technology is 24 years old and back in those years >>>> all that was known about was bios, efi and uefi didn't exist then.? Last >>>> bios flash update for AMD k8 athelon computers I think was 2006.? So, >>>> I'll see if I can rescue the 3tb drive with archlinux then go from there. >> >>> I haven't such a big drive to check but am a bit surprised of such a >>> limitation. >>> >>> To help investigate, could you please start again the installer, then >>> after log in as root instead of running setup type this command, then post >>> the output: >>> lsblk -o model,name,size,fstype >>> >>> And also please post the output of this other command: >>> fdisk -l|grep ^/ >>> >>> That should allow me to understand why the installer doesn't see the >>> partitions. >>> >>> Best regards, >>> >>> Didier >>> >>> ___ >>> Blinux-list mailing list >>> Blinux-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/blinux-list >> >> > ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
Okay that last number before 2.7t on the fdisk output is correct. It doesn't make sense to me that it's smaller than the number before it, but I checked and what was supplied is accurate. On Tue, 13 Mar 2018, Linux for blind general discussion wrote: Date: Tue, 13 Mar 2018 18:26:39 From: Linux for blind general discussion To: Linux for blind general discussion Subject: Re: slint 2tb limit output from: lsblk -o model,name,size,fstype wdc wd30ezrx-00d sda 2.7t sda1 2m ext4 sda2 2g swap sda3 2.7t ihas124 w sr0 3.4g iso9660 output from: fdisk -l|grep ^/ /dev/sda1 2048 6143 4096 2m bios boot /dev/sda2 6144 4198399 4192256 2g linux filesystem /dev/sda3 4198400 5860531119 5856332720 2.7t linux filesystem The last number on last line before 2.7t is probably wrong. I can try running second command again and see if result differs. On Mon, 12 Mar 2018, Linux for blind general discussion wrote: Date: Mon, 12 Mar 2018 11:13:51 From: Linux for blind general discussion To: blinux-list@redhat.com Subject: Re: slint 2tb limit Hello, Didier Spaier, Slint maintainer, here. Le 12/03/2018 ? 15:48, Linux for blind general discussion a ?crit?: So far as I can tell, slint appears to have a 2tb hard drive size limit. I tried it with a 3tb drive and hope I haven't permanently trashed the drive.? What happens with slint is you set up a swap partition on the drive and a linux partition and it doesn't matter what you use to do it either.? Once done, you run setup and get the message that slint can't find any partitions on the hard drive.? I have a bad compatibility situation here since technology is 24 years old and back in those years all that was known about was bios, efi and uefi didn't exist then.? Last bios flash update for AMD k8 athelon computers I think was 2006.? So, I'll see if I can rescue the 3tb drive with archlinux then go from there. I haven't such a big drive to check but am a bit surprised of such a limitation. To help investigate, could you please start again the installer, then after log in as root instead of running setup type this command, then post the output: lsblk -o model,name,size,fstype And also please post the output of this other command: fdisk -l|grep ^/ That should allow me to understand why the installer doesn't see the partitions. Best regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
output from: lsblk -o model,name,size,fstype wdc wd30ezrx-00d sda 2.7t sda1 2m ext4 sda2 2g swap sda3 2.7t ihas124 w sr0 3.4g iso9660 output from: fdisk -l|grep ^/ /dev/sda1 2048 6143 4096 2m bios boot /dev/sda2 6144 4198399 4192256 2g linux filesystem /dev/sda3 4198400 5860531119 5856332720 2.7t linux filesystem The last number on last line before 2.7t is probably wrong. I can try running second command again and see if result differs. On Mon, 12 Mar 2018, Linux for blind general discussion wrote: Date: Mon, 12 Mar 2018 11:13:51 From: Linux for blind general discussion To: blinux-list@redhat.com Subject: Re: slint 2tb limit Hello, Didier Spaier, Slint maintainer, here. Le 12/03/2018 ? 15:48, Linux for blind general discussion a ?crit?: So far as I can tell, slint appears to have a 2tb hard drive size limit. I tried it with a 3tb drive and hope I haven't permanently trashed the drive.? What happens with slint is you set up a swap partition on the drive and a linux partition and it doesn't matter what you use to do it either.? Once done, you run setup and get the message that slint can't find any partitions on the hard drive.? I have a bad compatibility situation here since technology is 24 years old and back in those years all that was known about was bios, efi and uefi didn't exist then.? Last bios flash update for AMD k8 athelon computers I think was 2006.? So, I'll see if I can rescue the 3tb drive with archlinux then go from there. I haven't such a big drive to check but am a bit surprised of such a limitation. To help investigate, could you please start again the installer, then after log in as root instead of running setup type this command, then post the output: lsblk -o model,name,size,fstype And also please post the output of this other command: fdisk -l|grep ^/ That should allow me to understand why the installer doesn't see the partitions. Best regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
Hello, Diider again, Le 12/03/2018 à 15:48, Linux for blind general discussion a écrit : > So far as I can tell, slint appears to have a 2tb hard drive size limit. I > tried it with a 3tb drive and hope I haven't permanently trashed the drive. > What happens with slint is you set up a swap partition on the drive and a > linux partition and it doesn't matter what you use to do it either. Once > done, you run setup and get the message that slint can't find any partitions > on the hard drive. I have a bad compatibility situation here since > technology is 24 years old and back in those years all that was known about > was bios, efi and uefi didn't exist then. Last bios flash update for AMD k8 > athelon computers I think was 2006. So, I'll see if I can rescue the 3tb > drive with archlinux then go from there. With MBR, the maximum disk size is 2 TB. It can work on larger disks, too, but you won’t be able to use anything beyond the first 2 TB. However, this only applies to disks with 512-byte sectors (because, incidentally, 512 byte * 2^32 = 2 TB).UEFI To complete my previous answer it is a know limitation o DOS (aka MBR) partition table, as quoted below: With MBR, the maximum disk size is 2 TB. It can work on larger disks, too, but you won’t be able to use anything beyond the first 2 TB. However, this only applies to disks with 512-byte sectors (because, incidentally, 512 byte * 2^32 = 2 TB). So, I'd try just replacing the DOS partition table by a GUID Partition Table using gdisk (shipped in the installer). In case you wonder, although GPT be mentioned in the UEFI specification it is as far as I know possible to use a GPT with BIOS. At least that's worth trying. Bests regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: slint 2tb limit
Hello, Didier Spaier, Slint maintainer, here. Le 12/03/2018 à 15:48, Linux for blind general discussion a écrit : > So far as I can tell, slint appears to have a 2tb hard drive size limit. I > tried it with a 3tb drive and hope I haven't permanently trashed the drive. > What happens with slint is you set up a swap partition on the drive and a > linux partition and it doesn't matter what you use to do it either. Once > done, you run setup and get the message that slint can't find any partitions > on the hard drive. I have a bad compatibility situation here since > technology is 24 years old and back in those years all that was known about > was bios, efi and uefi didn't exist then. Last bios flash update for AMD k8 > athelon computers I think was 2006. So, I'll see if I can rescue the 3tb > drive with archlinux then go from there. I haven't such a big drive to check but am a bit surprised of such a limitation. To help investigate, could you please start again the installer, then after log in as root instead of running setup type this command, then post the output: lsblk -o model,name,size,fstype And also please post the output of this other command: fdisk -l|grep ^/ That should allow me to understand why the installer doesn't see the partitions. Best regards, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
slint 2tb limit
So far as I can tell, slint appears to have a 2tb hard drive size limit. I tried it with a 3tb drive and hope I haven't permanently trashed the drive. What happens with slint is you set up a swap partition on the drive and a linux partition and it doesn't matter what you use to do it either. Once done, you run setup and get the message that slint can't find any partitions on the hard drive. I have a bad compatibility situation here since technology is 24 years old and back in those years all that was known about was bios, efi and uefi didn't exist then. Last bios flash update for AMD k8 athelon computers I think was 2006. So, I'll see if I can rescue the 3tb drive with archlinux then go from there. -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
