[opensuse] Hard disk partition not detected on boot
The day before I updated my home data graveyard from 10.1 to 10.3. This system had 10 disks before and 12 now. After update everything seemed reasonably ok except one strange problem: SATA disk sdg - which has been in the system for about 2 years now - is properly detected but the single primary partition on it is not linked to /dev/sdg1. The device file is simply missing. There are no strange messages in /var/log/boot.msg or /var/log/messages. There are 5 other identical disks working well. Smart state is ok. I can start fdisk /dev/sdg and all seems to be ok: ========== DatenGrab:~ # fdisk /dev/sdg The number of cylinders for this disk is set to 38913. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sdg: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000ac812 Device Boot Start End Blocks Id System /dev/sdg1 1 38913 312568641 fd Linux raid autodetect ========== I can use kpartx to actively bind the partition via device-mapper - after that it is accessible and working well. I tried "partprobe /dev/sdg" to enable this partition - this had been not working until I hotplugged the SATA cable. Has anyone an idea where to look for this problem? Which tools to use to track it down? Regards Ralf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 29.10.2007 um 14:08 schrieb Ralf Müller:
The day before I updated my home data graveyard from 10.1 to 10.3. This system had 10 disks before and 12 now. After update everything seemed reasonably ok except one strange problem:
SATA disk sdg - which has been in the system for about 2 years now - is properly detected but the single primary partition on it is not linked to /dev/sdg1. The device file is simply missing.
Seems it has been an old RAID superblock behind the active partition. I shrinked the raid where sdg1 is in by some cylinders to integrate a smaller disk some month before. So at the end of sdg has been an old superblock left. When assembling the RAID where sdg1 is in, mdadm found this old superblock at the end of sdg. When detecting this mdadm seemed to remove the device node for sdg1. There has been no message about it. It just told me there is no /dev/sdg1 - what has been correct as it had been disabled a microsecond before by the very same program ... Anyway after cleaning up behind sdg1 it gets not anymore disabled and the real RAID can be created without problems now. The partprobe problem simply has been a usage problem by me ... Regards Ralf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (1)
-
Ralf Müller