LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Linux - Hardware (http://www.linuxquestions.org/questions/forumdisplay.php?f=18)
-   -   Boot problems (http://www.linuxquestions.org/questions/showthread.php?t=4175442923)

asd0z 12-25-2012 04:06 PM

Boot problems
 
Hi everyone

I have bought new external HDD. I want to install linux on it and is ready for experiments.

There are several problems with the disk:

1. the disk has USB3 => BIOS or grub2 can be unable to boot from USB3 (i dont know about support status; it is ok to start with USB2 port).

2. the disk is more than 2TB (3TB actually) => have to use GPT (but it is ok to start with MBR label).

3. and the worst thing disk is 4096 (4KB) sector size. (seems like both: physical and logical :().

4. BIOS doesn't recognize disk and turn its power off.


I want to start with booting OS located at external disk from another grub by chainloading.

The problem is grub2 does not see second drive (hd1). But grub2 can see other USB flash without external power (thumb drive) by the way. But with new HDD I turn on PC, USB HDD starts spin up, work for a while and spin down. USB HDD visible in OS but not in grub2.



How to force grub2 to see USB HDD and scan it for partitions?


OS: Fedora 17
Drive: SEAGATE Expansion STBV3000200 USB 3.0, 3.5" 3Tb

jefro 12-25-2012 04:25 PM

"
4. BIOS doesn't recognize disk and turn its power off."

You have to fix this first. Bios must see the drive as either an internal hard drive choice or some other usb type choice.

Shadow_7 12-25-2012 06:34 PM

from the grub command line (grub2 anyway). Not sure about any usb3 tidbits, but this is how I boot my laptop (chainloaded I suppose) from a grub boot cd. Bios does not support booting usb directly on said laptop. And I run linux on a cruzer 8GB flash stick for that old laptop.

grub> insmod uhci
grub> insmod ohci
grub> insmod usb
grub> ls

If your device isn't powered and listed (partition) at this point, you've got other concerns.

grub> insmod part_msdos
grub> insmod ext2
grub> configfile (usb0a,msdos2)/boot/grub/grub.cfg

The device,partition is as listed via the "ls" on the first half. And the configfile has to be 100% correct as in UUID's (partition specific), or it's almost pointless. And of course /etc/fstab for the linux in question with UUID's since usb is even more quirky than a motherboard with both SATA and PATA (IDE) drives. And it might have been me, or update-grub that put /dev/ into the grub.cfg. The source of my epic fail on first attempts. As in works on one machine (sometimes) and never on another (the actual destination machine). Using UUIDs across the board fixed that quirk.

Baring all this you might see if plop boot manager gives you any joy. The most braindead solution I've seen, although not the most intelligent, just a generic list with no sensing of what is actually there. But it worked for me out of the box until I dotted all the i's and crossed the t's on the grub2 solution.

malekmustaq 12-25-2012 09:25 PM

Quote:

from the grub command line (grub2 anyway). Not sure about any usb3 tidbits, but this is how I boot my laptop (chainloaded I suppose) from a grub boot cd. Bios does not support booting usb directly on said laptop. And I run linux on a cruzer 8GB flash stick for that old laptop.

grub> insmod uhci
grub> insmod ohci
grub> insmod usb
grub> ls

If your device isn't powered and listed (partition) at this point, you've got other concerns.

grub> insmod part_msdos
grub> insmod ext2
grub> configfile (usb0a,msdos2)/boot/grub/grub.cfg

The device,partition is as listed via the "ls" on the first half. And the configfile has to be 100% correct as in UUID's (partition specific), or it's almost pointless. And of course /etc/fstab for the linux in question with UUID's since usb is even more quirky than a motherboard with both SATA and PATA (IDE) drives. And it might have been me, or update-grub that put /dev/ into the grub.cfg. The source of my epic fail on first attempts. As in works on one machine (sometimes) and never on another (the actual destination machine). Using UUIDs across the board fixed that quirk.

Baring all this you might see if plop boot manager gives you any joy. The most braindead solution I've seen, although not the most intelligent, just a generic list with no sensing of what is actually there. But it worked for me out of the box until I dotted all the i's and crossed the t's on the grub2 solution.
To the OP, if it worked with you this post by Shadow 7 is rare and excellent: it deserves an appreciation.

asd0z 12-26-2012 03:04 AM

Quote:

Originally Posted by jefro (Post 4856711)
"
4. BIOS doesn't recognize disk and turn its power off."

You have to fix this first. Bios must see the drive as either an internal hard drive choice or some other usb type choice.

I cannot do anything with it: sometimes helps to wait POST and reboot but not in my case. BIOS update hasn't helped too. That is why i want make boot loader to see this disk.

I will try insmod *.

Shadow_7 12-26-2012 08:20 AM

# grub-mkrescue -o grub_eltorito.iso
$ k3b grub_eltorito.iso

To make a basic grub boot disk (with grub2 already installed on your existing system). And the things that you can insmod can be found as .mod files in /boot/grub/. (in theory)

$ ls /boot/grub/*.mod

asd0z 12-26-2012 10:53 AM

I have tried this from my internal hdd grub2:

Code:

menuentry "usb3" {
insmod uhci
insmod ohci
insmod usb
# following modules not exist in my system, but they were in usb ubuntu server tutor
insmod xhci_hcd
insmod usbhid
insmod hid
insmod usb_storage

ls
insmod part_msdos
insmod ext2
insmod ntfs
ls
}


Negative result. Grub2 see only (hd0) which is internal. It doesn't try to power on external disk while loading new modules.

(Shadow_7, is rescue act something different, should i try it?)

OS obviously sent some commands to USB HDD to power it on. Grub2 should be able to do the same. It either has some unknown command for this or it is just not implemented.

Shadow_7 12-26-2012 11:37 AM

It looks like usb3 might have some relation to efi and xnu. So you could try insmod'ing in grub the following modules (in addition to the usb ones).

grub> insmod efiemu
grub> insmod xnu
grub> insmod xnu_uuid

And see if that gives any additional joy.

Most of my tech is old, usb3 is not in my arsenal to play with at the moment. But if it is supported insmod for all *.mod files in /boot/grub should load the module(s) needed for usb3 support. At which point the ls command (in grubs command line mode) should show what it calls the device. If there is support and it works.


All times are GMT -5. The time now is 05:26 AM.