Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Disk /dev/sda: 73.5 GB, 73543163904 bytes
255 heads, 63 sectors/track, 8941 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 33 265041 83 Linux
/dev/sda2 8805 8941 1100452+ 82 Linux swap / Solaris
/dev/sda3 34 8804 70453057+ 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table
****** NOT USING /dev/sdb AT ALL ******
Created two 16 GB files on devices /dev/sda and made them iSCSI devices.
After setting up iSCSI devices
#fdisk -l
Disk /dev/sda: 73.5 GB, 73543163904 bytes
255 heads, 63 sectors/track, 8941 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 33 265041 83 Linux
/dev/sda2 8805 8941 1100452+ 82 Linux swap / Solaris
/dev/sda3 34 8804 70453057+ 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 73.4 GB, 73407868928 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 17.1 GB, 17179869184 bytes
64 heads, 32 sectors/track, 16384 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 16384 16777200 fd Linux raid autodetect
Disk /dev/sdd: 17.1 GB, 17179869184 bytes
64 heads, 32 sectors/track, 16384 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 16384 16777200 fd Linux raid autodetect
/dev/sdc and /dev/sdd are the new iSCSI devices which i created. I have one partition in each with fd option.
Disk /dev/md0: 34.3 GB, 34359476224 bytes
2 heads, 4 sectors/track, 8388544 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id System
/dev/md0p1 1 62501 250002 83 Linux
/dev/md0p2 62502 8312502 33000004 83 Linux
/dev/md0p3 8312503 8388544 304168 83 Linux
______________________
NOTE: just FYI
when i try to do
#mkfs.ext3 /dev/md0p1
mke2fs 1.39 (29-May-2006)
Could not stat /dev/md0p1 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
First of all, regenerate the initramfs image and see if your problems go away. If not, unpack the initramfs image and see if it contains the md and raid0 drivers, and md tools. If not, you may need to tweak the initramfs generation scripts to ensure that the drivers are included in the image and loaded, and that the md config file and tools are included and run as appropriate.
How you regenerate the initramfs image depends on your particular distro; for Debian it's simply: dpkg-reconfigure linux-image-$(uname -r)
How you regenerate the initramfs image depends on your particular distro; for Debian it's simply: dpkg-reconfigure linux-image-$(uname -r)
Pinniped, Thank you for this post! Newbie with a RAID controller and Linux here...
I recently bought a Areca 1220 RAID controller. I was having difficulty getting my hdd on my motherboards hdd controller to boot. I had an error message with something like "FAILED! /dev/sda1 was not found! Dropping to a shell!"
I'm not sure if it's a problem with Debian that needs to be reported? The arcmsr driver is built into the kernel for Debian Lenny (kernel 2.6.26-1) and both the OS hard drive and the RAID array where correctly displayed when installing. However after reboot a "dpkg-reconfigure linux-image-$(uname -r)" needs to be done.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.