Bug 37281
Summary: | Dropping Disk Geometry of RAID Drives on Reboot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Calvin Webster <cwebster> |
Component: | util-linux | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-07-16 13:32:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Calvin Webster
2001-04-23 23:49:55 UTC
[04-24-2001] 1. Found this possibly related FAQ on the European redhat site: http://www.europe.redhat.com/documentation/HOWTO/Software-RAID-0.4x-HOWTO-5.php3 Q: I can't make md work with partitions on our latest SPARCstation 5. I suspect that this has something to do with disk-labels. A: Sun disk-labels sit in the first 1K of a partition. For RAID-1, the Sun disk- label is not an issue since ext2fs will skip the label on every mirror. For other raid levels (0, linear and 4/5), this appears to be a problem; it has not yet (Dec 97) been addressed. 2. Upgraded kernel to 2.2.19-6.2.1 then repartitioned with additional 3rd (whole) partition. Re-created raid, re-made filesystem and rebooted. Drops disk geometry on sdb, sdc, and sdd. Rebuilt raid and rebooted three times, each losing sdb, sdc, and sdd. Here are relevant entries in /var/log/messages: ####################### # Begin Boot Messages # ####################### Apr 24 18:25:06 winggear kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sda: sda1 Apr 24 18:25:06 winggear kernel: sym53c875-0-<1,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16) Apr 24 18:25:06 winggear kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sdb: unknown partition table Apr 24 18:25:06 winggear kernel: sym53c875-0-<2,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16) Apr 24 18:25:06 winggear kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sdc: unknown partition table Apr 24 18:25:06 winggear kernel: sym53c875-0-<3,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16) Apr 24 18:25:06 winggear kernel: SCSI device sdd: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sdd: unknown partition table Apr 24 18:25:06 winggear kernel: sym53c875-0-<4,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16) Apr 24 18:25:06 winggear kernel: SCSI device sde: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sde: sde1 Apr 24 18:25:06 winggear kernel: sym53c875-0-<5,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16) Apr 24 18:25:06 winggear kernel: SCSI device sdf: hdwr sector= 512 bytes. Sectors= 35378533 [17274 MB] [17.3 GB] Apr 24 18:25:06 winggear kernel: sdf: sdf1 Apr 24 18:25:06 winggear kernel: (read) sda1's sb offset: 17684032 [events: 00000002] Apr 24 18:25:06 winggear kernel: blkdev_open() failed: -6 Apr 24 18:25:06 winggear kernel: md: could not lock sdb1, zero-size? Marking faulty. Apr 24 18:25:06 winggear kernel: could not import sdb1, trying to run array nevertheless. Apr 24 18:25:06 winggear kernel: blkdev_open() failed: -6 Apr 24 18:25:06 winggear kernel: md: could not lock sdc1, zero-size? Marking faulty. Apr 24 18:25:06 winggear kernel: could not import sdc1, trying to run array nevertheless. Apr 24 18:25:06 winggear kernel: blkdev_open() failed: -6 Apr 24 18:25:06 winggear kernel: md: could not lock sdd1, zero-size? Marking faulty. Apr 24 18:25:06 winggear kernel: could not import sdd1, trying to run array nevertheless. Apr 24 18:25:06 winggear kernel: (read) sde1's sb offset: 17684032 [events: 00000002] Apr 24 18:25:06 winggear kernel: (read) sdf1's sb offset: 17684032 [events: 00000002] Apr 24 18:25:06 winggear kernel: autorun ... Apr 24 18:25:06 winggear kernel: considering sdf1 ... Apr 24 18:25:06 winggear kernel: adding sdf1 ... Apr 24 18:25:06 winggear kernel: adding sde1 ... Apr 24 18:25:06 winggear kernel: adding sda1 ... Apr 24 18:25:06 winggear kernel: created md0 Apr 24 18:25:06 winggear kernel: bind<sda1,1> Apr 24 18:25:06 winggear kernel: bind<sde1,2> Apr 24 18:25:06 winggear kernel: bind<sdf1,3> Apr 24 18:25:06 winggear kernel: running: <sdf1><sde1><sda1> Apr 24 18:25:06 winggear kernel: now! Apr 24 18:25:06 winggear kernel: sdf1's event counter: 00000002 Apr 24 18:25:06 winggear kernel: sde1's event counter: 00000002 Apr 24 18:25:06 winggear kernel: sda1's event counter: 00000002 Apr 24 18:25:06 winggear kernel: md0: former device sdb1 is unavailable, removing from array! Apr 24 18:25:06 winggear kernel: md0: former device sdc1 is unavailable, removing from array! Apr 24 18:25:06 winggear kernel: md0: former device sdd1 is unavailable, removing from array! Apr 24 18:25:06 winggear kernel: raid5 personality registered Apr 24 18:25:06 winggear kernel: md0: max total readahead window set to 2048k Apr 24 18:25:06 winggear kernel: md0: 4 data-disks, max readahead per data- disk: 512k Apr 24 18:25:06 winggear kernel: raid5: spare disk sdf1 Apr 24 18:25:06 winggear kernel: raid5: device sde1 operational as raid disk 4 Apr 24 18:25:06 winggear kernel: raid5: device sda1 operational as raid disk 0 Apr 24 18:25:06 winggear kernel: raid5: not enough operational devices for md0 (3/5 failed) Apr 24 18:25:06 winggear kernel: RAID5 conf printout: Apr 24 18:25:06 winggear kernel: --- rd:5 wd:2 fd:3 Apr 24 18:25:06 winggear kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:sda1 Apr 24 18:25:06 winggear kernel: disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 2, s:0, o:0, n:2 rd:2 us:1 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 3, s:0, o:0, n:3 rd:3 us:1 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 4, s:0, o:1, n:4 rd:4 us:1 dev:sde1 Apr 24 18:25:06 winggear kernel: disk 5, s:1, o:0, n:5 rd:5 us:1 dev:sdf1 Apr 24 18:25:06 winggear kernel: disk 6, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 7, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 8, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 9, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 10, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: disk 11, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00] Apr 24 18:25:06 winggear kernel: raid5: failed to run raid set md0 Apr 24 18:25:06 winggear kernel: pers->run() failed ... Apr 24 18:25:06 winggear kernel: do_md_run() returned -22 Apr 24 18:25:06 winggear kernel: unbind<sdf1,2> Apr 24 18:25:06 winggear kernel: export_rdev(sdf1) Apr 24 18:25:06 winggear kernel: unbind<sde1,1> Apr 24 18:25:06 winggear kernel: export_rdev(sde1) Apr 24 18:25:06 winggear kernel: unbind<sda1,0> Apr 24 18:25:06 winggear kernel: export_rdev(sda1) Apr 24 18:25:06 winggear kernel: md0 stopped. Apr 24 18:25:06 winggear kernel: ... autorun DONE. ##################### # End Boot Messages # ##################### Bug is not in "raidtools", but in "fdisk" built-in defaults. Found this comment in the man page for "fdisk": "Do not start a partition that actually uses its first sector (like a swap partition) at cylinder 0, since that will destroy the disklabel." Apparently, "fdisk" doesn't follow its own advice when creating default partitions. The 1st partition's default starting cylinder is always "0". Overriding the default, I re-configured the 1st partition to use cylinders 1- 7506 instead of 0-7506. Disk label containing geometry information and partition tables no longer gets corrupted on restart. Sorry, AFAICS this behaviour can't be forced by fdisk since it is highly dependant on the type of partition table being used. It's basically a case of just reading the docs properly. :( |