kernel unable re-read partition table on disks when i start gparted

penduleum · 01-22-2010, 06:27 AM

I have the next problem:

When i start gparted, to see if i can add extra harddisk where all my data is, i get the next error:

Code:

[root# gparted
======================
libparted : 1.9.0
======================
The kernel was unable to re-read the partition table on /dev/sda (Device or resource busy).  This means Linux won't know anything about the modifications you made until you reboot.  You should reboot your computer before doing anything with /dev/sda.

I can start fedora 12 x64 amd whitout any problem.
My partition layout on a single disk (80 gb sata maxtor) for the system is:

Code:

/
/home
swap

When i try to mount one of the extra disks (samsung spinpoint 1 tb, i have 4) i get to next error:

Code:

root# mount /dev/sdb1 /media/sdb1
mount: you must specify the filesystem type

if i add the option with the filesystem i get:

Code:

root# mount -t ext3 /dev/sdb1 /media/sdb1
mount: special device /dev/sdb1 does not exist

Well, in my /car/log/boot.log, i found the following error:

Code:

ERROR: sil: wrong # of devices in RAID set "sil_aibieiddaadi" [1/0] on /dev/sde
ERROR: removing inconsistent RAID set "sil_aibieiddaadi"
ERROR: sil: wrong # of devices in RAID set "sil_aibieiddaaca" [1/0] on /dev/sdd
ERROR: removing inconsistent RAID set "sil_aibieiddaaca"
ERROR: sil: wrong # of devices in RAID set "sil_ajabdgcbejfh" [1/0] on /dev/sdc
ERROR: removing inconsistent RAID set "sil_ajabdgcbejfh"
ERROR: sil: wrong # of devices in RAID set "sil_ajabdgcbejej" [1/0] on /dev/sdb
ERROR: removing inconsistent RAID set "sil_ajabdgcbejej"
ERROR: no RAID set found
failed to stat() /dev/mapper/no
failed to stat() /dev/mapper/raid
failed to stat() /dev/mapper/sets
Setting up Logical Volume Management:                      [  OK  ]
Checking filesystems
Fedora-12-x86_64: clean, 172878/2564096 files, 1077290/10240000 blocks
/dev/sda3: clean, 354/2252800 files, 197974/9000949 blocks

ps: i have my disks just as a jbdo config on the raid chip on my mobo.
I dont whant any raid, just as mucht as disk cappacy possible.

My sda is on the first sata port of the mobo.

when i re-read the disks, whit any program, i can mount them afterwards whit

Code:

 /mount /dev/sdb1 /media/sdb1

all four disks.

In gparted, when i select just a flag option, and deselect, press ok, the disk is forced to be reread by the program. after that i can also mount it.

When i use any of the programs linked in this post, i ame able to mount the disks whitout any problem.
Exept after a reboot, i get the same problem. SO whit each reboot, or poweroff, i need to do a re-read of the disks.

The system is fedora 12 x64 for amd, installed from a live cd, the rest whit yums groupinstall, the latest kernel.

Code:

[root@pc-francc /]# hdparm -z /dev/sdb

/dev/sdb:
 re-reading partition table
[root@pc-francc /]# mount /dev/sdb1 /media/sdb1
[root@pc-francc /]# cd /media/sdb1
[root@pc-francc sdb1]# ls
Automatically Add to iTunes  climbing  lost+found  musica

For the first time, after i do hdparm -z, i got a splash window whit the next error:

failed to mount "1T Volume"
The enclosing drive of the volume is locked.

At the same time, whit that splash window open, i could enter the above commands..

I have this problem for all the 4 samsung 1 tb spinpoint disks.
What is going on here?

I whant them to be albe to mount on boot, but thats impossible whit the above problem (ofcourse, after i added them on /etc/fstab, but for the moment, thats not possible, as i need to do each time a re-read of all the 4 diks).

What can i do to solve this problem?
When i had Ubuntu (8.10 or 9.*) installed, i had no problem mounting and booting this disks.

WHit a live cd of ubuntu, i ame still able to get to the data.

It is impossible to do a format, as i have also backups of from friends computers and laptops..

thx for any info...
please ask for any info if needed...

Edit:

back from doing some other things.
When i do now in the terminal:

Code:

[root@pc-francc /]# hdparm -z /dev/sdb

/dev/sdb:
 re-reading partition table

It mounts automaticly the disk, and i can access it (tryed whit all the disks, the same thing happend).
so, whats going on???

penduleum · 01-25-2010, 05:59 AM

please, any help?

i cant figure this out by my self...

penduleum · 01-28-2010, 05:41 AM

hmmm.....

to bad it seems that no one can pin point me to the right location to search, or even give me a correct answer for this issue, well, it seems that i need to go back to ubunto, as i dint have this problem whit all the releases of ubuntu....

this is realy bad, as i like this os as it is.
only the mentioned problem cant be solved...

penduleum · 01-31-2010, 10:19 AM

thx but no thx for the help...

sry for the flame, but the lack on support from the fedora comm. lets me no choise to go to a other distribution.

I had found a workaround whit cron for this problem, but still, its not a selution...

I ame switching right now to debian stable. So, i dont have this problem any more.

This topic can be put on solved...

BlueBright · 01-31-2010, 05:12 PM

I was faced with a very similar problem today. I added an older disk to my new system, repartitioned it and put an ext4 file system on it. Everything seemed to go fine until I rebooted, when the new /dev/sdd1 was not recognized. I updated the partition table again, filled the MBR with zeros and then updated the partition table, but whatever I tried I got the message:

Code:

dracut: Found dmraid sets:
dracut: no raid sets
dracut: Activating no
dracut: ERROR: sil: wrong # of devices in RAID set "sil_afbgcbdedcca" [1/0] on /dev/sdd

I was about to give up and use the "hdparm -z" trick I found in this post. While updating the rc.local, I included some comments, and at that point I noticed the "dmraid". I rebooted, supplied rd_NO_DM (which I had found earlier on the dracut manpage) as one of the options for kernel, and the dracut error disappeared.

penduleum · 02-01-2010, 11:52 AM

Quote:

Originally Posted by BlueBright

I was faced with a very similar problem today. I added an older disk to my new system, repartitioned it and put an ext4 file system on it. Everything seemed to go fine until I rebooted, when the new /dev/sdd1 was not recognized. I updated the partition table again, filled the MBR with zeros and then updated the partition table, but whatever I tried I got the message:

Code:

dracut: Found dmraid sets:
dracut: no raid sets
dracut: Activating no
dracut: ERROR: sil: wrong # of devices in RAID set "sil_afbgcbdedcca" [1/0] on /dev/sdd

I was about to give up and use the "hdparm -z" trick I found in this post. While updating the rc.local, I included some comments, and at that point I noticed the "dmraid". I rebooted, supplied rd_NO_DM (which I had found earlier on the dracut manpage) as one of the options for kernel, and the dracut error disappeared.

hey there.

thx for the reply.

I ame going to try this one later out.
at the moment i have already done a etch net install of debian 5 from a usb pen. I had no problems at all. After i mounted the disks, i added in /etc/fstab the disks and its mount points. at eacht reboot, the disks are mounted where i whant them to be mounted...

at least i ame glad that this post could help someone..

jandrioli · 04-20-2010, 06:56 AM

I had the same problem since yesterday with a standard dell laptop latitude D610. NO RAID drives!
It has one 60GB harddrive, and i created 4 partitions:
/dev/sda1 ===> ubuntu 9.10
/dev/sda2 ===> winXP
/dev/sda3 ===> extended
/dev/sda4 ===> logical part., ubuntu 10.04
/dev/sda5 ===> logical part., swap

This problem started after i resized some of these partitions.
I tried re-editing the table and moving/resizing partitions, changing flags, etc... nothing helped .
I've no idea why but i finally got rid of the issue after deleting the extended partitions and leaving only the 2 primary ones.