LinuxQuestions.org - Problem on booting after re-allocating SATA connection

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - Problem on booting after re-allocating SATA connection (https://www.linuxquestions.org/questions/ubuntu-63/problem-on-booting-after-re-allocating-sata-connection-4175537501/)

Problem on booting after re-allocating SATA connection

Hi all,

This is an old box (spare) which has not been run for sometimes. Because of the problem of a defective SATA connector on the motherboard I just re-allocated the HDs connection on SATA connectors

Available SATA connectors on motherboard = 5, one defective

Original setup: dual boot as follows, selected on motherboard BIOS

Hard drives:
1)
WD HD (1.5TB) - Ubuntu 14.04
running Oracle VirtualBox

2)
SSD (120G) - Debian OS
Seagate HD (640G) - for running VMs

Booting 1) Ubuntu 14.04 following warning popup

Code:

error: diskwriter writes are not supported

Press any key to continue

ALT+F2 doesn't work

Press "Ent" to continue

Warning

Code:

The disk drive for /medit/ssd is not ready yet or not present

Continue to wait, or Press S to skip mounting or M for manual recovery

Press S to boot Ubuntu 14.04

$ cat /etc/fstab

Code:

# /etc/fstab: static file system information.

#

# Use 'blkid' to print the universally unique identifier for a

# device; this may be used with UUID= as a more robust way to name devices

# that works even if disks are added and removed. See fstab(5).

#

# <file system> <mount point>  <type>  <options>      <dump>  <pass>

proc            /proc          proc    nodev,noexec,nosuid 0      0

/dev/mapper/LVM1.5D-root /              ext4    errors=remount-ro 0      1

/dev/mapper/LVM1.5D-data /data          ext4    defaults        0      2

/dev/mapper/LVM1.5D-swap none            swap    sw              0      0



/dev/debian731/root    /media/ssd      ext4    defaults        0 0

Unable to boot
2)
SSD - Debian OS
WD HD - for running VMs

Warning

Code:

Reboot and Select proper Boot device

or Insert Boot Media in selected Boot device and press key

Please help. Thanks

Regards
satimis

Are you using grub-pc to boot with (grub2)?

Have you checked in your bios to make sure all sata ports are enabled?

Bios determines what the designation of the drives are. You will need to find out what those designations are and edit your boot loader to account for this.

Quote:

Originally Posted by widget (Post 5336154)

Are you using grub-pc to boot with (grub2)?

Yes. The last time about one month ago I still can boot Debian on SSD but all VMs couldn't be connected. Later I discovered one SATA connector of the motherboard died. For such a reason I re-allocated all SATA connection

Quote:

Have you checked in your bios to make sure all sata ports are enabled?

Yes. All enabled with SSD and HD detected

Quote:

Bios determines what the designation of the drives are. You will need to find out what those designations are and edit your boot loader to account for this.

Yes. It worked without problem before booting Debian.

This box is quite old and I have intention to replace it. My daily working desktop is also a little bid old, about 3~4 years. I'm also prepared building a new desktop to replace it.

Planning config of new desktop:-
AMD 8-core CPU
32G RAM
1 TB SSD for installing OS as well as VMs

Current Daily working desktop - config:-
AMD 8-core CPU
Motherboard ASUSTeK COMPUTER INC.
Product Name: M5A97 R2.0
Version: Rev 1.xx
Serial Number: 120801426800789
32G RAM
120G SSD for installing OS - Ubuntu 12.04
2T WD black-label HD for running VMs

I'll move the 32G RAM to the new desktop and move the 8G RAM from this problem desktop to the current daily working desktop making it as spare desktop.

The price of 1TB SSD is still quite expensive. I'm waiting for its price to drop.

Regards
satimis

That seems to cover it pretty well. Don't see, at all, how booting to any particular install could screw things up like that.

My impulse is to think it has something to do with LVM but I have no basis for that except prejudice against LVM on things other than servers.

Running the boot info script and posting the results would be the best bet for either seeing the problem yourself or for some one here to see it.
http://bootinfoscript.sourceforge.net/