[opensuse] Problems loading opensuse on 4TB USB drive on 42.3
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition. After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue I examined the partitions from my running system: Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data Why do you think this USB file system is loaded as sda. My other USB drives come up sdc, after my two installed hard drives sda and sdb. Is there something I need to write into the BIOS boot partition, and why didn't the 42.3 system installer do it? Any assistance would be appreciated. I hope these questions are not too simple. Sometimes I miss a switch in the GUI, or something equally as trivial. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/03/2017 07:59 PM, don fisher wrote:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
I examined the partitions from my running system:
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data
Why do you think this USB file system is loaded as sda. My other USB drives come up sdc, after my two installed hard drives sda and sdb. Is there something I need to write into the BIOS boot partition, and why didn't the 42.3 system installer do it? Any assistance would be appreciated.
I hope these questions are not too simple. Sometimes I miss a switch in the GUI, or something equally as trivial.
Thanks, Don
Sorry, forgot to mention why the partitions are Microsoft basic data, instead of linux, linux and linux swap. I created these using the system installer DVD. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Sorry, forgot to mention why the partitions are Microsoft basic data, instead of linux, linux and linux swap. I created these using the system installer DVD.
Don "Microsoft basic data" is an ntfs partition type used for large
On 04/08/2017 05:13, don fisher wrote: partitions, maybe that's the reason for your problem? Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 08:23, Dave Plater wrote:
Sorry, forgot to mention why the partitions are Microsoft basic data, instead of linux, linux and linux swap. I created these using the system installer DVD.
Don "Microsoft basic data" is an ntfs partition type used for large
On 04/08/2017 05:13, don fisher wrote: partitions, maybe that's the reason for your problem?
Nope. This is mine, and all are Linux filesystems: Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4 Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R.
On 2017-08-05 08:23, Dave Plater wrote:
Sorry, forgot to mention why the partitions are Microsoft basic data, instead of linux, linux and linux swap. I created these using the system installer DVD.
Don "Microsoft basic data" is an ntfs partition type used for large
On 04/08/2017 05:13, don fisher wrote: partitions, maybe that's the reason for your problem?
Nope.
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data Telcontar:~ #
and I have two: fdisk -l /dev/sde /dev/sdg Disk /dev/sde: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: D00C3930-FEE3-4582-97EA-34248A02E1DE Device Start End Sectors Size Type /dev/sde1 34 262177 262144 128M Microsoft reserved /dev/sde2 264192 7814035455 7813771264 3.7T Microsoft basic data Disk /dev/sdg: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: CE9BEE0F-0E03-4F30-9B74-A02A1A3A6A8E Device Start End Sectors Size Type /dev/sdg1 2048 7814035455 7814033408 3.7T Microsoft basic data the Microsoft reserved partition on sdg is to boot a windows recovery (backup) system installed there for off-site clients. (which I hope to never use) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/08/2017 14:55, Carlos E. R. wrote:
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data
This interests me I've a 1T usb hard drive which lists "Microsoft basic data" as the partition type in fdisk but I've left the ntfs partition for now. Can't linux partition types be set on a disk with a gpt partition? Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Dave Plater
On 05/08/2017 14:55, Carlos E. R. wrote:
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data
This interests me I've a 1T usb hard drive which lists "Microsoft basic data" as the partition type in fdisk but I've left the ntfs partition for now. Can't linux partition types be set on a disk with a gpt partition?
gpt is not a partition but a standard for partitioning disks. you must format the partition to the type you desire. if you open fdisk to a particular disk and list known partition types, you will see: 10 Microsoft reserved 11 Microsoft basic data and you will not see ntfs -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 15:10, Dave Plater wrote:
On 05/08/2017 14:55, Carlos E. R. wrote:
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data
This interests me I've a 1T usb hard drive which lists "Microsoft basic data" as the partition type in fdisk but I've left the ntfs partition for now. Can't linux partition types be set on a disk with a gpt partition?
Of course. The above is a bootable Linux disk partitioned as GPT. All partitions are LInux types created with Linux software, despite the "Microsoft basic data" above. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 05/08/2017 15:25, Carlos E. R. wrote:
On 2017-08-05 15:10, Dave Plater wrote:
On 05/08/2017 14:55, Carlos E. R. wrote:
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data
This interests me I've a 1T usb hard drive which lists "Microsoft basic data" as the partition type in fdisk but I've left the ntfs partition for now. Can't linux partition types be set on a disk with a gpt partition?
Of course. The above is a bootable Linux disk partitioned as GPT. All partitions are LInux types created with Linux software, despite the "Microsoft basic data" above.
But in fdisk on my gpt partitioned disk "l" lists a host of partition types including several linux ones, why would you use "11 Microsoft basic data" for a linux file system? Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 15:39, Dave Plater wrote:
On 05/08/2017 15:25, Carlos E. R. wrote:
On 2017-08-05 15:10, Dave Plater wrote:
On 05/08/2017 14:55, Carlos E. R. wrote:
This is mine, and all are Linux filesystems:
Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 9020FF2C-0CF7-49F8-8F2B-9425CFCDCCE4
Device Start End Sectors Size Type /dev/sda1 2048 16383 14336 7M BIOS boot /dev/sda2 16384 41961471 41945088 20G Microsoft basic data /dev/sda3 41961472 73416703 31455232 15G Microsoft basic data /dev/sda4 73416704 75522047 2105344 1G Microsoft basic data /dev/sda5 75522048 77625343 2103296 1G Microsoft basic data /dev/sda6 77625344 79730687 2105344 1G Microsoft basic data /dev/sda7 79730688 121675775 41945088 20G Microsoft basic data /dev/sda8 121675776 184586239 62910464 30G Microsoft basic data /dev/sda9 184586240 226533375 41947136 20G Microsoft basic data /dev/sda10 226533376 268478463 41945088 20G Microsoft basic data /dev/sda11 268478464 293652479 25174016 12G Linux RAID /dev/sda12 293652480 2441140223 2147487744 1T Microsoft basic data /dev/sda13 2441140224 3907028991 1465888768 699G Microsoft basic data
This interests me I've a 1T usb hard drive which lists "Microsoft basic data" as the partition type in fdisk but I've left the ntfs partition for now. Can't linux partition types be set on a disk with a gpt partition?
Of course. The above is a bootable Linux disk partitioned as GPT. All partitions are LInux types created with Linux software, despite the "Microsoft basic data" above.
But in fdisk on my gpt partitioned disk "l" lists a host of partition types including several linux ones, why would you use "11 Microsoft basic data" for a linux file system?
/I/ did not do it. Linux tools did it. Gparted, actually. And in other cases, the openSUSE install DVD does it. I did not see any place to change it. I looked now with gparted, the "Microsoft basic data" is not even displayed. No way to change it. I don't have an empty disk to try. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 05/08/2017 15:52, Carlos E. R. wrote:
But in fdisk on my gpt partitioned disk "l" lists a host of partition types including several linux ones, why would you use "11 Microsoft basic data" for a linux file system? /I/ did not do it. Linux tools did it. Gparted, actually. And in other cases, the openSUSE install DVD does it.
I did not see any place to change it. I looked now with gparted, the "Microsoft basic data" is not even displayed. No way to change it. I don't have an empty disk to try. I usually use fdisk and mkfs to set up disks, maybe it's a bug that gparted uses a microsoft partition type, I must experiment some time when I get a new disk. Quoted from wikepedia: All modern PC operating systems support GPT. Some, including macOS and Microsoft Windows on x86, support booting from GPT partitions only on systems with EFI firmware, but FreeBSD and most Linux distributions can boot from GPT partitions on systems with both legacy BIOS firmware interface and EFI.
Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 16:29, Dave Plater wrote:
On 05/08/2017 15:52, Carlos E. R. wrote:
Quoted from wikepedia: All modern PC operating systems support GPT. Some, including macOS and Microsoft Windows on x86, support booting from GPT partitions only on systems with EFI firmware, but FreeBSD and most Linux distributions can boot from GPT partitions on systems with both legacy BIOS firmware interface and EFI.
Yes. I boot this "legacy" computer from a 2TB disk partitioned as GPT. Works nicely. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 03/08/17 11:13 PM, don fisher wrote:
Sorry, forgot to mention why the partitions are Microsoft basic data, instead of linux, linux and linux swap. I created these using the system installer DVD.
One would expect that the Linux installer would tag the partitions as being of type Linux. But honestly, whenever I have to install on a new drive I first use fdisk (or equivalent), possibly after booting with a LiveCD (for some reason the one that seems to work in all circumstances is Knoppix) and set up the partition structure, tag them appropriately for Linux use AND LABEL THE PARTITIONS THAT I WANT TO USE FOR SWAP, ROOT, TMP AND HOME using the fdisk tool *before* starting the installation. Now why would I always do something ridiculous like that? Dunno, but doing it avoids ending up with the installer creating partition s tagged for Microsoft data. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-04 04:59, don fisher wrote:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
I assume your computer is using BIOS, not UEFI?
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
I understand you can boot some Linux system, then please download and run this nice script: https://raw.githubusercontent.com/arvidjaar/bootinfoscript/master/bootinfosc... It will generate a file: RESULTS.txt. Just upload the file to susepaste.org (for a limited time) and post here the link. That will give any helper here a lot of information, instead of asking questions. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
On 2017-08-04 04:59, don fisher wrote:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
I assume your computer is using BIOS, not UEFI?
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
I understand you can boot some Linux system, then please download and run this nice script:
https://raw.githubusercontent.com/arvidjaar/bootinfoscript/master/bootinfosc...
It will generate a file: RESULTS.txt. Just upload the file to susepaste.org (for a limited time) and post here the link.
That will give any helper here a lot of information, instead of asking questions.
I could not open susepaste.org from my browser, so I included the file as an attachment. Please advise how one should submit a file syse0aste.org. The entire output from fdisk -l is: sudo fdisk -l /dev/sda Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: 632303A7-EC28-4C7B-ADB3-3430E0918988 Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data I notice that this disk says it is type: gpt, where my other disks say they are of type dos. Please advise. Thanks Don
On 2017-08-04 21:17, don fisher wrote:
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
It will generate a file: RESULTS.txt. Just upload the file to susepaste.org (for a limited time) and post here the link.
That will give any helper here a lot of information, instead of asking questions.
I could not open susepaste.org from my browser, so I included the file as an attachment. Please advise how one should submit a file syse0aste.org.
Attached is ok. It is a normal webpage, nothing strange in it. You can also use command "susepaste", but you have to install it first.
The entire output from fdisk -l is:
sudo fdisk -l /dev/sda Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: 632303A7-EC28-4C7B-ADB3-3430E0918988
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data
This can not be the entire output of the command, because I do not see sdb nor sdc. Ah. You were asked for the output of "fdisk -l" not "fdisk -l /dev/sda". Please repost as asked.
I notice that this disk says it is type: gpt, where my other disks say they are of type dos. Please advise.
It is correct, you need GPT for a disk that size. Reading RESULTS.txt file and commenting. => Syslinux GPTMBR (4.04-5.01) is installed in the MBR of /dev/sda. => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdb. => Syslinux MBR (5.00 and higher) is installed in the MBR of /dev/sdc. sda2 is marked bootable, and contains grub2, and also Leap 42.3. Also sdb2 and sdc are marked bootable. sdb2 contains grub2 and Leap 42.3 sdc2 contains grub2 and yet another Leap 42.3. grub2 at sda2 tries load root from 2dfbf5e1-e13c-4cd7-9f00-b5b9602d7250, which is correct. Also, sdb2 and sdc2 seem correct. All seems correct. I don't see what is wrong - unless the bios tries to boot another disk that I do not see in the file. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
04.08.2017 22:17, don fisher пишет:
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
On 2017-08-04 04:59, don fisher wrote:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
I assume your computer is using BIOS, not UEFI?
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
...> The entire output from fdisk -l is:
sudo fdisk -l /dev/sda Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
You have 4K disk. So far I have not seen or heard of any BIOS that is capable of booting from 4K disks. If your system supports EFI, use it - it is likely to work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 06:47, Andrei Borzenkov wrote:
04.08.2017 22:17, don fisher пишет:
...>
The entire output from fdisk -l is:
sudo fdisk -l /dev/sda Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
You have 4K disk. So far I have not seen or heard of any BIOS that is capable of booting from 4K disks. If your system supports EFI, use it - it is likely to work.
Mine does fine - notice that we both have a logical size of 512B: Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Mine is smaller; the main difference is on the I/O line. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
On 2017-08-04 04:59, don fisher wrote:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
I assume your computer is using BIOS, not UEFI?
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
I understand you can boot some Linux system, then please download and run this nice script:
https://raw.githubusercontent.com/arvidjaar/bootinfoscript/master/bootinfosc...
It will generate a file: RESULTS.txt. Just upload the file to susepaste.org (for a limited time) and post here the link.
That will give any helper here a lot of information, instead of asking questions.
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: 632303A7-EC28-4C7B-ADB3-3430E0918988 Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data Disk /dev/sdb: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000e2eb0 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 20965375 20963328 10G 82 Linux swap / Solaris /dev/sdb2 * 20965376 125820927 104855552 50G 83 Linux /dev/sdb3 125820928 2000408575 1874587648 893.9G 83 Linux Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000d75b2 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4208639 4206592 2G 82 Linux swap / Solaris /dev/sdc2 * 4208640 46153727 41945088 20G 83 Linux /dev/sdc3 46153728 1953523711 1907369984 909.5G 83 Linux What happened to gparted? when I search for it it only comes up under 42.2. Also I am curious why fdisk shows file types as Microsoft basic data. The output from lsblk shows the file systems as I requested: sudo lsblk -a -fs /dev/sda2 NAME FSTYPE LABEL UUID MOUNTPOINT sda2 btrfs 2dfbf5e1-e13c-4cd7-9f00-b5b9602d7250 `-sda dfpc64-dfisher> sudo lsblk -a -fs /dev/sda3 NAME FSTYPE LABEL UUID MOUNTPOINT sda3 xfs 7e820331-a9da-46cd-a670-e103361487ed `-sda dfpc64-dfisher> sudo lsblk -a -fs /dev/sda4 NAME FSTYPE LABEL UUID MOUNTPOINT sda4 swap 5ba695db-9b9e-4376-8ece-11703bf64fed `-sda dfpc64-dfisher> sudo lsblk -a -fs /dev/sda1 NAME FSTYPE LABEL UUID MOUNTPOINT sda1 `-sda Are you aware of anybody that has built a bootable system on a 4TB drive? I have performed installation from the 42.3 distribution twice with repeatable results. Any ideas? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-04 23:24, don fisher wrote:
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: 632303A7-EC28-4C7B-ADB3-3430E0918988
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data
Disk /dev/sdb: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000e2eb0
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 20965375 20963328 10G 82 Linux swap / Solaris /dev/sdb2 * 20965376 125820927 104855552 50G 83 Linux /dev/sdb3 125820928 2000408575 1874587648 893.9G 83 Linux
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000d75b2
Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4208639 4206592 2G 82 Linux swap / Solaris /dev/sdc2 * 4208640 46153727 41945088 20G 83 Linux /dev/sdc3 46153728 1953523711 1907369984 909.5G 83 Linux
Seems correct. There are no hidden disks. Your symptoms are as if the BIOS is booting from another disk. Maybe Andrei can see something else, he is the expert. Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now.
What happened to gparted? when I search for it it only comes up under 42.2.
No, it is also on 42.3, I installed it. https://software.opensuse.org/package/gparted
Also I am curious why fdisk shows file types as Microsoft basic data.
I don't remember, but it is of no consequence. It is not the actual filesystem type, but the type that the partitioner was told when the partition was created.
Are you aware of anybody that has built a bootable system on a 4TB drive? I have performed installation from the 42.3 distribution twice with repeatable results.
Mine uses a 2 TB disk, GPT, BIOS system. It is similar to yours but internal and smaller. And I have a separate /boot partition. I have a 3 TB data disk. Possibly the BIOS can not access the entire 4TB disk, but the system is at the start, 50 GB, so I would not expect a problem. Telcontar:~ # lsblk --bytes --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT /dev/sda NAME KNAME RA RM RO SIZE TYPE FSTYPE LABEL PARTLABEL MOUNTPOINT UUID PARTUUID WWN MODEL ALIGNMENT sda sda 512 0 0 2000398934016 disk ST2000DM001-1CH1 0 ├─sda1 sda1 512 0 0 7340032 part primary 425bb0bf-d0f3-490a-8a2b-9f4bc96d47bc 0 ├─sda2 sda2 512 0 0 21475885056 part ext4 Gestor primary 943d650b-ea9c-4fbd-9d2c-993abae7655b 108a99e8-6c65-4478-a0fb-2e119191cceb 0 ├─sda3 sda3 512 0 0 16105078784 part swap Swap_0 primary [SWAP] 1760cc5a-4caa-4c1c-8328-115d395f0637 d67674b0-b4d1-4adf-8b3e-e7cdb00703cf 0 ├─sda4 sda4 512 0 0 1077936128 part ext2 a_boot_1 primary /other/test_a1/boot 4e391e1e-bf64-4a84-a13d-89f4f71fc9d0 a1537507-05d1-479a-8e3d-da5e3ec57122 0 ├─sda5 sda5 512 0 0 1076887552 part ext2 a_boot_2 primary /boot e99d9dcb-869d-4a24-94cf-cba32f169b8d 31a69a08-1633-4a55-9780-5f1803660513 0 ├─sda6 sda6 512 0 0 1077936128 part ext2 a_boot_3 primary 810339a7-20f4-43b5-8aab-edb051247f81 727195a6-509d-4cef-aac9-abdbf9913e8f 0 ├─sda7 sda7 512 0 0 21475885056 part reiserfs a_test1 primary /other/test_a1 dd47dbe5-9f3d-4b01-8e56-d67d4ecbd031 b532160d-5273-4293-b167-dcc20888888a 0 ├─sda8 sda8 512 0 0 32210157568 part ext4 a_main primary / c6a59497-85b9-454c-a5d1-1dcafa6eed3d 880b53b2-2202-410c-ba20-4ba1a5a47d3e 0 ├─sda9 sda9 512 0 0 21476933632 part ext4 a_test2 primary 29c8ff1e-552a-4538-93fe-628be4568c08 141273d8-afc1-4a25-be19-073684d98ac8 0 ├─sda10 sda10 512 0 0 21475885056 part ext4 a_test3 primary cacc257e-8664-4b06-8926-174be61b8719 99ed5c63-2166-46f5-8296-80ca9ec3461e 0 ├─sda11 sda11 512 0 0 12889096192 part linux_raid_member Telcontar:0 primary 825b22e8-af55-0e83-9372-7666fb8987fd 39b04c75-67f9-4122-9510-5d760f2aed3d 0 │ └─md0 md0 512 0 0 25777668096 raid5 xfs raid5 /data/raid 451fb568-860a-4ee3-b238-1423bfb0a034 0 ├─sda12 sda12 512 0 0 1099513724928 part xfs a_vmware primary /data/vmware 4405d4ee-918b-4701-8bd3-8b7b48b20cf3 f39f935b-e4bf-4f37-81dd-694e8630f7f6 0 └─sda13 sda13 512 0 0 750535049216 part xfs a_storage primary /data/storage_a 1526a315-e970-4dd6-8130-4c8275c9d3a5 740c9a40-58bf-4bf4-984b-90f874ef494f 0 Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2017-08-05 04:19 (UTC+0200):
On 2017-08-04 23:24, don fisher wrote: ...
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes ... Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now.... What's the problem you think you see? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 04:29, Felix Miata wrote:
Carlos E. R. composed on 2017-08-05 04:19 (UTC+0200):
On 2017-08-04 23:24, don fisher wrote: ...
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes ... Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now.... What's the problem you think you see?
My mistake in appreciation, it is 4 KiB physical size. With a large disk, 4 TB, the number of 512 byte sector is huge. With 4K sectors, it is 8 times smaller. Current disks have typically 4 KiB sectors. Sometimes, 4 KiB real, 512 emulated. See: Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / *4096* bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Mine: Telcontar:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Now I wonder now about the optima I/O size of his. :-? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/04/2017 07:29 PM, Felix Miata wrote:
Carlos E. R. composed on 2017-08-05 04:19 (UTC+0200):
On 2017-08-04 23:24, don fisher wrote: ...
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes ... Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now.... What's the problem you think you see?
as in first post, system will not boot. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2017-08-04 23:20 (UTC-0400):
Felix Miata wrote:
Carlos E. R. composed on 2017-08-05 04:19 (UTC+0200):
Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now....
What's the problem you think you see?
as in first post, system will not boot.
My question was directed to Carlos' question. I'm still interested in seeing your problem solved, but as yet recognize nothing to explain it. I've been multibooting >25 years, but have no disks >2TB, so can't very well try emulating your situation. Why bootinfoscript has reported that your MBRs contain syslinux I don't understand. If your motherboard firmware is configured to boot in legacy mode I would have expected it to contain legacy compatible code or grub code. Is 42.3 your first installation using the 4TB disk as a primary (sda) disk, and/or first trying to use a USB HD to boot from? I think the thread has been made overly complex if what you're really after is booting 42.3 from your internal 1TB HD reliably. I recommend powering the USB disk down and keeping it that way until internal HD booting works as it should. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 06:25, Felix Miata wrote:
don fisher composed on 2017-08-04 23:20 (UTC-0400):
Felix Miata wrote:
Carlos E. R. composed on 2017-08-05 04:19 (UTC+0200):
Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now....
What's the problem you think you see?
as in first post, system will not boot.
My question was directed to Carlos' question.
I'm still interested in seeing your problem solved, but as yet recognize nothing to explain it. I've been multibooting >25 years, but have no disks >2TB, so can't very well try emulating your situation.
Why bootinfoscript has reported that your MBRs contain syslinux I don't understand. If your motherboard firmware is configured to boot in legacy mode I would have expected it to contain legacy compatible code or grub code.
Syslinux GPTMBR is what is needed to boot with a BIOS machine a big GPT disk, on a legacy machine (BIOS). This is mine (working): ============================= Boot Info Summary: =============================== => Syslinux GPTMBR (4.04-5.01) is installed in the MBR of /dev/sda. => libparted MBR boot code is installed in the MBR of /dev/sdb. It is an MBR code that is designed to be written to the protective MBR of a GPT partitioned disk, and as the original one it searches for the boot mark - look at mine: Drive: sda _____________________________________________________________________ Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Partition Boot Start Sector End Sector # of Sectors Id System /dev/sda1 1 3,907,029,167 3,907,029,167 ee GPT GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sda1 2,048 16,383 14,336 BIOS Boot partition /dev/sda2 B 16,384 41,961,471 41,945,088 Data partition (Windows/Linux) /dev/sda3 41,961,472 73,416,703 31,455,232 Data partition (Windows/Linux) /dev/sda4 73,416,704 75,522,047 2,105,344 Data partition (Windows/Linux) ... Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set Thus, on a GPT disk you can have dozens of primary partitions and boot any one directly by marking it bootable. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 08/04/2017 07:19 PM, Carlos E. R. wrote:
On 2017-08-04 23:24, don fisher wrote:
On 08/03/2017 08:21 PM, Carlos E. R. wrote:
Complete output from fdisk -l is: Disk /dev/sda: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: 632303A7-EC28-4C7B-ADB3-3430E0918988
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data
Disk /dev/sdb: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000e2eb0
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 20965375 20963328 10G 82 Linux swap / Solaris /dev/sdb2 * 20965376 125820927 104855552 50G 83 Linux /dev/sdb3 125820928 2000408575 1874587648 893.9G 83 Linux
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000d75b2
Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4208639 4206592 2G 82 Linux swap / Solaris /dev/sdc2 * 4208640 46153727 41945088 20G 83 Linux /dev/sdc3 46153728 1953523711 1907369984 909.5G 83 Linux
Seems correct. There are no hidden disks. Your symptoms are as if the BIOS is booting from another disk.
Maybe Andrei can see something else, he is the expert.
Curious: your sectors are of 512 bytes on the big disk. Those typically are 4K now.
What happened to gparted? when I search for it it only comes up under 42.2.
No, it is also on 42.3, I installed it.
https://software.opensuse.org/package/gparted
Also I am curious why fdisk shows file types as Microsoft basic data.
I don't remember, but it is of no consequence. It is not the actual filesystem type, but the type that the partitioner was told when the partition was created.
Are you aware of anybody that has built a bootable system on a 4TB drive? I have performed installation from the 42.3 distribution twice with repeatable results.
Mine uses a 2 TB disk, GPT, BIOS system. It is similar to yours but internal and smaller. And I have a separate /boot partition. I have a 3 TB data disk.
Possibly the BIOS can not access the entire 4TB disk, but the system is at the start, 50 GB, so I would not expect a problem.
Telcontar:~ # lsblk --bytes --output NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT /dev/sda NAME KNAME RA RM RO SIZE TYPE FSTYPE LABEL PARTLABEL MOUNTPOINT UUID PARTUUID WWN MODEL ALIGNMENT sda sda 512 0 0 2000398934016 disk ST2000DM001-1CH1 0 ├─sda1 sda1 512 0 0 7340032 part primary 425bb0bf-d0f3-490a-8a2b-9f4bc96d47bc 0 ├─sda2 sda2 512 0 0 21475885056 part ext4 Gestor primary 943d650b-ea9c-4fbd-9d2c-993abae7655b 108a99e8-6c65-4478-a0fb-2e119191cceb 0 ├─sda3 sda3 512 0 0 16105078784 part swap Swap_0 primary [SWAP] 1760cc5a-4caa-4c1c-8328-115d395f0637 d67674b0-b4d1-4adf-8b3e-e7cdb00703cf 0 ├─sda4 sda4 512 0 0 1077936128 part ext2 a_boot_1 primary /other/test_a1/boot 4e391e1e-bf64-4a84-a13d-89f4f71fc9d0 a1537507-05d1-479a-8e3d-da5e3ec57122 0 ├─sda5 sda5 512 0 0 1076887552 part ext2 a_boot_2 primary /boot e99d9dcb-869d-4a24-94cf-cba32f169b8d 31a69a08-1633-4a55-9780-5f1803660513 0 ├─sda6 sda6 512 0 0 1077936128 part ext2 a_boot_3 primary 810339a7-20f4-43b5-8aab-edb051247f81 727195a6-509d-4cef-aac9-abdbf9913e8f 0 ├─sda7 sda7 512 0 0 21475885056 part reiserfs a_test1 primary /other/test_a1 dd47dbe5-9f3d-4b01-8e56-d67d4ecbd031 b532160d-5273-4293-b167-dcc20888888a 0 ├─sda8 sda8 512 0 0 32210157568 part ext4 a_main primary / c6a59497-85b9-454c-a5d1-1dcafa6eed3d 880b53b2-2202-410c-ba20-4ba1a5a47d3e 0 ├─sda9 sda9 512 0 0 21476933632 part ext4 a_test2 primary 29c8ff1e-552a-4538-93fe-628be4568c08 141273d8-afc1-4a25-be19-073684d98ac8 0 ├─sda10 sda10 512 0 0 21475885056 part ext4 a_test3 primary cacc257e-8664-4b06-8926-174be61b8719 99ed5c63-2166-46f5-8296-80ca9ec3461e 0 ├─sda11 sda11 512 0 0 12889096192 part linux_raid_member Telcontar:0 primary 825b22e8-af55-0e83-9372-7666fb8987fd 39b04c75-67f9-4122-9510-5d760f2aed3d 0 │ └─md0 md0 512 0 0 25777668096 raid5 xfs raid5 /data/raid 451fb568-860a-4ee3-b238-1423bfb0a034 0 ├─sda12 sda12 512 0 0 1099513724928 part xfs a_vmware primary /data/vmware 4405d4ee-918b-4701-8bd3-8b7b48b20cf3 f39f935b-e4bf-4f37-81dd-694e8630f7f6 0 └─sda13 sda13 512 0 0 750535049216 part xfs a_storage primary /data/storage_a 1526a315-e970-4dd6-8130-4c8275c9d3a5 740c9a40-58bf-4bf4-984b-90f874ef494f 0 Telcontar:~ #
The link says it is for 42.2. The last time I attempted to load a 42.2 package it tried to install a lot of the 42.2 distribution. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2017-08-04 20:26 (UTC-0700):
Carlos E. R. wrote:
don fisher wrote:
What happened to gparted? when I search for it it only comes up under 42.2.
No, it is also on 42.3, I installed it.
https://software.opensuse.org/package/gparted ... The link says it is for 42.2. The last time I attempted to load a 42.2 package it tried to install a lot of the 42.2 distribution.
It's on the normal mirrors, but maybe you're suffering from the common North American mirror bottleneck problem I've been encountering lately. https://software.opensuse.org/package/gparted http://ftp.uni-erlangen.de/opensuse/distribution/leap/42.3/repo/oss/suse/x86... https://muug.ca/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://ftp5.gwdg.de/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64... http://download.opensuse.org/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://mirrors.kernel.org/opensuse/distribution/leap/42.3/repo/oss/suse/x86_... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/04/2017 08:49 PM, Felix Miata wrote:
don fisher composed on 2017-08-04 20:26 (UTC-0700):
Carlos E. R. wrote:
don fisher wrote:
What happened to gparted? when I search for it it only comes up under 42.2.
No, it is also on 42.3, I installed it.
https://software.opensuse.org/package/gparted ... The link says it is for 42.2. The last time I attempted to load a 42.2 package it tried to install a lot of the 42.2 distribution.
It's on the normal mirrors, but maybe you're suffering from the common North American mirror bottleneck problem I've been encountering lately.
https://software.opensuse.org/package/gparted http://ftp.uni-erlangen.de/opensuse/distribution/leap/42.3/repo/oss/suse/x86... https://muug.ca/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://ftp5.gwdg.de/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64... http://download.opensuse.org/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://mirrors.kernel.org/opensuse/distribution/leap/42.3/repo/oss/suse/x86_...
Sorry to beat a dead horse:-) I installed from mirrors.kernel.org, and when I executed it I received: /usr/sbin/gpartedbin: symbol lookup error: /usr/sbin/gpartedbin: undefined symbol: _ZN4Glib17SignalProxyNormal13connect_impl_EbON4sigc9slot_baseEb What did I do incorrectly? Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* don fisher
On 08/04/2017 08:49 PM, Felix Miata wrote:
don fisher composed on 2017-08-04 20:26 (UTC-0700):
Carlos E. R. wrote:
don fisher wrote:
What happened to gparted? when I search for it it only comes up under 42.2.
No, it is also on 42.3, I installed it.
https://software.opensuse.org/package/gparted ... The link says it is for 42.2. The last time I attempted to load a 42.2 package it tried to install a lot of the 42.2 distribution.
It's on the normal mirrors, but maybe you're suffering from the common North American mirror bottleneck problem I've been encountering lately.
https://software.opensuse.org/package/gparted http://ftp.uni-erlangen.de/opensuse/distribution/leap/42.3/repo/oss/suse/x86... https://muug.ca/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://ftp5.gwdg.de/pub/opensuse/distribution/leap/42.3/repo/oss/suse/x86_64... http://download.opensuse.org/distribution/leap/42.3/repo/oss/suse/x86_64/gpa... http://mirrors.kernel.org/opensuse/distribution/leap/42.3/repo/oss/suse/x86_...
Sorry to beat a dead horse:-) I installed from mirrors.kernel.org, and when I executed it I received:
/usr/sbin/gpartedbin: symbol lookup error: /usr/sbin/gpartedbin: undefined symbol: _ZN4Glib17SignalProxyNormal13connect_impl_EbON4sigc9slot_baseEb
What did I do incorrectly?
no idea but this should work zypper -v in --no-r http://download.opensuse.org/repositories/openSUSE:/Leap:/42.3/standard/x86_... that is all on one line as root. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
don fisher composed on 2017-08-06 16:36 (UTC-0700):
Felix Miata wrote: ...
http://mirrors.kernel.org/opensuse/distribution/leap/42.3/repo/oss/suse/x86_...
Sorry to beat a dead horse:-) I installed from mirrors.kernel.org, and when I executed it I received:
/usr/sbin/gpartedbin: symbol lookup error: /usr/sbin/gpartedbin: undefined symbol: _ZN4Glib17SignalProxyNormal13connect_impl_EbON4sigc9slot_baseEb
What did I do incorrectly?
Maybe nothing. Maybe mirror problems remain. Give 'zypper -v ve' a try. Does it find errors to fix, or claim no problems found? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
/usr/sbin/gpartedbin: symbol lookup error: /usr/sbin/gpartedbin: undefined symbol: _ZN4Glib17SignalProxyNormal13connect_impl_EbON4sigc9slot_baseEb
What did I do incorrectly?
Don One of the libraries that gpartedbin depends on is old and doesn't have
On 07/08/2017 01:36, don fisher wrote: the symbol. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-08-05 05:26, don fisher wrote:
On 08/04/2017 07:19 PM, Carlos E. R. wrote:
The link says it is for 42.2. The last time I attempted to load a 42.2 package it tried to install a lot of the 42.2 distribution.
Look carefully. https://software.opensuse.org/package/gparted First you see a "direct install" box. Don't click on it. Click on "Show other versions instead". That will list all distributions for which there is a gparted package. Click on the "openSUSE Leap 42.3" and it will give you the links. Notice the words "official release", means you do not have to add any extra repo, it is already in the official repos. Now look near the search box; Do you see a wrench? Click on it and select your default distribution. The page will remember (via cookie) and offer searchs for that one by default. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
04.08.2017 05:59, don fisher пишет:
I purchased a 4TB Seagate Backup Plus hard drive. I have experienced problems with reliable booting on other of my USB drives, so attempted to palace an opensuse system on the new 4TB drive as an experiment. I used a 42.3 cdrom installation media. It created partition 1 without my input, BIOS boot. I realize that the MBR boot cannot exceed 2TB, so was not surprised at this. I usually have swap in partition 1, so for this drive I place swap at the end of the dis after the XFS /home partition.
After the installation I booted and received: error: unknown filesystem entering rescue mpode Grub rescue
This means grub was not able to read /boot filesystem (or even identify it).
I examined the partitions from my running system:
Please show full fdisk -l output.
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 104871934 104855551 50G Microsoft basic data /dev/sda3 104871936 7792859134 7687987199 3.6T Microsoft basic data /dev/sda4 7792897920 7814000189 21102270 10.1G Microsoft basic data
Why do you think this USB file system is loaded as sda. My other USB drives come up sdc, after my two installed hard drives sda and sdb. Is there something I need to write into the BIOS boot partition, and why didn't the 42.3 system installer do it? Any assistance would be appreciated.
I hope these questions are not too simple. Sometimes I miss a switch in the GUI, or something equally as trivial.
Thanks, Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/03/2017 07:59 PM, don fisher wrote:
Why do you think this USB file system is loaded as sda. My other USB drives come up sdc, after my two installed hard drives sda and sdb.
USB drives can come up in the order they are plugged in, or in the order that USB headers are probed. This is why I always use uuids and put a line if fstab for drives I need to show up in specific orders, such as my backup devices. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen composed on 2017-08-04 12:08 (UTC-0700):
don fisher wrote:
Why do you think this USB file system is loaded as sda. My other USB drives come up sdc, after my two installed hard drives sda and sdb.
USB drives can come up in the order they are plugged in, or in the order that USB headers are probed. This is why I always use uuids and put a line if fstab for drives I need to show up in specific orders, such as my backup devices. I prevent USB storage from showing up ahead of ATA by disabling USB boot in motherboard firmware, but of course that's unhelpful when boot from USB is needed, in which case USB as sda is nice, keeping / filesystem on sda. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
Dave Plater -
don fisher -
Felix Miata -
John Andersen -
Patrick Shanahan