SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
In order to get a clearer picture of your setup, how about downloading the Boot Info Script to your desktop, and then do the following as root user, but replace <username> with your user name:
That will create a "RESULTS.txt" file in the same directory from where the script is run, namely your desktop; please copy/paste the contents of the RESULTS.txt file to your next post. That will help clarify your setup and hopefully what the solution to your problem might be.
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x06706357
Partition Boot Start End Size Id System
/dev/sda1 63 1,992,059 1,991,997 82 Linux swap / Solaris
/dev/sda2 1,992,060 21,992,984 20,000,925 83 Linux
/dev/sda3 21,992,985 625,137,344 603,144,360 8e Linux LVM
/dev/root on / type ext3 (rw,errors=continue,data=ordered)
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/mapper/slackvg-home on /home type ext3 (rw)
/dev/mapper/slackvg-usr on /usr type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /media/disk type ext3 (rw)
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 10
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
# Linux bootable partition config ends
=================== sda2: Location of files loaded by Grub: ===================
7.4GB: boot/vmlinuz
7.4GB: boot/vmlinuz-generic-2.6.27.7
7.3GB: boot/vmlinuz-generic-smp-2.6.27.7-smp
7.3GB: boot/vmlinuz-huge-2.6.27.7
7.4GB: boot/vmlinuz-huge-smp-2.6.27.7-smp
=======Devices which don't seem to have a corresponding hard drive==============
According to the script results, your 320 GB sda drive is using lilo to boot, and your 500 GB sdb drive has a Windows MBR (not Grub); so I don't understand where you are getting a Grub error from. Are there any other drives present on start up that might have Grub in their MBR? I think if you make sure your 320 GB slackware drive is first in the BIOS boot order, you shouldn't have any more problems. Let me know how that goes.
So...here i am...back...In bios a can't put for first boot device the sda(320GB) HDD.The BIOS can see only the hdd in the rack when i plug it in...Also 500 GB sdb drive has Windows MBR. Is there any way to change this from its MBR or something else to make the rack hdd work..? Im confused...:S:S Thanx once again...
Did you have your HDD rack connected when you ran the script in post #4? It doesn't look like it, because the script only showed your 320 GB and 500 GB drives. How about plugging in your rack HDD, boot a Live CD, run the script from the Live CD, and post the output. Also, since you can't change your BIOS boot order, we will need to know what boot order the HDDs are in when you connect the HDD in the rack. To figure that out, how about downloading the Super Grub Disk, boot that, and at the first main menu press "c" to get the command line, and do:
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x06706357
Partition Boot Start End Size Id System
/dev/sda1 63 1,992,059 1,991,997 82 Linux swap / Solaris
/dev/sda2 1,992,060 21,992,984 20,000,925 83 Linux
/dev/sda3 21,992,985 625,137,344 603,144,360 8e Linux LVM
/dev/root on / type ext3 (rw,errors=continue,data=ordered)
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/mapper/slackvg-home on /home type ext3 (rw)
/dev/mapper/slackvg-usr on /usr type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sdb1 on /media/disk type ext3 (rw)
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 10
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Linux
read-only
# Linux bootable partition config ends
=================== sda2: Location of files loaded by Grub: ===================
7.4GB: boot/vmlinuz
7.4GB: boot/vmlinuz-generic-2.6.27.7
7.3GB: boot/vmlinuz-generic-smp-2.6.27.7-smp
7.3GB: boot/vmlinuz-huge-2.6.27.7
7.4GB: boot/vmlinuz-huge-smp-2.6.27.7-smp
=======Devices which don't seem to have a corresponding hard drive==============
It looks like you've first got to get your Live CD to see the HDD rack when it is connected, because currently whichever Live CD you used did not even detect any other drives than your sda/sdb drives. You can always check which HDDs linux sees by doing:
Code:
sudo fdisk -lu
So you probably need to change your BIOS settings for the rack HDD, but until you can get the rack HDD even recognized in linux, it doesn't seem like there is much point to even having it hooked up if it is inaccessible. You might want to also check the jumper settings on the HDDs in the rack.
So...listen at this...I press F8 at booting and select 320G hdd to boot and it boot perfect...Now i can se and the rack hdd but i have to correct it from BIOS..not to have always F8 :P
Quote:
Disk /dev/hdd: 10.1 GB, 10110320640 bytes
255 heads, 63 sectors/track, 1229 cylinders, total 19746720 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x0003da09
Device Boot Start End Blocks Id System
/dev/hdd1 63 19743884 9871911 83 Linux
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x06706357
Device Boot Start End Blocks Id System
/dev/sda1 63 1992059 995998+ 82 Linux swap
/dev/sda2 1992060 21992984 10000462+ 83 Linux
/dev/sda3 21992985 625137344 301572180 8e Linux LVM
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x076f5e24
Device Boot Start End Blocks Id System
/dev/sdb1 63 976768064 488384001 83 Linux
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.