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