Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
06-20-2006, 03:28 PM
|
#1
|
Member
Registered: Apr 2004
Distribution: RedHat, Fedora, Suse, Debian, Gentoo, Mandrake
Posts: 132
Rep:
|
RAID 1 on SATA "RedHat 4"
Hi
I got a problem while and after installing RHEL4 update3
tiring to install RAID1 on SATA hard drives
250 G each
'it boots looks ok but'
when I do fdisk -l
I always get a massage like that
#======================================================
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 257008+ fd Linux raid autodetect
/dev/sda2 33 7681 61440592+ fd Linux raid autodetect
/dev/sda3 7682 12780 40957717+ fd Linux raid autodetect
/dev/sda4 12781 30401 141540682+ 5 Extended
/dev/sda5 12781 16604 30716248+ fd Linux raid autodetect
/dev/sda6 16605 18516 15358108+ fd Linux raid autodetect
/dev/sda7 18517 19791 10241406 fd Linux raid autodetect
/dev/sda8 19792 20052 2096451 fd Linux raid autodetect
/dev/sda9 20053 30401 83128311 fd Linux raid autodetect
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 32 257008+ fd Linux raid autodetect
/dev/sdb2 33 7681 61440592+ fd Linux raid autodetect
/dev/sdb3 7682 12780 40957717+ fd Linux raid autodetect
/dev/sdb4 12781 30401 141540682+ 5 Extended
/dev/sdb5 12781 16604 30716248+ fd Linux raid autodetect
/dev/sdb6 16605 18516 15358108+ fd Linux raid autodetect
/dev/sdb7 18517 19791 10241406 fd Linux raid autodetect
/dev/sdb8 19792 20052 2096451 fd Linux raid autodetect
/dev/sdb9 20053 30401 83128311 fd Linux raid autodetect
#======================================================
Disk /dev/mdN: 62.9 GB, 62915084288 bytes
2 heads, 4 sectors/track, 15360128 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk /dev/mdN doesn't contain a valid partition table
#======================================================
and the output of mdadm -D /dev/mdN
/dev/mdN:
Version : 00.90.01
Creation Time : Tue Jun 20 13:43:49 2006
Raid Level : raid1
Array Size : 10241280 (9.77 GiB 10.49 GB)
Device Size : 10241280 (9.77 GiB 10.49 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 6
Persistence : Superblock is persistent
Update Time : Tue Jun 20 14:55:57 2006
State : dirty
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
0 8 7 0 active sync /dev/sdaN
1 8 23 1 active sync /dev/sdbN
UUID : f55241be:4580603f:a0abab71:2685099e
Events : 0.16
#=======================================================
and /etc/fstab look like that
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/md3 / ext3 defaults 1 1
/dev/md0 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
/dev/md2 /home ext3 defaults 1 2
none /proc proc defaults 0 0
/dev/md5 /servers ext3 defaults 1 2
none /sys sysfs defaults 0 0
/dev/md6 /tmp ext3 defaults 1 2
/dev/md1 /usr ext3 defaults 1 2
/dev/md4 /var ext3 defaults 1 2
/dev/md7 swap swap defaults 0 0
/dev/hdc /media/cdrom auto pamconsole,fscontext=system_u:.object_r:removable_t,exec,noauto,managed 0 0
#==============================================================
So should I to worry about this message
"Disk /dev/mdN doesn't contain a valid partition tabble" or not?
#==============================================================
Thanks
|
|
|
06-21-2006, 12:41 PM
|
#2
|
Senior Member
Registered: Oct 2003
Location: /earth/usa/nj (UTC-5)
Distribution: RHEL, AltimaLinux, Rocky
Posts: 1,151
Rep:
|
Quote:
Disk /dev/mdN doesn't contain a valid partition table
|
Unless you specified a partitionable array using “mdadm -C --auto ...”, then a non-partitionable array was created by default.
The fdisk message just confirms the presence of a non-partitionable array.
|
|
|
06-23-2006, 08:47 PM
|
#3
|
Member
Registered: Apr 2004
Distribution: RedHat, Fedora, Suse, Debian, Gentoo, Mandrake
Posts: 132
Original Poster
Rep:
|
Thanks a lot
|
|
|
All times are GMT -5. The time now is 11:11 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|