Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 19/20 > Using Fedora
FedoraForum Search

Forgot Password? Join Us!

Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 4th August 2010, 06:06 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
linuxfedorafirefox
One or more block devices are holding /dev/*

I have recently installed Fedora 13 and like what I have seen so far, I last used Fedora 4 a long time ago.

Hardware setup:
2.something AMD dual core
4GB RAM (64 shared vid)
onboard Raid is disabled
1 250GB HDD
2 500GB HDD
3 1TB Raid (Hardware sata)
250GB HDD times 4

When i look in disk utility it shows the Raid drive (1.0 TB) as not partitioned. when I attempt to partition it I get the error "One or more block devices are holding /dev/dm-0". I have search here and the all mighty Goggle for similar issues with no luck except one. http://forums.fedoraforum.org/showthread.php?p=1387441
I "chmod 777 /dev/dm-0" to see if this was the issue but it was no help. I may be overlooking or outright forgetting something. All and any help appreciated.
Reply With Quote
  #2  
Old 4th August 2010, 08:43 PM
assen Offline
Registered User
 
Join Date: Oct 2008
Posts: 492
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Hi,


It may help to know what is the hardware RAID controller. "lspci" should help shed some light.

Also, you need to have some kind of array configured on the hardware RAID (RAID-0, RAID-1 etc.) - I assume this has been done.

WWell,
Reply With Quote
  #3  
Old 4th August 2010, 09:42 PM
stevea Online
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,712
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

I think I can explain. There were some fairly recent changes (like w/in the past yr) so that if any partition on a device was opened or mounted then you cannot (easily) modify the partition table for the entire device.

In the old days (like last year) you could rewrite the partition table and then the driver was notified to re-read the partition table and everything was happy - unless you made a mistake. If you created a bad or misaligned or modified partition table for a mounted file-system there was an excellent chance the kernel would go down in flames along with the file-system. So the old Unix philosophy of "there is plenty of rope to hang everyone" has changes to "training wheels for all".

So now if you use a tool like fdisk or gparted and you are modifying or repartitioning unused space, when you go to write the partition info the attempt will upchuck an error. Even if you manage to re-write the partition table, the mechanism to re-read it is lost, so you need to umount everything, close all the accessing programs, then try.

'palimpsest' seems to be the tool best adapted to the recent changes.


Also you can and should use 'lsof' to find who is holding dm-0. That is the problem.

BTW the *&^*-sucking Gnome desktop automatically opens devices sometimes (it think's it's an OS) - so you may have to kick the gnomes.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe

Last edited by stevea; 4th August 2010 at 09:47 PM.
Reply With Quote
  #4  
Old 5th August 2010, 12:29 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

I thank you for your help.

I am running into several issues that do not make sense.

1. When I run (@root) "fdisk -l" I get

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000de037

Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 30402 243685376 8e Linux LVM

Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00009386

Device Boot Start End Blocks Id System
/dev/sdc1 1 121605 976789760 8e Linux LVM

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6c9b6c9b

Device Boot Start End Blocks Id System
/dev/sdb1 1 60802 488385536 8e Linux LVM

Disk /dev/sdd: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sde: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/sdf: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-0: 1000.2 GB, 1000232976384 bytes
255 heads, 63 sectors/track, 121604 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 262144 bytes
Disk identifier: 0x00009386

Device Boot Start End Blocks Id System
/dev/dm-0p1 1 121605 976789760 8e Linux LVM

Disk /dev/dm-1: 1000.2 GB, 1000232714240 bytes
255 heads, 63 sectors/track, 121604 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 262144 bytes
Disk identifier: 0x00000000


Disk /dev/dm-2: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 262144 bytes
Disk identifier: 0x00000000


Disk /dev/dm-3: 6241 MB, 6241124352 bytes
255 heads, 63 sectors/track, 758 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


Disk /dev/dm-4: 1689.9 GB, 1689901858816 bytes
255 heads, 63 sectors/track, 205452 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 262144 bytes
Disk identifier: 0x00000000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^
This is contrary to the disk utility that says the Raid is not partitioned and unformatted.

2. I also tried "lsof" but was unable to find or even define if the drive/drives were in the list. I will attach the list as it is to long.

I also noticed that the device is not in the mnt folder. Has the mounting of drives been changed as well? Also can't I force a dismount to break any blocks on the device/drive?
Attached Files
File Type: txt lsof.txt (904.5 KB, 445 views)
Reply With Quote
  #5  
Old 5th August 2010, 12:31 AM
oxala Offline
Registered User
 
Join Date: Jul 2010
Posts: 270
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

An ah-ha moment .... palimpsest .... it's "Disk Utility" on the the "System Tools" menu ... I feel soooooooooo smart!

I have had ZERO success getting palimpsest to create a raid device. If the raid is already created ... it will create a partition.


Wlyon,

If it were me ... I'd just resort to good old fashioned brute force:

<CTRL><ALT><F2> #gets you to a simple terminal window
Log in as root
init 2 #kick the gnomes; kill almost everything
mkfs.ext4 <OPTIONS> /dev/md<NUMBER> #Create the filesystem exactly how you want it where you want it
init 5 #apologize to the gnomes .... bring system back to full multi-user graphical goodness


I don't understand wtf "Disk Utility"/palimpsest is designed to convey in the upper right hand corner, where we are reading "Partitioning: Not Partitioned" ... it says this for all my md devices ... and I have a little bit of everything ...

On my system ... this information is meaningless ... .... maybe it's displaying the wrong phrase ... ????
Reply With Quote
  #6  
Old 5th August 2010, 05:01 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
windows_xp_2003firefox
Re: One or more block devices are holding /dev/*

If this is a Gnome issue would KDE or other resolve the issue. TBO the GUI is only to help me catch back up to the whole Linux goodness and primarily want to run/experiment with server playtoys.
Reply With Quote
  #7  
Old 5th August 2010, 05:27 AM
oxala Offline
Registered User
 
Join Date: Jul 2010
Posts: 270
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Hello again,

I just re-read your original post more carefully. Are you SURE that it is not partitioned? You may just be responding to a strange label in "Disk Utility"?

Anyway, please post the output of the command "df -h". I would like to see how your actual file-system correspond to the disks. You may not actually have a problem ... which is an easy solution

Cheers,


cwight
Reply With Quote
  #8  
Old 6th August 2010, 03:11 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

I think that it is formatted from what fdisk says. However, you seem to be onto something and I have been thinking that when I installed the OS I did select the raid drive to be added automaticly. Wow I feel like such a noob it's been to long... I guess I will have to never leave again.

[root@server01 mnt]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_server01-lv_root
50G 4.0G 43G 9% /
tmpfs 2.0G 508K 2.0G 1% /dev/shm
/dev/sda1 485M 28M 432M 7% /boot
/dev/mapper/vg_server01-lv_home
1.6T 249M 1.5T 1% /home
[root@server01 mnt]#

Correct me if I'm wrong but does that mean that it bundled everything into one. it would explain why I can't find the mount point... or i forgot something else.
Reply With Quote
  #9  
Old 6th August 2010, 03:45 AM
oxala Offline
Registered User
 
Join Date: Jul 2010
Posts: 270
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Hello again wlyon,

Hee hee hee, you have 1.6 Terabytes in your home file system ... which means you don't need to worry about running low for a VERY LONG TIME ....

Unless you have another 3 or 4 disks you forgot to mention, it looks like everything is mapped to the home file-system on top of lvm on top of raid.

If you feel the need to double check, or are just curious, each raid device created during the install will be listed in /etc/mdadm.conf, which is created by the anaconda installer. If you use the command "mdadm --detail /dev/md<NUMBER>" for each device listed in mdadm.conf, you will see exactly how the devices from your fdisk output map to the raid arrays.

Have fun!
Reply With Quote
  #10  
Old 7th August 2010, 12:38 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
windows_xp_2003firefox
Re: One or more block devices are holding /dev/*

Okay, this is a problem (maybe). See back in the day you would partition the drive to install Linux and then format the partition and after install you would partition and format other drives. Then you would create mount points in the /home/mnt/ directory and then "mount /home/mnt/drivemountpoint". The desired way i want to set this up is so that Linux uses 1 drive for the OS and swap and the raid is a separate mount point so I can set the FTP server, or whatever server, to that mount point. I have no Issues about reinstalling if need be. Also one of my raid drive seems to have developed a problem and was going to rearrange my drives to resolve this issue anyway. Suggestions? I do thank you for your help so far and i hope that I can return the favor some day.
Reply With Quote
  #11  
Old 7th August 2010, 01:58 AM
oxala Offline
Registered User
 
Join Date: Jul 2010
Posts: 270
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Hello again wlyon,

"Also one of my raid drive seems to have developed a problem and was going to rearrange my drives to resolve this issue anyway."

Could you please
provide more detail? Why do you think you have a problem? A problem with an individual disk, which may be part of an array, or the actual array (e.g. /dev/md0 )?

Also, could you please post the output of the commands "lvdisplay" and "mdadm --detail --scan|awk '{print $2}'|xargs mdadm --detail"? (NOTE: these must be run a user "root")

I don't think I yet understand how you want the disks laid-out ... but let's make sure you have a healthy system first.

BTW, your post reminded me exactly why I always choose "custom" on every installer ....

.... and don't forget to have fun ....
Reply With Quote
  #12  
Old 7th August 2010, 10:56 AM
stevea Online
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,712
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Quote:
Originally Posted by oxala View Post
An ah-ha moment .... palimpsest .... it's "Disk Utility" on the the "System Tools" menu ... I feel soooooooooo smart!

I have had ZERO success getting palimpsest to create a raid device. If the raid is already created ... it will create a partition.
Wow - did you even try - it's dead easy.
Click File->Create->Raid_Array
In the new window select,
RAID-types (supports, 0, 1, 5, 6)
Array Name
StripeSize (for -0, -5, -6)
Array size
Then select 2 or more disks to iinclude and select "Create".


For a single partition in the main window create a file system and mount it if you wish.
-
For multiple partitions on the RAID select the create/format and select "GUID partition table". Then create multiple partitions and format and mount as desired.

I don't know how that could make it any easier without adding more graphics and braille.

==

Quote:
Wlyon,

If it were me ... I'd just resort to good old fashioned brute force:

<CTRL><ALT><F2> #gets you to a simple terminal window
Log in as root

init 2 #kick the gnomes; kill almost everything
I can't agree. It silly to run about like a headless chicken shutting things off and changing the init level based on your unfounded suspicion. From the 'lsof' it's CLEAR that gnome has nothing to do with the OPs problem. From his 'df' the problem is CLEARLY that the devices are already mounted. You should diagnose before you treat.

If the OP followed your advise he'd be reformatting a mount RAID - and that's pretty awful.



Quote:
mkfs.ext4 <OPTIONS> /dev/md<NUMBER> #Create the filesystem exactly how you want it where you want it
init 5 #apologize to the gnomes .... bring system back to full multi-user graphical goodness
You don't even trust 'mount -t' ? Weird advise.


Quote:
I don't understand wtf "Disk Utility"/palimpsest is designed to convey in the upper right hand corner, where we are reading "Partitioning: Not Partitioned" ... it says this for all my md devices ... and I have a little bit of everything ...

On my system ... this information is meaningless ... .... maybe it's displaying the wrong phrase ... ????
It clearly means there is no partition table on the device. It seems extremely clear, and I haven't seen it error in any way.

"Brute force" doesn't do your methods justice. You're like the guy working as a watch maker but your only tool is a hammer.





Quote:
Originally Posted by oxala View Post
Anyway, please post the output of the command "df -h". I would like to see how your actual file-system correspond to the disks. You may not actually have a problem ... which is an easy solution
It's a closed case - but WTF are you asking for 'df' ?

'df' only shows MOUNTED fiole systems.
'fdisk' shows the partition tables which is a good start., but that FS types in the partiton tables are not to be taken seriously.

You want to examine the actual file systems on all the partitions perhaps like ...
for i in $(tail -n +3 /proc/partitions | cut -c 26-) ; do file -s /dev/$i; done
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe
Reply With Quote
  #13  
Old 7th August 2010, 04:44 PM
oxala Offline
Registered User
 
Join Date: Jul 2010
Posts: 270
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Quote:
It silly to run about like a headless chicken shutting things off and changing the init level based on your unfounded suspicion
At this point I had not seen the df output and "assumed" that the filesystems had not been formatted, as per the information that had been posted. After re-reading the posts, I thought differently as is clear from the thread.

Nonetheless, your critique is valid and appreciated! The brute force approach is seldom efficacious and I provided bad advice at that point in the thread. One thing I am learning here: it's much easier to get my system running the way I want it than to help someone else get their system running as they want it. It's often challenging to simply understand the question!

Quote:
for i in $(tail -n +3 /proc/partitions | cut -c 26-) ; do file -s /dev/$i; done
NICE ... lot's of info from something that can be pasted into a terminal!

A picture is worth a thousand words:
file:///home/wight/Desktop/look.jpg
But it's wrong dimension and I don't feel like messing with it.

The information being displayed in the upper right had corner is either misleading or WRONG!

"Disk Utility" also has trouble creating arrays ... it's a nice tool, but clearly in need of some tlc.

Last edited by oxala; 7th August 2010 at 06:29 PM. Reason: get the picture in
Reply With Quote
  #14  
Old 16th August 2010, 02:26 AM
wlyon Offline
Registered User
 
Join Date: Aug 2010
Posts: 12
windows_xp_2003firefox
Re: One or more block devices are holding /dev/*

Sorry for the delay, I've been really busy. One of the drives in the Raid array does have a problem and is also the wrong drive. This can be identified by the model number of the HDD as the HDD that has a problem is an older drive and has a diff model number. There are also a few (2) hot-swap bays for PATA HDD's that I plan on using so setting mount points is going to be a necessity. The configuration of internal HDDs will be as follows:

1: primary 500GB (holding OS and swap partitions)
2: Raid 1TB (set to mount point Raid01 [or other such name] this is where I would set the FTP and other servers as storage area)
3: set mount points for the hot-swap bays

I need to stop the OS from auto mounting all drives on boot (I can specify this later easy enough) I want the OS to only auto mount the primary HDD. I am planing on performing this change tonight and see if I have any similar problems with the built in drive utility. If there are any suggestions please by all means fire away.

The one thing I can not figure out is why you would not trust fdisk to tell what the partition format is as I have never seen it incorrectly report any partition that was not corrupt.
Reply With Quote
  #15  
Old 16th August 2010, 03:31 AM
stevea Online
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,712
linuxfedorafirefox
Re: One or more block devices are holding /dev/*

Quote:
Originally Posted by oxala View Post
Nonetheless, your critique is valid and appreciated! The brute force approach is seldom efficacious
It's often highly efficacious at taking a system from being 1 minor tweak for OK to totally irreparably broken.
Just like in medicine - first diagnose - then treat.

Quote:
But it's wrong dimension and I don't feel like messing with it.
??? I just don't get your logic - the info you need is in /proc/partitions, it is NOT available from df or fdisk, so you reject the only means provide to get the info. Maybe there is some other tool to do the job, but you refuse to use anything but your hammer.

Quote:
The information being displayed in the upper right had corner is either misleading or WRONG!

"Disk Utility" also has trouble creating arrays ... it's a nice tool, but clearly in need of some tlc.
No - you are wrong. Palmisest is providing the correct info abt the disk not having a conventional MSDOS style partitioin table.

I don't see any trouble w/ palmisest creating arrays - so if you have a clear example either file a bugzilla or plz create a new thread. I would admit that palisest isn't the prettiest tool in the box, it's new and green and has a few ergonomic rough edges ... BUT ... it is the future of fedora disk management. If you wanna shape that future it's your obligation to post a bugzilla and to send your constructive criticism to the maintainers. This is a self-help forum.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe
Reply With Quote
Reply

Tags
block, devices, holding, or dev or

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Test Day today - block devices (important) - come help out AdamW Alpha, Beta & Snapshots Discussions (Fedora 11 Only) 0 5th March 2009 04:55 PM
sata /dev/sd[ab]1 block devices shown as busy or non existant? geogriffin Hardware & Laptops 2 20th July 2008 09:17 AM


Current GMT-time: 12:43 (Tuesday, 29-07-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat