Moby, THANKS!!!!!! That fixed my problem! Yes I don't know why people insist swap should be on raid 0 other that performance reasons but if your disk goes belly up then yeah your totally screwed. Anyways I'm glad I didn't have to go raid 0 in order to fix this problem and now it works my 10.3, very sweet thank you very much :)
Regards, - Jake On 10/9/07, Moby <[EMAIL PROTECTED]> wrote: > > > Jake Conk wrote: > > Well the reason why I didn't make it raid 0 because if one of the > > disks were to go bad then my whole raid would go down right? Can you > > give me the steps on how to make my md1 device a raid 0 without > > reformatting my whole system? I don't think I can stop md1 unless I > > stop all the md devices above it right? (md2/3/4/5) > > > > Thanks, > > - Jake > > > > On 10/9/07, Richard Creighton <[EMAIL PROTECTED]> wrote: > > > >> Jake Conk wrote: > >> > >>> Hello, > >>> > >>> I tried to setup a fresh install of 10.3 with 2 disks and I used YaST > >>> to mirror all my partitions. I had originally my raid swap partitions > >>> on an extended partition but that didn't work and I thought that was > >>> the problem so instead now I put the raid partitions on primary > >>> partitions, which still doesn't work. > >>> > >>> Any suggestions would be appreciated because I'm completely stumped, I > >>> can't figure out for the life of mine why my swap partition won't > >>> work. > >>> > >>> > >>> > >> I think I would try making your swap partition RAID 0 > >> > >> I have MD0 /boot Raid1 > >> MD1 swap Raid 0 > >> MD2 / (root) Raid 1 > >> MD3 /home Raid 5 > >> > >> and it works well with both 10.2 and 10.3. There is no advantage to > >> using raid1 with swap anyhow, you really don't need it to be backed up > >> or duplicated and it just slows the system down even if it did work. > >> > >> > >> > >> > >> > >>> FDISKS___________________________________________________________________ > >>> > >>> > >>> > >>> # fdisk -l /dev/sda > >>> > >>> Disk /dev/sda: 250.0 GB, 250059350016 bytes > >>> 255 heads, 63 sectors/track, 30401 cylinders > >>> Units = cylinders of 16065 * 512 = 8225280 bytes > >>> Disk identifier: 0x000a59ec > >>> > >>> Device Boot Start End Blocks Id System > >>> /dev/sda1 * 1 13 104391 fd Linux raid > >>> autodetect > >>> /dev/sda2 14 275 2104515 fd Linux raid > >>> autodetect > >>> /dev/sda3 276 30401 241987095 f W95 Ext'd (LBA) > >>> /dev/sda5 276 928 5245191 fd Linux raid > >>> autodetect > >>> /dev/sda6 929 948 160618+ fd Linux raid > >>> autodetect > >>> /dev/sda7 949 30401 236581191 fd Linux raid > >>> autodetect > >>> > >>> # fdisk -l /dev/sdb > >>> > >>> Disk /dev/sdb: 250.0 GB, 250059350016 bytes > >>> 255 heads, 63 sectors/track, 30401 cylinders > >>> Units = cylinders of 16065 * 512 = 8225280 bytes > >>> Disk identifier: 0x00026740 > >>> > >>> Device Boot Start End Blocks Id System > >>> /dev/sdb1 * 1 13 104391 fd Linux raid > >>> autodetect > >>> /dev/sdb2 14 275 2104515 fd Linux raid > >>> autodetect > >>> /dev/sdb3 276 30401 241987095 f W95 Ext'd (LBA) > >>> /dev/sdb5 276 928 5245191 fd Linux raid > >>> autodetect > >>> /dev/sdb6 929 948 160618+ fd Linux raid > >>> autodetect > >>> /dev/sdb7 949 30401 236581191 fd Linux raid > >>> autodetect > >>> > >>> > >>> > >>> MOUNT___________________________________________________________________ > >>> > >>> > >>> > >>> # mount > >>> /dev/md2 on / type ext3 (rw,acl,user_xattr) > >>> proc on /proc type proc (rw) > >>> sysfs on /sys type sysfs (rw) > >>> debugfs on /sys/kernel/debug type debugfs (rw) > >>> udev on /dev type tmpfs (rw) > >>> devpts on /dev/pts type devpts (rw,mode=0620,gid=5) > >>> /dev/md0 on /boot type ext3 (rw,acl,user_xattr) > >>> /dev/md4 on /srv type ext3 (rw,acl,user_xattr) > >>> /dev/md5 on /srv/db type ext3 (rw,acl,user_xattr) > >>> /dev/md3 on /tmp type ext3 (rw,acl,user_xattr) > >>> securityfs on /sys/kernel/security type securityfs (rw) > >>> > >>> > >>> > >>> MDADM DETAILS___________________________________________________________ > >>> > >>> > >>> > >>> # mdadm --detail /dev/md1 > >>> /dev/md1: > >>> Version : 01.00.03 > >>> Creation Time : Mon Oct 8 22:11:04 2007 > >>> Raid Level : raid1 > >>> Used Dev Size : 2104500 (2.01 GiB 2.16 GB) > >>> Raid Devices : 2 > >>> Total Devices : 2 > >>> Preferred Minor : 1 > >>> Persistence : Superblock is persistent > >>> > >>> Intent Bitmap : Internal > >>> > >>> Update Time : Mon Oct 8 22:14:55 2007 > >>> State : active, Not Started > >>> Active Devices : 2 > >>> Working Devices : 2 > >>> Failed Devices : 0 > >>> Spare Devices : 0 > >>> > >>> Name : 1 > >>> UUID : 397a7460:be70dee1:fc6c650c:7d900cf7 > >>> Events : 5 > >>> > >>> Number Major Minor RaidDevice State > >>> 0 8 2 0 active sync /dev/sda2 > >>> 1 8 18 1 active sync /dev/sdb2 > >>> > >>> > >>> # cat /sys/block/md1/md/sync_action > >>> recover > >>> > >>> > >>> > >>> FSTAB_________________________________________________________________ > >>> > >>> > >>> > >>> # cat /etc/fstab > >>> /dev/md2 / ext3 acl,user_xattr > >>> 1 1 > >>> /dev/md0 /boot ext3 acl,user_xattr > >>> 1 2 > >>> /dev/md4 /srv ext3 acl,user_xattr > >>> 1 2 > >>> /dev/md5 /srv/db ext3 acl,user_xattr > >>> 1 2 > >>> /dev/md3 /tmp ext3 acl,user_xattr > >>> 1 2 > >>> /dev/md1 swap swap defaults > >>> 0 0 > >>> proc /proc proc defaults > >>> 0 0 > >>> sysfs /sys sysfs noauto > >>> 0 0 > >>> debugfs /sys/kernel/debug debugfs noauto > >>> 0 0 > >>> usbfs /proc/bus/usb usbfs noauto > >>> 0 0 > >>> devpts /dev/pts devpts mode=0620,gid=5 > >>> 0 0 > >>> /dev/fd0 /media/floppy auto noauto,user,sync > >>> 0 0 > >>> > >>> > >>> > >>> FREE__________________________________________________________________ > >>> > >>> > >>> > >>> # free -m > >>> total used free shared buffers cached > >>> Mem: 6089 57 6031 0 3 25 > >>> -/+ buffers/cache: 29 6060 > >>> Swap: 0 0 0 > >>> > >>> > >> -- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >> > I still do not understand why people keep on insisting that swap should > not be on raid - try keeping a system running when the disk holding swap > goes South. > As for the problem, try putting a noresume line in your menu.lst for > grub - I have a feeling you have a resume= pointing to your raid1 set > that you are having issues with. I just got done fighting a similar > problem here, and changing resume= to noresume fixed it. > > > -- > --Moby > > They that can give up essential liberty to obtain a little temporary safety > deserve neither liberty nor safety. -- Benjamin Franklin > > > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
