You are not logged in.
Pages: 1
Hi
just had to downgrade to 2.6.31 since the new kernel didnt let me mount 2 partitions on my third hdd ...
mount: /dev/sda4 is not a valid block device
after downgrading everything worked again so i dont think its a problem with the disk itself.
would be great if someone had an idea.
Last edited by Yonk (2009-12-31 15:16:39)
Offline
What information does running
$ sudo sfdisk -l
provide about the problematic partition?
Offline
with 2.6.31
...
Disk /dev/sdc: 77825 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0Device Boot Start End #cyls #blocks Id System
/dev/sdc1 0+ 25496- 25497- 204800000 7 HPFS/NTFS
/dev/sdc2 25496+ 77824 52329- 420328288+ 5 Extended
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
/dev/sdc5 25496+ 77824 52329- 420328257 83 Linux
...
rebooting now to check 2.6.32
strange ... now everything works fine after i installed 2.6.32 again
maybe there was an error in 2.6.32-1 ?
Last edited by Yonk (2009-12-30 12:21:13)
Offline
mount: /dev/sda4 is not a valid block device
Disk /dev/sdc:...
Is one of these a typo? Even so, /dev/sdc4 seems equally invalid judging by the output of sfdisk.
Could you clarify this? Perhaps I've misunderstood the problem.
Last edited by chpln (2009-12-30 12:56:11)
Offline
was a typo
should have read /dev/sdc5 and|or /dev/sdc1
Offline
It looks like maybe you had the same problem I had - the a/b/c device names change depending on random factors, thus throwing your fstab out of whack. Better to use the UUID of the drive, so the lettering no longer matters. Get the UUID for all your partitions via the 'blkid' command, then use "UUID=very-long-uuid" instead of "/dev/sda1" in your fstab. Then the lettering no longer is a problem.
Offline
problem is back today ... 2.6.32 sometimes just ignores the 3rd hdd ... or so it seems
open for suggestions again ...
Offline
Did you try using UUIDs instead of /dev names?
Offline
tried and failed ...
somehow the uuid changed after reboot (happend at least once)
Offline
You must be doing something wrong, because I don't believe the disk UUID ever changes, not even between OSes. The UUID for /dev/sdc1 might change, because the dev mapping is different, but for a particular partition, the UUID is not going to be different.
Offline
/dev/sda2: UUID="982252F62252D8B8" TYPE="ntfs"
/dev/sda3: UUID="95175034-e262-4a15-ae22-b1a5016b1f85" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: UUID="2620E26820E23F05" LABEL="New Volume" TYPE="ntfs"
/dev/sdb5: UUID="81c4402f-e76b-42d3-b532-d423be22eabd" TYPE="ext4"
/dev/sdc5: UUID="81c4402f-e76b-42d3-b532-d423be22eabd" TYPE="ext4"
copy/paste of blkid ... 2 partitions same uuid
Offline
Is /dev/sdc5 by any chance a clone of /dev/sdb5?
Edit: To change the UUID of an unmounted partition try:
$ sudo tune2fs -U random /dev/sd?N
Last edited by azleifel (2009-12-31 19:22:39)
Offline
no ... all seperate partitions
no mirroring
nothing ...
Offline
You tried UUIDs and /dev/names. Have you tried labels?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
didnt try labels ... the funny thing is ... even if i cant mount /dev/sdc5 ... it's still in /dev
so it seems it recognizes something
Offline
well ... worked for the last few days ...
but today after the update to 2.6.32-5 it again refuses to mount 2 of my partitions
mount: /dev/sdc5 is not a valid block device
even though the device exists in /dev
i would write a bug report but i dont know what to put in there ... could someone please help ?
Offline
Pages: 1