[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Hard Drives not accessible after Update to F11

On 20.06.2009 19:35, stan wrote:
On Sat, 20 Jun 2009 15:35:45 +0200
Andreas Burget<andiburget gmx de>  wrote:

On Fri, 19 Jun 2009 19:15:51 +0200
Andreas Burget<andiburget gmx de>   wrote:

  Hi there,
  I updated my System via Preupgrade from F10 to F11. The update
went smoothly but after the reboot the System stopped while
booting saying it can't find some drives by their UUIDs. I booted
the LiveCD and disabled them in fstab. after that the system
booted without problems, but I'm not able to mount my other

  here's my fstab:http://fpaste.org/paste/15779
  and here's the fdisk -l output:http://fpaste.org/paste/15780

  I also tried booting the F10 LiveCD and was able to mount them
there. here's the fdisk -l output from

  I hope you can help me fix this

If you run the command   blkid  it will give you the information you
need to put in your fstab in order to access the drives.

Thanks for the hint but that didn't solve my Problem.
blkid only outputs the devices that are already in fstab so there's
nothing new for me to add. http://fpaste.org/paste/15865

I don't think this is true.  I have umounted partitions, deleted them
with (c)fdisk, recreated different partitions, put filesystem on them,
and run blkid and it has given me the new UUID number.  I then edit
fstab, adding the new partitions and deleting the old, and I am able
to mount them.

I think it more likely that there has to be an entry in /dev as a block
device (looks like those are major chord 8 or 253 from your listing).

But it seems Bill was prescient in asking why they disappeared.

my drives are listed in /dev as sdb, sdc, sdd but the partitions are
missing. they should be sdb1 sdc1 and sdd2 as seen in fdisk -l output
from the F10 LiveCD. here's my /dev http://fpaste.org/paste/15866

The evidence seems to suggest that either udev or hal failed to notice
and log these partitions in /dev (I am not familiar with this process).
Once they are there, they should have the same UUID, and so should be
mountable from fstab again.

You say you can boot into the system without mounting those
drives. Can you run parted, fdisk, or cfdisk against one of the drives
when the new system is up.

parted /dev/sdb  or
cfdisk /dev/sdb  or
fdisk /dev/sdb

For now, just print the partition table and see if it is present as you
would expect it to be.  If it is, as seems likely, then the problem is
definitely in the hardware sensing.  At that point, quit the
partition tool.  Then you should first look in /var/log/messages to see
if there are any relevant error messages from boot up about why the
partitions that exist aren't being recognized.  Then you should go look
for bugzilla records of this problem to see if there is a workaround. If
there are none, open a problem record so you can get expert help.
cfdisk and fdisk do find my partitions and I'm not sure how to use parted. (print doesn't show them) When I checked /var/log/messages I found that they are recognized on boot up and no errors are shown so far. (http://fpaste.org/paste/15934)
I didn't find anyting in that direction so I filed a new bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=507142
There are experts here, perhaps one will be able to recognize your
problem and give you better advice.

WARNING!!!  The advice below could lose your data!

If you are feeling adventurous and impatient, you could write the
partition table on the drive without changing it, if it is correct.
Perhaps that will trigger a process to put device nodes in /dev for the
partitions or do so on reboot.  But there is a risk that it could
lose the data on the drive by messing with the partition table.  I
wouldn't do this until I had pursued other alternatives first.

I don't want to destroy my data :)
thank you for your help so far

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]