CentOS 5 :: Chainloading 2nd Sata Drive Partition 5?
Mar 5, 2011
I am still fighting with getting the right configuration in my grub file to chainload the second linux OS on my computer.
2 hard drives (sata)
2 OS's (CentOS,Ubuntu)
CentOS is in and running fine. It owns the MBR and was in place before I added the Ubuntu OS. Ubuntu was added to the free space of the second hard drive in partition 5 and its grub was installed there. So I thought this would work for a grub stanza.
ubuntu 8.04 server can not detect seagate sata hard drive 2tb or sata Lg dvdrw x22 sata drive .is it possible to install it without buying a pci ide sata card?is it possible to get a driver for sata driver and sata drive that can be recognise by ubunto 8.04 server ?or to get the files for 1.44 floppy diskdoes the late edition of unbutu recognise sate hdd and sata cdrw drive automaticly during the installation of the unbutu?
OpenSUSE 11.2 server, Gigabyte GA-MA790X-UD4P sda for system, 3 ext4 partitions, working fine.sdb promise RAID1 for data, 1 ext4 partition, working fine.sdc is an eSATA docking station for data backup, 1 encrypted ext4 partition -- here lies the problem.
This configuration has been functional for months until I decided to add two more external drives (sdc) to rotate through backups. I had difficulty with encyption on the first new drive and eventually decided to start over. Using the gui Yast Expert Partitioner, I deleted the single partition. That began a real nightmare...
Since deleting the partition, the system detects drives inserted in the docking station, but does not report them (including a different fully functional drive and a brand new unused drive). I have tested all drives on other computers and they function perfectly. I have rebooted the system several times while troubleshooting this issue.
Could not recreate the partition on server (since it does not recognize the drive), so I used Gparted on another computer - it all went without a hitch, formatted ext4. But when I placed the drive in the dock, the drive still was detected but not recognized.
So how did partition deletion cause this issue, and how do I correct the problem? It is possible that my difficulties encrypting the first new drive are related (it's not my first time doing it successfully). It seems the problem is in the Kernel or configuration. I have invested many hours in forums and on google - tried dozens of possible fixes. I'm beginning to suspect system corruption or a bug, however all other system functions are working perfectly.
Alright, what I thought would be a simple task has me tied in knots.
I wanted to make a multiboot USB flash drive that I could easily manipulate to switch to various distros easily. My plans were:
1. Partition my 8GB drive to one large first partition (5GB) so that windows could access it. (P.S. GParted didn't partition correctly, needed to use fdisk. THIS MIGHT BE IMPORTANT IN SOLVING THE PROBLEM BECAUSE THERE MIGHT BE A BLOCK ERROR). I then made an extended partition with 5 500MB logical partitions.
2. Install Grub2 to MBR from Ubuntu
3. Expand ISO's of varios distros (Acronis Recovery, Puppy linux, etc.) to the partitions, and create syslinux.cfg files for each (from the isolinux.cfg files that were already there)
4. Install syslinux to each partition's boot sector
Code: #syslinux /dev/sdb5... 5. make grub.cfg on /dev/sdb1 chainload each partition.
THE GRAND PROBLEM:
Grub2 loads, but when selecting what I want to boot, I get the error
which is syslinux, not grub2. So I know it's chainloading, but syslinux doesn't seem to find ldlinux.sys.
P.S. I'm not asking for other ways to make a multiboot drive, I know I can just direct boot from Grub2, but I want to be able to pass the boot to the boot loaders on the other logical partitions.
I have a new system using an Intel DG451D main board. I have been trying to get a RAID 1 mirror set working as the main drive in this system and for some reason, my SATA drives - three of them all new have had their SMART data changed to show the drives as failing and in need of replacement. Eventually the drive reports failure to the degree that the BIOS no longer recognises it. When loading the Centos os I was getting differing results because of this issue. I am not sure if this is a hardware issue even - I know that the drives were all very much OK and brand new - no good now! Just putting a feeler out to see if anyone has had a similar issue or to see if anyone knows of any possible known causes for this?
Failing any explanation, can anyone suggest a good desktop style Main Board that supports RAID well for Centos 5.4? I plan to sue this as a small server system so graphics etc are not important here.
extended sata partition shrunk at 15 partition limit, how to re-enlarge i hit the 15 partition limit, forgetting it now exists for sata drives, thinking i would add more. upon creation of the 15th, it squished the end of the extended partition to meet the last logical partition, leaving a large unallocated portion after the extended partition, which seemingly nothing can be done with, just sat being wasted space. i have since deleted a few of those partitions, but so far have still failed to find a way to recoup the unallocated space back into the extended partition.
if necessary, i'll do it the painful long winded way of backing up and starting the extended partition again from scratch, but i really rather wouldnt have to do that. i'm sure there must be a way of telling the extended partition to once again reach the end of the drive.
I keep getting this error in my log viewer every 2 seconds: Code: ata4: limiting SATA link speed to 1.5 Gbps I have a dual boot SSD and I have run many SMART tests in windows and linux, (using smartmon tools and the disk utility) and the reports are all 100% healthy..... My research shows that this error represents one of the following:
1. Problem with SATA controller 2. Changing BIOS to allow SATA 3. Changing SATA mode to PATA or AHCI 4. Replacing the SATA cable 5. Allowing the SSD to run at SATA II speeds, i.e. 3 Gbps
- Does anyone know how to try number 5, i.e. allowing the SSD to run at SATA II speeds? I am lost here and this problem has caused my machine to crash twice when watching a movie in linux/ ubuntu. (It is worth noting that the crashes have only occurred in linux and I have never had an issue in windows, so it does seem to be a linux setting somewhere, hence why I think it is a "allowing SATA II to run at correct speeds issue")
The installer can't see my raid controller (I assume) as I'm getting the following error:"Error opening /dev/mapper/isw_jbhgjgjj_Vol0: No such device or address"It just sees them as 4 individual drives: sda, sdb, sdc and sdd.Please note that I have set up the RAID 5 in the controller bios interface and the image name is Vol0, which it seems that it tries to load but for some particular reason it can't.I have also tried different bios settings and nothing worked.
I have Ubuntu 10.04 LTS just installed on my IDE 41Gb HDD. After installation, I plugged in a SATA 320 Gb HDD. I ran gparted, I partitioned the HDD in 3. It was recognized as sda1... I could see the 3 partitions in my "Places" renamed as I wanted, could see my IDE HDD and my external 1TB HDD. But after one day, computer was not turned off, I come back to it and... couldn't see what I previously had done (my 3 partitions on SATA just vanished?). I reset the PC and go in BIOS - nothing there. Turn off PC, reboot>BIOS> HDD SATA 2 recognized. Press F10 save, Ubuntu is up, but still no SATA hard disk. I go to gparted... no option with SATA. What can I do to have it back? I didn't mount anything since during partition I didn't have this option. This is what shows up now: (the 41 Gb HDD is now sda, before was sdb - I guess because it is smaller?)
bogdan@LORD:~$ sudo parted -l [sudo] password for bogdan: Model: ATA HDS728040PLAT20 (scsi) Disk /dev/sda: 41.2GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 39.4GB 39.4GB primary ext4 2 39.4GB 41.2GB 1734MB extended 5 39.4GB 41.2GB 1734MB logical linux-swap(v1)
Ive installed ubuntu for the first time today, i have a hdd of 500gb, that had 65gb occupied with music, movies and games.
What i did during installation:
it asked me where to install it, so i created a new partition of 100gb ext4 type, to install it there, and i was going to leave the rest for the data, but it wont let me do it, so i went back and selected the "exchange type swap linux 0x82 type" for the 400gb partition.
Then installed it, and now i cant find my data, and i have only 100gb of space in the hd, if i use the "disc utility" i can see the other 400gb, and change partition type, but i dont want to lose my data..
I'm trying to install 10.10 on a sata disk. In terminal, dmesg recognizes the disk at /dev/sda. The installer recognizes it as well, but the partition area is blank and the option are greyed out. How can I go on? BTW, on the disk currently Fedora 14 is (fresh) installed and working fine, but a software install script is written specifically for Ubuntu. That's why I need to change to Ubuntu and it's no hardware problem.
This thread is not so much looking for a 'solution' as it is looking for some 'reason why', as I now have it working.I have just inherited a Gateway 509GE - P4 3.0GHZ / 1GB RAM / 200GB SATA WD2000JD HD. It is circa 2005 hardware. The previous owner had tried to install Mandriva after windows began to choke on accumulated garbage, then tried to revert to XP, both of which appeared to install but neither would boot. He decided to just get a new box and gave me this one.I ran Memtest86 and found a bad DIMM and replaced it.
I repartitioned and formatted, a single ext4 root partition plus 2GB for swap. I completely removed existing partitions including the hidden M$ restore partition and checked disk - all using Gparted Live CD.I put a full Slackware 13 on it, installed with LILO to MBR, rebooted... nothing... "No bootable device found".I booted to install CD and played with Gparted Live CD and everything was there and LILO configured correctly...I tried several times and looked at MBR sector directly - all OK as far as I could tell.
Long story short - as far as I can tell after trying a few things, I finally set the 'active' flag on the extended partition (sda1) and it now boots.But Linux does not care whether a partition is active and I have several boxes - including another with SATA drive that do not have any 'active' partitions. So I conclude this must be a BIOS thing looking for an active partition, but see nothing settable in the BIOS config (in fact very little useful in this machine's BIOS config).Anyway, it is now working but I would like to solicit any useful comments from others. Is it a Gateway thing? (This is my only Gateway box). Is it an SATA thing? Anyone else had to set a Linux partition active to boot
We have an external raid box connected to a debian squeeze server.Every new volume set I have created will be detected (as /dev/sdx) after a reboot. As this is our file-server I cannot reboot the server every-time a new volume set is created.Is there a way to make this new device visible.I tried already 'partprobe' and restarting udev didn't work eather.What is a good way to do this?
I have just installed opensuse 11.4 and the install fails to boot, grub hangs or gives an error.
I have tried installing grub in MBR and root changed every setting I can find and even downloaded a fresh ISO. As a last resort I changed the machines BOIS settings from SATA to emulate ide, booted as expected but a bit slow.
11.2 and 11.3 worked on this machine with no problems. Am i missing something? I also tried an Ubuntu install and this worked fine!
I have tried to install ubuntu onto my computer using the live CD. It installed fine, and it put grub on sda (which linux sees as my SATA drive). Windows is installed on the ide drive which linux see's as the sdb drive. It was a successful install and in theory it should work, except it find the windows install first so it boots into windows without using grub. I think that linux assigns the drives using the sata first and the ide second, but windows does the opposite and the ide drive is first and the sata is second.
Is it possible to install grub onto the ide drive and get it to dual boot linux or is it possible to use the windows bootloader to recognize the linux install and chainload grub? I am thinking that if I use grub on the ide drive it will throw an error like what happened during my wubi install and it is unable to find the kernel because it is looking for it on sda, but from a windows install it is sdb. I have tried to get the computer to boot from the sata drive, but the mobo is a bit old and I do not think it is supported.
I'm having a bit of a problem enabling any sort of permissions for my 1TB SATA HDD on /dev/sda1. Using Nautilus and wine, I'm trying to play games already pre-installed on my Windows 7 partition. When ever I right-click>permissions>Enable execution, it reverses the changes. I don't know if this is relevant, but id rather not copy anything on to my /dev/sdb2/ partition because its about 1/10th the size of sda1 (142GB free to be exact). Is their any way to make a permanent change? I don't really mind if it's a solution in the terminal... So long as it doesn't mess up my ability to boot Windows 7.
I have a HP PC that I have installed a PCI SATA controller in. The PC doesn't support booting from the card.... So here is what I would like to do. (btw..I'm a seasoned noob on Linux.) I would like to be able to boot ubuntu 10.10 from a usb pin drive 2Gb to a point where the kernal can recognize the SATA drive then start the OS from the SATA HDD.
I can see and access the drive if I boot to a live CD but when I install it won't boot because the PC's bios does not see the PCI card. This has to be possible but my Google foo isn't strong enough to find out how. Would a simple GRUB install on the pen drive work?
I recently installed a PCI Sata card along with a SATA HDD and a SATA DVD burner. My PC ogirinally used /dev/sda1 to boot into root. But now when I plug the new HDD in, it names the SATA drive /dev/sda and the SCSI drive /dev/sdb.
I have unplugged the SATA drive and am able to boot into linux. I can also use the DVD burner. In the lilo.conf file, I have rename the root to /dev/sdb1 so when I plug the SATA drive in and reboot, it should go to sdb1 for root. But here is the error that Im getting.
VFS: Cannot open root device "801" or unknown-block(8,1) Please append a correct "root=" boot option; here are the available paritions 0800 488386584 sda driver: sd 0b00 1048575 sr0 driver: sr
I have a number of drives that I am setting up for friends who wish to switch/alternate from Windoze. So far several completed. One particular drive is being a bit difficult. When checked on my system[10.10] by Sata/USB wire it reads OK and gives the following info. 200GB, 768kb used, file sys Ms-Dos
When installed on the Mobo as main drive and machine booted set to boot from HD it sometimes reports 'No Drive Found' Reset the BIOS to boot from CD and Load Ubuntu from DVD- it goes through load routine then reports 'Error- cannot Mount drive[or words to that effect] Tried installing frm CD/DVD drive to the disk via the SATA/USB wire But that failed also with CD Auto load error So the disk seems to need setting up in some way to suit Linux presumably just like FDisk in Dos/Windoze
I tried to load Red Hat Linux 4 on my PC, which has 945 MB, Core 2 Duo Processor, 2GB RAM, 250GB SATA HDD. But i couldnt do so as it did not detect the hard drive and was asking for drivers. I changed the SATA settings to Legacy but still it didnt recognise the HDD...I have Windows XP SP3 also installed on it.
I've installed debian squeezy recently and for some reason I have problems with mounting /home partition during startup.
There's an error:Mounting local filesystems...mount: special device /dev/mapper/isw_bbfedcffgi_Volume0p6 does not exist. failed
I've tried using fsck - no result the file system is healthy, I've tried formatting it once again (fresh copy, no user data) and it's not working. What is more mounting the partition manually goes well - I can read the data and write to it. All other partitions are ok.
I have no idea what's going on and why mounting /home fails. I've written this post on Polish debian users forum, but no response - only to give more info, so I'll put it here also:
ls -al /dev/mapper
crw------- 1 root root 10, 59 Nov 9 19:34 control lrwxrwxrwx 1 root root 7 Nov 9 19:34 isw_bbfedcffgi_Volume0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Nov 9 19:34 isw_bbfedcffgi_Volume01 -> ../dm-2 lrwxrwxrwx 1 root root 7 Nov 9 19:34 isw_bbfedcffgi_Volume05 -> ../dm-3 lrwxrwxrwx 1 root root 7 Nov 9 19:34 isw_bbfedcffgi_Volume06 -> ../dm-4 code....
I am trying to install Debian 5.0 "Lenny" on a PC with a very new hardware config (i3 processor, DDR3 RAM,LG SATA DVD drive, and Seagate SATA HDD). During the hardware detection phase of installation, I get a message saying the driver for my CD drive is not known, and asking me to select one manually. The options I get are only 'devcdrom', which does not work, and my installation cannot proceed.
I tried the following:
1. I read in a similar query that to use SATA DVD drives, I will have to set some boot options, so tried entering install libatapi_enabled=1 as an install option. This showed 'unknown parameter' error followed by same problem.
2. My Intel m/b BIOS has an option to set the DVD drive to "Native" or "Legacy", default is Native. I also tried changing this to "Legacy". Still same problem.
3. Read that I have to point to different drivers, but don't know how to do this during the installation.
I have a working F-10 box with an older motherboard (pre-sata). The p-ata ports are full (4 drives), so I'm trying to add a sata controller and another drive. The sata controller plugs into the pci bus, but is not detected by the bios (very old). After booting, the OS loads the driver module(s) and detects the new controller and drive. I was able to add the new sata drive into the LVM system using system-config-lvm. All was fine until I rebooted.
I get pages of lvm errors and booting fails. It looks like it's trying to mount the volumes before the sata controller is modprobed. Is there a way to get the os to modprobe for the new controller before trying to mount? The extra drive space is on a data partition, not the boot partition.