I posted this on another forum but haven't received any responses. This is regarding f14 --just updated from f10 (reluctantly). The disk resides on a Adaptec 1430sa controller but I'm not going to pursue this as a driver issue (unless I can be convinced).
There's a URL below from someone who was having nearly identical trouble. I tried his fix (dmsetup remove <foo>) but it didn't work for me.
----
There must be a new way of doing things that nobody has told me about.
If you haven't seen this before can you tell me quickly how to at least get the sdb1 device to persist over reboots?
Scenario:
1)
[ 2.579435] sd 4:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 2.579520] sd 4:0:0:0: [sdb] Write Protect is off
[ 2.579524] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 2.579551] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.580606] sdb:
[ 3.069317] sdb1
[ 3.069871] sd 4:0:0:0: [sdb] Attached SCSI disk
2) mount /dev/sdb1 /foo
mount: special device /dev/sdb1 does not exist
3) cd /dev; MAKDEV sdb1; ls -ld /dev/sdb1
brw-r-----. 1 root disk 8, 17 May 23 16:04 sdb1
4) mount /dev/sdb1 /foo
mount: /dev/sdb1 already mounted or /foo busy
5) umount /foo
umount: /foo: not mounted
---------- Post added at 06:12 PM ---------- Previous post was at 06:11 PM ----------
Oh yes:
fdisk -l /dev/sdb
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa6cfa924
Device Boot Start End Blocks Id System
/dev/sdb1 63 1953520064 976760001 83 Linux
---------- Post added at 08:15 PM ---------- Previous post was at 06:12 PM ----------
In looking through a few zillion posts on this the more relevant ones suggest conflicts with device mapper...
However I know little about how to correct this so need help here. Here's what I see:
# dmsetup ls
ddf1_ezekieldas (253, 0)
# ls /dev/mapper/
control ddf1_ezekieldas
I *KNOW* this is the disk. Can anyone tell me what to do to allow it to mount or release control of it?
Commenting out the "dm-" entries in /lib/modules/.../modules.dep did not offer any positive results.
These posts were close, but didn't offer a complete solution...
https://alexlurthu.wordpress.com/201...or-mysql-busy/
http://magazine.redhat.com/page/5/?s=blur