[opensuse] Boot problem with External 5 TB USB drive.
Below is all the information.
--
Boyd Gerber
On 2017-02-06 19:21, Boyd Lynn Gerber wrote:
Below is all the information.
Please, never use "dash dash space newline" in the midle of an email. It signifies "end of post, start of signature", so that your entire post is deleted on compliant software when starting to reply. I have now to copy paste your email to be able to comment on it.
The system will not boot. It tries to come up it goes immediately to grub-rescue. Trying to rescue the system from the DVD. I have tried.
Did it boot previously, or is it a new install?
1. booting from the DVD 2. mkdir /hdroot 3. mount /dev/md/hdroot /hdroot 4. mount --bind /dev /hdroot/dev 5. mount --bind /sys /hdroot/sys 6. mount --bind /proc /hdroot/proc 7. mount --bind /run /hdroot/run # done it with and without this one 8. chroot /hdroot 9. mount /boot 10. grub2-mkconfig -o /boot/grub2/grub.cfg 11. grub2-install /dev/sda 12. grub2-install --force /dev/sda1 13. grub2-install --force /dev/sda2 14. mkinitrd
grub-rescue >
I then boot from DVD using boot linux system or what ever the title is. I choose the boot and initrd, then choose the root device /dev/md/hdroot The system comes up normally.
# qemu-kvm -hda /dev/sda -boot c -m 256 -net none # shows boot menu and then boots.
/dev/sda1 BIOS Grub /dev/sda2 Linux EXT4 /dev/sda3 Swap Swapo /dev/sda4 NTFS NTFS /dev/sda5 Linux EXT4 /dev/sda6 Linux XFS
# fdisk -l Disk /dev/sda: 4.6 TiB, 5000981077504 bytes, 9767541167 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: 5109FB32-B869-4FEF-96F3-366953FFC77A
Device Start End Sectors Size Type /dev/sda1 2048 16382 14335 7M BIOS boot /dev/sda2 16384 2119678 2103295 1G Microsoft basic data /dev/sda3 2162655 23068319 20905665 10G Microsoft basic data /dev/sda4 23068320 1071628319 1048560000 500G Microsoft basic data /dev/sda5 1071628320 2124710234 1053081915 502.2G Microsoft basic data /dev/sda6 2124710235 9767533004 7642822770 3.6T Microsoft basic data
Partition 3 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary.
The rest of partitions do not intervene in booting, I understand. I suggest you download and run this script: https://github.com/arvidjaar/bootinfoscript/raw/master/bootinfoscript You can examine yourself the result, or share it with us. Don't email it, just upload to susepaste.org and post the link. It provides a lot of information on the boot files and analyzes some of it, it is easier to see problems using it. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-02-06 19:21, Boyd Lynn Gerber wrote:
Below is all the information.
Please, never use "dash dash space newline" in the midle of an email. It signifies "end of post, start of signature", so that your entire post is deleted on compliant software when starting to reply.
I have now to copy paste your email to be able to comment on it.
Just select it and hit reply. Works in knode. -- Per Jessen, Zürich (2.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hallo Per Jessen, op 06-02-17 om 20:40 schreef je:
Just select it and hit reply. Works in knode.
Thunderbird too. Shift+Ctrl+L (list) R (reply) Harrie -- Harrie Baken | Tekstbureau TekstBaken Copy-editing - proofreading (Dutch) www.tekstbaken.nl Registered Linux user #366560 | openSUSE 13.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/17 19:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-06 19:21, Boyd Lynn Gerber wrote:
Below is all the information.
Please, never use "dash dash space newline" in the midle of an email. It signifies "end of post, start of signature", so that your entire post is deleted on compliant software when starting to reply.
I have now to copy paste your email to be able to comment on it.
Just select it and hit reply. Works in knode.
In which case, knode is broken and non-RFC-compliant. As Carlos says, any RFC-compliant mailer, upon coming across "dash dash space" on a line all by itself, will delete that line and everything else following it when you hit "reply" or "forward". And non-RFC-compliant mailers are a pain in the neck to everyone else. If yours is non-compliant, please ditch it. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hallo Wols Lists, op 06-02-17 om 20:48 schreef je:
If yours is non-compliant, please ditch it.
No. :)
Cheers, Wol
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Harrie Baken | Tekstbureau TekstBaken Copy-editing - proofreading (Dutch) www.tekstbaken.nl Registered Linux user #366560 | openSUSE 13.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/17 19:50, Harrie Baken wrote:
Hallo Wols Lists, op 06-02-17 om 20:48 schreef je:
If yours is non-compliant, please ditch it.
No. :)
Sorry if that came over a bit harsh :-) and with a name like knode I'd actually be surprised if it was non-compliant. But seriously, non-compliant mailers are a pain in the neck - I use threads heavily, and there's one of my mailing lists where one poster is forever breaking threads and making keeping track of everything very difficult. Any old-time nix users will find it very frustrating. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hallo Wols Lists, op 06-02-17 om 21:12 schreef je:
On 06/02/17 19:50, Harrie Baken wrote:
Hallo Wols Lists, op 06-02-17 om 20:48 schreef je:
If yours is non-compliant, please ditch it.
No. :)
Sorry if that came over a bit harsh :-) and with a name like knode I'd actually be surprised if it was non-compliant.
But seriously, non-compliant mailers are a pain in the neck - I use threads heavily, and there's one of my mailing lists where one poster is forever breaking threads and making keeping track of everything very difficult. Any old-time nix users will find it very frustrating.
OK. I promise not to break a single thread, using my non-compliant but GREAT mailclient for imap: Thunderbird. If... you stop mailing (me) double. ;-P Harrie - just teasing a bit -- Harrie Baken | Tekstbureau TekstBaken Copy-editing - proofreading (Dutch) www.tekstbaken.nl Registered Linux user #366560 | openSUSE 13.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-06 20:48, Wols Lists wrote:
On 06/02/17 19:40, Per Jessen wrote:
Carlos E. R. wrote:
I have now to copy paste your email to be able to comment on it.
Just select it and hit reply. Works in knode.
In which case, knode is broken and non-RFC-compliant.
Yes, but if prior to hitting reply you select the text beyond the signature, it is included in the reply. I did not know this. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Wols Lists wrote:
On 06/02/17 19:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-06 19:21, Boyd Lynn Gerber wrote:
Below is all the information.
Please, never use "dash dash space newline" in the midle of an email. It signifies "end of post, start of signature", so that your entire post is deleted on compliant software when starting to reply.
I have now to copy paste your email to be able to comment on it.
Just select it and hit reply. Works in knode.
In which case, knode is broken and non-RFC-compliant.
-- Compliant to what? What *email* RFC are you talking about?
As Carlos says, any RFC-compliant mailer, upon coming across "dash dash space" on a line all by itself, will delete that line and everything else following it when you hit "reply" or "forward".
-- What email RFC? I've never heard of such a lame
And non-RFC-compliant mailers are a pain in the neck to everyone else. If yours is non-compliant, please ditch it.
-- So if you have an email reader that applies Usenet-RFC's to non-Usenet communications, wouldn't it be those email readers that are a pain to everyone else? I.e. the email readers that you and Carlos are using? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-07 04:55, L A Walsh wrote: You wrote nothing. Just a big signature. Not answering. >:-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2017-02-07 04:55, L A Walsh wrote:
You wrote nothing. Just a big signature. Not answering. >:-)
----- ROTFLOL... The RFC that mentions the "-- " as being a convention on USENET as well as being found in some email postings. However, at the beginning, it defines plain-text as having lines separated by CR+LF... Last I saw, nearly all emails on this forum used 'LF' as a separator. So technically, even if "-- " was a standard, it wouldn't apply here. :-| -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
L A Walsh wrote:
The RFC that mentions the "-- " as being a convention on USENET as well as being found in some email postings. However, at the beginning, it defines plain-text as having lines separated by CR+LF...
Last I saw, nearly all emails on this forum used 'LF' as a separator.
So technically, even if "-- " was a standard, it wouldn't apply here.
:-|
In that case, I wonder why Seamonkey is putting text below the "-- " in a paler colour? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Richmond
L A Walsh wrote:
The RFC that mentions the "-- " as being a convention on USENET as well as being found in some email postings. However, at the beginning, it defines plain-text as having lines separated by CR+LF...
Last I saw, nearly all emails on this forum used 'LF' as a separator.
So technically, even if "-- " was a standard, it wouldn't apply here.
:-|
In that case, I wonder why Seamonkey is putting text below the "-- " in a paler colour?
probably to denote it is a signature why else -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-02-07 21:19, Patrick Shanahan wrote:
* Richmond <> [02-07-17 14:23]:
In that case, I wonder why Seamonkey is putting text below the "-- " in a paler colour?
probably to denote it is a signature why else
Yes, exactly. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Wols Lists wrote:
On 06/02/17 19:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-02-06 19:21, Boyd Lynn Gerber wrote:
Below is all the information.
Please, never use "dash dash space newline" in the midle of an email. It signifies "end of post, start of signature", so that your entire post is deleted on compliant software when starting to reply.
I have now to copy paste your email to be able to comment on it.
Just select it and hit reply. Works in knode.
In which case, knode is broken and non-RFC-compliant.
Please let us know which RFC describes this reply behaviour. "pan" works the same, btw. The signature separator line is described in RFC3676, but a quick scan did not reveal anything about the reply format.
And non-RFC-compliant mailers are a pain in the neck to everyone else. If yours is non-compliant, please ditch it.
Feel free to propose another newsreader. /Per -- Per Jessen, Zürich (0.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/17 12:21, Boyd Lynn Gerber wrote:
Below is all the information.
I won't copy all of that. Looking at the discussion, it is mostly about your mail formatting. That didn't actually cause a problem here (with Thunderbird). But I'm not sure if I deleted the space after the two "--") before saving for Thunderbird to access. I'm going to assume that you installed grub in "/dev/sda1" (the first of your two attempts). But maybe you should go by the last of your attempts, since that is the one that creates the important "core.img" file beneath "/boot/grub2/i386-pc". For what you are trying to do: (1) You need generic boot code in the protective MBR of "/dev/sda". You can get that with: # cat gptmbr.bin > /dev/sda Run that as root. On my system, the file "gptmbr.bin" can be found in "/usr/share/syslinux". (2) You need to set the legacy BIOS boot flag on "/dev/sda1" and not on any other partition. You can do that with "gdisk". You will need to use the "x" command for extra features, and then the "a" command to set attributes. There's probably also a way to do it with "parted" and perhaps with "fdisk" depending on the GPT capabilities of your "fdisk". You might find it easier to just run "yast" from your chroot environment. That will give you the "ncurses" interface for "yast", which can be awkward. Get into bootloader. Make sure that the option to install generic boot code is selected. And make sure that the option to make the boot partition active is also selected. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi
Previous post but as a pastebin
http://pastebin.com/Zx7cZeGA
bootinfoscript results
http://pastebin.com/3g9fZqKu
--
Boyd Gerber
On 2017-02-10 21:45, Boyd Lynn Gerber wrote:
Hi
Previous post but as a pastebin
bootinfoscript results
You have this entry in fstab: UUID=8be3c339-609c-4115-80ce-578e0d9a0043 /boot ext4 acl,user_xattr,nofail 1 2 but that partition does not exist. However, this would not make the system go to grub rescue, but to system rescue. How do I know it does not exist? Search for the string "8be3c339-609c-4115-80ce-578e0d9a0043", it does not appear in the partition list. Main disk, sda, is GPT, but has no UEFI. It has to boot in classical bios mode. The MBR has grub, and is configured to boot (,gpt3)/grub2, which should be sda3. This paragraph confuses me: Boot files: /grub2/grub.cfg /boot/grub2/grub.cfg /grub2/i386-pc/core.img /boot/grub2/i386-pc/core.img Two locations, two grub.cfg files? sda3/boot/grub2/grub.cfg: Will try to boot menuentry 'openSUSE Leap 42.2', looking at: hd0,gpt3' 69ef0b91-ef92-4844-8693-3a7ba7beea86 Kernel line is: linux /vmlinuz-4.4.36-8-default root=UUID=556d9099-ba4f-4ca7-9888-5c83bf509c67 resume=/dev/disk/by-uuid/fc96b71f-9589-4691-b8c4-9c07462fff78 splash=silent quiet showopts From this I take that: 69ef0b91-ef92-4844-8693-3a7ba7beea86 should be the disk that holds /boot, points to sda3 556d9099-ba4f-4ca7-9888-5c83bf509c67 should be the root, but is /dev/md120 fc96b71f-9589-4691-b8c4-9c07462fff78 should be swap, but is /dev/md123 But that /boot is not in fstab. /dev/sda3 69ef0b91-ef92-4844-8693-3a7ba7beea86 ext4 newhdboot <== this is what grub thinks is /boot. /dev/sda4 f3d85405-c333-4fd8-b922-c1a35d6fcb09 swap newhdswap /dev/sda5 3089cdd8-685d-4ed6-a2ff-a64da549c6a7 ext4 newhdroot /dev/sda6 53e7901c-0052-4b55-be31-a9ba27131ea0 xfs newhdhome /dev/md120 556d9099-ba4f-4ca7-9888-5c83bf509c67 xfs hdroot0 <== this is what grub thinks is root. /dev/md123 fc96b71f-9589-4691-b8c4-9c07462fff78 swap hdswap0 <== this is what grub thinks is swap fstab: UUID=81c22f23-f341-42cf-a80c-329e3a7ae609 swap swap nofail 0 0 UUID=17645a8c-793d-43ca-acac-7b4a62bc5bc2 swap swap defaults 0 0 LABEL=hdswap0 swap swap defaults 0 0 <== matches grub /dev/md12 UUID=1b8253e5-bcb1-4573-8455-0991111dd8d2 / ext4 acl,user_xattr 1 1 <== does not match grub, and does not exist. UUID=8be3c339-609c-4115-80ce-578e0d9a0043 /boot ext4 acl,user_xattr,nofail 1 2 <== does not exist. So you see, there are several errors... I can't make a recommendation, I don't see what the intention is. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
10.02.2017 23:45, Boyd Lynn Gerber пишет:
Hi
Previous post but as a pastebin
11. grub2-install /dev/sda
You mean you did not need "--force" in this case? That not what BIS output suggests.
12. grub2-install --force /dev/sda1 13. grub2-install --force /dev/sda2
BIS output does not show any GRUB2 PBR there, so either these commands failed but you did not tell us, or you changed something after these commands were run and again did not tell us. Missing information does not make it easier to (try to) help you. Anyway, if as you say
# qemu-kvm -hda /dev/sda -boot c -m 256 -net none # shows boot menu and then boots.
I suspect some problem with BIOS/4K disks. I have seen reports about problems with such disks, but was not able to find out what was wrong for multiple reasons. Could you provide output of hexdump -C -n 8192 /dev/sda If you can configure your BIOS to boot off another disk I would install GRUB in MBR of e.g. /dev/sdb and try to boot from this HDD. Not as final solution, but as one step to determine the root cause of problem. Oh, and how did you manage to have Windows with GPT on BIOS? Do you use Windows at all? Does it boot?
bootinfoscript results
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/17 07:17, Andrei Borzenkov wrote:
I suspect some problem with BIOS/4K disks. I have seen reports about problems with such disks, but was not able to find out what was wrong for multiple reasons. Could you provide output of
For info, when 4K disks first came out, they emulated 512B disks. So any bios that assumed 512B sectors would work fine. Newer 4K disks have dropped the emulation, so that will break non-compliant bioses. The other big problem is that if your fdisk or whatever assumed 512B, they had a habit of NOT aligning on a 4K boundary. I guess this now breaks also, and even if it didn't, it clobbered performance as the emulation code was forever having to read the disk, update across boundaries, and write it back. Two reads and a write for what the OS thought was a simple write ... Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 2017-02-11 11:46, Wols Lists wrote:
On 11/02/17 07:17, Andrei Borzenkov wrote:
I suspect some problem with BIOS/4K disks. I have seen reports about problems with such disks, but was not able to find out what was wrong for multiple reasons. Could you provide output of
For info, when 4K disks first came out, they emulated 512B disks. So any bios that assumed 512B sectors would work fine. Newer 4K disks have dropped the emulation, so that will break non-compliant bioses.
The other big problem is that if your fdisk or whatever assumed 512B, they had a habit of NOT aligning on a 4K boundary. I guess this now breaks also, and even if it didn't, it clobbered performance as the emulation code was forever having to read the disk, update across boundaries, and write it back. Two reads and a write for what the OS thought was a simple write ...
That was the problem. I put in a 132 GB pen drive and now everything is
work.
Thanks,
--
Boyd Gerber
participants (10)
-
Andrei Borzenkov -
Boyd Lynn Gerber -
Carlos E. R. -
Harrie Baken -
L A Walsh -
Neil Rickert -
Patrick Shanahan -
Per Jessen -
Richmond -
Wols Lists