Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I'm trying to put together a RAID server using Fedora Core 8. Originally the system had 6 750GB discs in RAID-5 mode. Unfortunately, one of the drives was bad, so I had to install a replacement and - on a whim - I bought an extra drive for the array.
The "bad" disk was /dev/sdd. I installed both new drives; the new /dev/sdd appeared, as did /dev/sdh, which was the "bonus" disk. At this point, I now had my OS on /dev/sda, while my RAID drives were /dev/sdb-sdh.
Unfortunately, I messed up and forgot to put a partition on sdd and sdh when I mdadm -add'ed them into the array (I just used mdadm --add /dev/md0 /dev/sdd /dev/sdh). So I mdadm --failed and mdadm --remove'd both disks, put a Linux Raid Autodetect partition on them (with the same characteristics as the other discs), and then mdadm -add'ed them back to the array - this time using the partiton names: mdadm -add /dev/md0 /dev/sdd1 /dev/sdh1.
That worked fine until I rebooted the machine. My box now won't mount the partitions /dev/sdd1 and /dev/sdh1 under /dev, so I can't reassemble my array. Oddly, fdisk and dmesg both "see" the partitions.
Dmesg shows:
sd 4:0:0:0: [sdd] 1465149168 512-byte hardware sectors (750156 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 4:0:0:0: [sdd] 1465149168 512-byte hardware sectors (750156 MB)
sd 4:0:0:0: [sdd] Write Protect is off
sd 4:0:0:0: [sdd] Mode Sense: 00 3a 00 00
sd 4:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdd: sdd1
sd 4:0:0:0: [sdd] Attached SCSI disk
Likewise, fdisk -l shows:
Disk /dev/sdd: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0300390a
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 91201 732572001 fd Linux raid autodetect
/dev/sdh1 also appears in dmesg and fdisk, and the entries for both these disks / partitions appear the same as the other RAID discs.
What's strange, then, is that there are no entries for the partitions on these two discs under /dev:
I'm still a Linux newbie, and I'm WAY over my head on this one. If anyone could tell me how I get the partitions /dev/sdd1 and /dev/sdh1 to show up in /dev, I'd appreciate it.
Sorry about the length, and thanks for the help!
Tim
in your /etc/fstab you will need to make the entries /dev/sdb1 /mnt/sdb1 ext.3 defaults 1 1
then go and make a folder that is in /mnt/sdb1 any time you put another hard drive in it will take that place. so if you have hot swapping the systm will name the sdb 123 or sdh 123 it will not matter a good thing to do if you do alot of hot swapping is to keep the same ammout of partions on all the drives that way you can switch them out then never have this problem. you only have to remember where you put it . good luck.
now I know this scsi sata drive thing is supposed to do this through the system block but why leave it to the program to mount your hard drives. ext3 or any other file system. good luck.n also in yum you can do this.
I've got the exact same problem. have you found any solution yet? I looked through my udev-rules, but didn't find anything special.
Unfortunately, I never really received any help on this one. Instead, I just re-installed Fedora 8. Curiously, the installer was able to figure everything out, and the new install recognized all the disks and made the RAID array fully functional again.
I've the same issue with disappearing /dev/sdb1,2 with combination of Raid1 md0. It started with accidentaly adding /dev/sdb to /dev/md0 instead of /dev/sdb1 (mdadm --manage /dev/md0 --add /dev/sdb instead of --add /dev/sdb1).
In dmesg (kern log)
md: md0 stopped.
md: bind<sdb>
md: could not open unknown-block(8,17).
md: md_import_device returned -6
md: bind<sda1>
md: kicking non-fresh sdb from array!
md: unbind<sdb>
md: export_rdev(sdb)
helped only erasing raid superblock on /dev/sdb (mdadm --misc --zero-superblock /dev/sdb) reboot and recreate partitions and assign /dev/sdb1 again to the raid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.