Hello,
Couple of weeks ago I brought external hdd WD “My passport”. Problem is that when it is connected computer can not boot. It freezes on firtt “picture” that says data about moterboard (P5LD2-X). Also in the bottom says “Press DEL to enter SETUP”, but it is the end. Computer can not continue booting. What can I do to make things better? I use LEAP 42.2.
Thank you for answer my question.
To me this looks like something coming from the BIOS. When that is true, it has nothing to do with Leap 42.2, or even with Grub. It never ever comes to loading anything from disk.
I just went thru this with a new WD 4TB “My Book” external USB 3 drive.
Most WD drives are formatted as one large exFAT partition.
exFAT support was not installed by default on my openSUSE 4.2.
So I installed:
exfat_utils
fuse_exfat
from packman.
Then your pc should no longer hang on boot.
My pc worked just fine after installing the exFAT packages - booted, mounted, and read/write the WD drives.
Of course I then deleted the partition on the WD drive and recreated it formatted XFS so I get full
support for linux permissions, links, etc.
Also, my new 4TB drive would not work correctly “out of the box” until I plugged it in to a Windows machine so it could
“initialize” itself. It seems some WD models are not shipped “ready to use”? Or perhaps this is just a req’d Windows procedure.
I did it, but nothing changed. I did not touch anything about reformated WD. Is that reason why there are no changes?
Open a terminal window ( ext hdd disconnected ) and have a look at the output of
dmesg -w
and check what is says when you connect the hdd
What if you plug in after boot?? Is it detected?
To me also it sounds like a BIOS/UEFI problem since it never gets to grub
If I plug in after boot, everything is right. It is recognized, I can access it, read and write.
Afer i did what you said (disconnected, and then connected) this appeared:
4943.580021] usb 5-1: new high-speed USB device number 9 using ehci-pci
4943.789167] usb 5-1: New USB device found, idVendor=1058, idProduct=25e1
4943.789173] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
4943.789175] usb 5-1: Product: My Passport 25E1
4943.789178] usb 5-1: Manufacturer: Western Digital
4943.789181] usb 5-1: SerialNumber: 575834314131374155445235
4943.790382] usb-storage 5-1:1.0: USB Mass Storage device detected
4943.796033] scsi host4: usb-storage 5-1:1.0
4944.796817] scsi 4:0:0:0: Direct-Access WD My Passport 25E1 1015 PQ: 0 ANSI: 6
4944.800967] sd 4:0:0:0: Attached scsi generic sg2 type 0
4944.803061] scsi 4:0:0:1: Enclosure WD SES Device 1015 PQ: 0 ANSI: 6
4944.806333] sd 4:0:0:0: [sdb] Spinning up disk…
4944.810788] ses 4:0:0:1: Attached Enclosure device
4944.810904] ses 4:0:0:1: Attached scsi generic sg3 type 13
4945.812017] .ready
4949.225125] sd 4:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
4949.227119] sd 4:0:0:0: [sdb] Write Protect is off
4949.227123] sd 4:0:0:0: [sdb] Mode Sense: 47 00 10 08
4949.228502] sd 4:0:0:0: [sdb] No Caching mode page found
4949.228505] sd 4:0:0:0: [sdb] Assuming drive cache: write through
4949.297789] sdb: sdb1
4949.302273] sd 4:0:0:0: [sdb] Attached SCSI disk
Maybe drive has both DOS and GPT partition tables and confuses the BIOS/UEFI
If so, is there anything to solve my problem?
Wipe partitioning tables and rebuild either DOS or GPT. how big is drive if over 2 TB then only GPT under and yo can use DOS but are restricted to 4 primary partition
That should be the normal case. Specially with only 1 partition.
But I admit that apart from it being a BIOS/UEFI problem (as I posted earlier), I have no idea what to do about it. Only installing the latest firmware or the BIOS/UEFI could be a standard action to take.
It might even need something like ‘Legacy USB’. But, same here, without proper info I have no idea either.
Are you using legacy BIOS or EFI?
I’m using BIOS.
Well, my guess is that BIOS tries to boot from your removable disk; content of the first block can be any random garbage that can easily hang your system. Can you provide the content of the first block (you can e.g. do “hexdump -C -n 512 /dev/sdX” where sdX refers to your disk and post output here)?
When I do it in terminal (type what you quoted), this happens:
hexdump -C -n 512 /dev/sdX
hexdump: /dev/sdX: No such file or directory
hexdump: all input file arguments failed
Can you modify the boot order, so that it does not attempt to boot from a removable or USB device unless the boot sequence is interrupted by pressing a function key to display a boot device menu?
Hummm replace X with the letter of the drive 
if not sure run fdisk -l to list the drives to determine the letter