Is RAID1 alive and well?
Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop I recently tested imaging and restoring my complete system with Mondo (before I screw it up again :-) All seems well, but earlier today I thought I saw something like RAID1 not detected in the messages scrolling by at boot up. May be nothing, as I have scanned all logs in the appropriate time frame without success, but I would like to put my mind at rest. I've been googling and searching man pages for hours for a way to determine if RAID1 is working properly after the restore. I even installed a package named dmraid which tells me there is no detected RAID, but I'm not sure it's looking for the type of software RAID used by Debian. The only thing I found (other than dmraid) that gives me any kind of indication is the cli sfdisk (I only used the -l option). The output from such is below. Is it telling me that hdb is an active RAID1 disk? Is there any other way of determining the status of RAID1 in my Debian installation? Sorry, but this is bugging me %-/ Thank you, Lee C output from sfdisk == debian1:/home/leec# sfdisk -l Disk /dev/hda: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hda1 * 0+851 852- 6843658+ 83 Linux /dev/hda285297288877 71304502+ 5 Extended /dev/hda3 0 - 0 00 Empty /dev/hda4 0 - 0 00 Empty /dev/hda5852+ 1182 331- 2658726 82 Linux swap / Solaris /dev/hda6 1183+ 97288546- 68645713+ 83 Linux Disk /dev/hdb: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hdb1 0+ 97259726- 78124063+ 5 Extended /dev/hdb2 0 - 0 00 Empty /dev/hdb3 0 - 0 00 Empty /dev/hdb4 0 - 0 00 Empty /dev/hdb5 0+ 97259726- 78124032 fd Linux raid autodetect debian1:/home/leec# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is RAID1 alive and well?
On Fri, 2006-01-06 at 03:45 -0500, Chinook wrote: Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop I recently tested imaging and restoring my complete system with Mondo (before I screw it up again :-) All seems well, but earlier today I thought I saw something like RAID1 not detected in the messages scrolling by at boot up. May be nothing, as I have scanned all logs in the appropriate time frame without success, but I would like to put my mind at rest. I've been googling and searching man pages for hours for a way to determine if RAID1 is working properly after the restore. I even installed a package named dmraid which tells me there is no detected RAID, but I'm not sure it's looking for the type of software RAID used by Debian. The only thing I found (other than dmraid) that gives me any kind of indication is the cli sfdisk (I only used the -l option). The output from such is below. Is it telling me that hdb is an active RAID1 disk? Is there any other way of determining the status of RAID1 in my Debian installation? Sorry, but this is bugging me %-/ Thank you, Lee C output from sfdisk == debian1:/home/leec# sfdisk -l Disk /dev/hda: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hda1 * 0+851 852- 6843658+ 83 Linux /dev/hda285297288877 71304502+ 5 Extended /dev/hda3 0 - 0 00 Empty /dev/hda4 0 - 0 00 Empty /dev/hda5852+ 1182 331- 2658726 82 Linux swap / Solaris /dev/hda6 1183+ 97288546- 68645713+ 83 Linux Disk /dev/hdb: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hdb1 0+ 97259726- 78124063+ 5 Extended /dev/hdb2 0 - 0 00 Empty /dev/hdb3 0 - 0 00 Empty /dev/hdb4 0 - 0 00 Empty /dev/hdb5 0+ 97259726- 78124032 fd Linux raid autodetect debian1:/home/leec# cat /prod/mdstat with regards Ronny Aasen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is RAID1 alive and well?
Chinook a écrit : Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop I recently tested imaging and restoring my complete system with Mondo (before I screw it up again :-) All seems well, but earlier today I thought I saw something like RAID1 not detected in the messages scrolling by at boot up. May be nothing, as I have scanned all logs in the appropriate time frame without success, but I would like to put my mind at rest. I've been googling and searching man pages for hours for a way to determine if RAID1 is working properly after the restore. I even installed a package named dmraid which tells me there is no detected RAID, but I'm not sure it's looking for the type of software RAID used by Debian. The only thing I found (other than dmraid) that gives me any kind of indication is the cli sfdisk (I only used the -l option). The output from such is below. Is it telling me that hdb is an active RAID1 disk? Is there any other way of determining the status of RAID1 in my Debian installation? Sorry, but this is bugging me %-/ Hi, You can watch the file /proc/mdstat or use the mdadm tool (in mdadm package, it's the official tool to manage software raid on linux). cu. Thank you, Lee C output from sfdisk == debian1:/home/leec# sfdisk -l Disk /dev/hda: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hda1 * 0+851 852- 6843658+ 83 Linux /dev/hda285297288877 71304502+ 5 Extended /dev/hda3 0 - 0 00 Empty /dev/hda4 0 - 0 00 Empty /dev/hda5852+ 1182 331- 2658726 82 Linux swap / Solaris /dev/hda6 1183+ 97288546- 68645713+ 83 Linux Disk /dev/hdb: 155061 cylinders, 16 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 155061/16/63). For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/hdb1 0+ 97259726- 78124063+ 5 Extended /dev/hdb2 0 - 0 00 Empty /dev/hdb3 0 - 0 00 Empty /dev/hdb4 0 - 0 00 Empty /dev/hdb5 0+ 97259726- 78124032 fd Linux raid autodetect debian1:/home/leec# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is RAID1 alive and well?
On Fri, 6 Jan 2006, Chinook wrote: Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop I recently tested imaging and restoring my complete system with Mondo (before I screw it up again :-) good that you can backup/restore ... at least that process/proceedure works :-) == debian1:/home/leec# sfdisk -l Device Boot Start End #cyls#blocks Id System /dev/hda1 * 0+851 852- 6843658+ 83 Linux /dev/hda285297288877 71304502+ 5 Extended /dev/hda3 0 - 0 00 Empty /dev/hda4 0 - 0 00 Empty what is the point of /dev/hda3 and /dev/hda4 ... - when you rebuilt the next time .. delete it /dev/hda5852+ 1182 331- 2658726 82 Linux swap / Solaris /dev/hda6 1183+ 97288546- 68645713+ 83 Linux it's not clear if you are booting off /dev/hda1 or off of /dev/hda6 Device Boot Start End #cyls#blocks Id System /dev/hdb1 0+ 97259726- 78124063+ 5 Extended very very bad idea ... /dev/hdb2 0 - 0 00 Empty /dev/hdb3 0 - 0 00 Empty /dev/hdb4 0 - 0 00 Empty delete unused garbage ... hdb2, hdb3, hdb4 /dev/hdb5 0+ 97259726- 78124032 fd Linux raid autodetect nice that its setup as raid autodetect which is correct .. without seeing your /etc/mdadm.conf files, one can't say what you have and dont have .. - as is, you raid setup will not work - raid1 is mirroring - /dev/hdaX and /dev/hdbX should be defined identically - raid1 will use the smaller size/partitions of the 2 disks - raid autodetect MUST be defined for raid1/raid5 - if you like watching jibberish, cat /proc/mdstat but you'd have to understand it to know that its useful - at a minimum, if you should see U and not _ for each of the raid devices in the /dev/mdX - you should never use /dev/hda and /dev/hdb in raid1/raid5 as that does not provide any redundancy and more importantly it will slow you down 2x-4x c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is RAID1 alive and well?
Chinook wrote: Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop snip Thanks for the responses Ronny, Marc and Alvin Since I missed the obvious (actually didn't recognize it for what it was in my scanning) I've been off doing more research and reading. Actually what it boils down to is that I don't really want RAID1. The main reason is that all I wanted in the first place was a quick clone facility and additionally a IDE master-slave RAID1 set is not a very good idea. On my PM G5 I've got 2 internal 250GB HDs as a RAID1 set for my working volume, but they are not in a master-slave relationship. I also clone daily to alternating external 250GB HDs. Anyway I'm reconfiguring without including hdb and will clone to it using g4l. Less often I'll also create a system image to bootable DVD(s) using Mondo. Thanks for showing me what I was missing, Lee C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
