Hard Drive Troubles

[Uber Nooblett]

Hey, just installed Gutsy on my test drive to give it a go.

When I first loaded it up, my drives where all visible, but I couldn't get into any of them. The error I was getting was: 'hal-storage-fixed-mount refused uid 1000'

So, what I did was edit my fstab as I assumed would be correct and rebooted.
Now, with the fstab all seemingly correct, I cannot even see my drives in the storage media section, though they do show where they should in /dev folder.

any ideas?

here is my fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=726def5b-d98f-42de-a6cc-643195901971 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
UUID=db42bcfa-0611-4162-819d-9f50306a58e8 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

#/dev/hdb2
UUID=b2378571-01d3-4d58-8a60-a37122ffcecc /media/hdb2 ext3 defaults 0 2
#/dev/sdb1
UUID=97a27a33-1a1d-4c96-95c8-e5799be7b7d3 /media/sdb1 ext3 defaults 0 2
#/dev/hda1
UUID=6ae756b0-b796-487d-92a9-b6686098ce12 /media/hda1 ext3 defaults 0 2
#/dev/hdb1
UUID=7A30C7E030C7A18D /media/hdb1 ntfs-3g defaults,locale=en_US.utf8 0 0
#/dev/sdc1
UUID=55D123D9E79ABF54 /media/sdc1 ntfs-3g defaults,locale=en_US.utf8 0 0

[dibl]

In a Konsole window, run


blkid

and compare the output to your fstab. If there are any differences, make fstab agree with the blkid output. If you copy & paste, beware the quote marks!

Let us know if it's still a problem. :)

[Uber Nooblett]

well this is what is stated in the blkid:


jj@jj-beast:~$ blkid
/dev/hda1: UUID="6ae756b0-b796-487d-92a9-b6686098ce12" SEC_TYPE="ext2" TYPE="ext 3"
/dev/hda5: UUID="147a517c-a560-4586-a771-8784cdc35cdd" TYPE="swap"
/dev/hdb1: UUID="7A30C7E030C7A18D" LABEL="Windows 2" TYPE="ntfs"
/dev/hdb2: UUID="b2378571-01d3-4d58-8a60-a37122ffcecc" SEC_TYPE="ext2" TYPE="ext 3"
/dev/sda1: UUID="726def5b-d98f-42de-a6cc-643195901971" SEC_TYPE="ext2" TYPE="ext 3"
/dev/sda5: TYPE="swap" UUID="db42bcfa-0611-4162-819d-9f50306a58e8"
/dev/sdb1: UUID="97a27a33-1a1d-4c96-95c8-e5799be7b7d3" SEC_TYPE="ext2" TYPE="ext 3"
/dev/sdc1: UUID="55D123D9E79ABF54" LABEL="MEDIA EXTERNAL" TYPE="ntfs"


anything look dodgy to you?

[dibl]

A couple of things are a little worry to me, but I don't know that they would explain the problem you posted.

1. "hd_" is not a drive type that *buntu is using any more for /dev designation of hard drives. Since Feisty, the new atapi driver makes them all "sd_", So I'm confused about why your Feisty system is outputting "hda" for those first 2 drives, which I presume are IDE/PATA drives, right? For example, here's my blkid output, and the first drive which shows up as /dev/sda is a IDE/PATA Maxtor drive, and the other four are SATA drives, and then there is a USB thumb drive formatted NTFS at the end.


dibl@gutsy:~$ blkid
/dev/sda1: UUID="f222f97f-278f-4db5-8642-513294f30193" TYPE="reiserfs"
/dev/sda2: UUID="a2c1f50a-bd30-4910-825b-7ef65c7788fe" TYPE="swap"
/dev/sda3: UUID="adf641ca-f64e-4311-bc30-86bfcdcb669c" TYPE="reiserfs"
/dev/sdb1: UUID="b1869c3e-b13a-4772-914c-bcc6db718967" TYPE="reiserfs"
/dev/sdb2: UUID="a6c2ba7b-8492-4746-92af-5182dcb4daab" TYPE="reiserfs"
/dev/sdc1: UUID="1ddd0144-0875-4667-9f98-e90a23f58ff3" TYPE="reiserfs"
/dev/sdc2: UUID="710efad8-9f97-4bcd-8f57-8f8cc1facc2f" TYPE="reiserfs"
/dev/sdc3: UUID="f1912a56-2e5c-45ce-b91b-3ebbe69e20f4" TYPE="reiserfs"
/dev/sdd1: UUID="cffddf89-57f3-40ab-a97f-40bb1ea45f16" TYPE="reiserfs"
/dev/sdd2: UUID="94d4d572-3581-491b-90dc-e5f619c65908" TYPE="swap"
/dev/sdd3: UUID="9b7658da-59e1-4b2b-a4b9-fa3ee11b68cf" TYPE="reiserfs"
/dev/sde1: UUID="d182b7c3-298c-49b3-ac66-b378033b815c" TYPE="reiserfs"
/dev/sdf1: UUID="A8FC3435FC33FC5E" LABEL="DIBLZSTUFF" TYPE="ntfs"

2. You are using ext2 filesystem format. I don't know why you would do that -- ext3 is substantially more reliable with "journalling" -- a way of tracking the last transactions before you crash, which is very handy if you do.

3. Something is wrong on your /dev/sda5 -- the sequence of that swap file table needs to be the same as the one for /dev/hda5 above. I hope you know you only need to be actually using one swap partition. You will also see two swaps in my list, but the first one on the /dev/sda drive does not get mounted in *buntu, it only runs for the E-Live system that is on that drive, and then other one on /dev/sdd2 is not mounted.

So, I hope those comments give you some notions -- I would definitely edit that /dev/sda5 line because it is non-functional as-is.

:)

EDIT: WAIT, WAIT -- I just realized, your filesystem table says ext3, but your blkid output says ext2! That can't be right! Are you sure the /etc/fstab table that you posted is the one that is being used by your running OS? They don't match! The drive UUIDs are a match, but the information about the filesystem type does not. ??? Could there, perhaps, be another Linux OS lurking around this system? ;D

[Uber Nooblett]

Yeah, there is Feisty on another hard drive, hence the second swap there. its running on hda1

The blkid seems to show the drives as type ext3 and secondary type ext2 whatever that means.

Take is only one Kubuntu can be installed and use the drives on a system then?

[dibl]

I did a quick google and found a similar situation in the Ubuntu archives from June:

http://ubuntuforums.org/archive/index.php/t-484394.html

I see a reference to a bug, and not a clear resolution to the problem.

I don't know what that SEC_TYPE is referring to -- I have not seen that on my system, which has been through numerous "growth spurts" since I first installed Dapper and had only 2 hard drives in it.

But it would bother me that blkid puts out that listing on /dev/sda5 in the wrong order, even though it looks correct in the fstab table. Something is definitely funny there.

Is it possible that you pulled up the /etc/fstab from your other Linux, and not the one from the running system? In other words,
kdesu kate and then browse up from your home directory to the root, and then over to /etc and then open that fstab and make sure it is the same one that you posted. :P

[dibl]

Take is only one Kubuntu can be installed and use the drives on a system then?



You could have different versions of Kubuntu on different hard drives or even different partitions on the same hard drive if you wanted. I have Ubuntu Feisty on another drive, and E-Live on the old IDE drive. You just have to be careful about the boot menu, to make sure your kernel boot entries are true to the drives and partitions where those kernels are actually located, as per Grub rules and naming conventions. :)

[Uber Nooblett]

This is deff the fstab from this install, though I made it using the same principal as my feisty fstab.

Just out of interest, does your Gutsy fstab look similar at all? perhapse I've just typed it up incorrectly thinking that gutsy would read the same type of file as feisty?

[Uber Nooblett]

well, am back in my safe, working, perhaps not so fast Feisty IDE boot and all is fine as far as drives go here, will give it another bash tomorrow... if I don't fall asleep before the F1 that is...

[Snowhog]

EDIT: WAIT, WAIT -- I just realized, your filesystem table says ext3, but your blkid output says ext2! That can't be right!...

Actually, it can. blkid on my system (Kubuntu Feisty) also shows " SEC_TYPE="ext2" TYPE="ext3" on my ext3 partitions. And, yes, my partitions are formatted as ext3, not ext2. So, SEC_TYPE=[something] doesn't refer to the actual format of the partition, the " TYPE="ext3" does.

[Rog131]

1. "hd_" is not a drive type that *buntu is using any more for /dev designation of hard drives. Since Feisty, the new atapi driver makes them all "sd_",

Here ide drives are hdX.

Note
After linux-image-2.6.20-14-generic and etc everything is SATA (hda->sda)but after linux-image-2.6.20-15-generic (2.6.20-15.25) to 2.6.20-15.27 sda -> hda again ;)
Topic: Everything is SATA
http://kubuntuforums.net/forums/index.php?topic=3081634.0

And In Gutsy hda is hda.


You can remove UUID's from fstab and use /dev's.
And sometimes:
fstab UUID's?
http://ubuntuforums.org/showthread.php?t=223182

also had /etc/fstab replaced during an upgrade, and after the reboot my ext3 partitions were mounted, but NTFS ones weren't. After I changed back UUID=... to /dev/sdX for NTFS partitions, everything was mounted again on boot.
and

Here the new UUID magic fails to work with LVM volumes (especially annoying if your rootfs is on LVM).

Why UUID:

UUIDs are unique identifiers genereated on file system creation. No matter if you change how the hd is connected to your system (for example primary/secondary master/slave for IDE) the UUID never changes, whereas the device node can change. Thus the association between mount point and partition is more robust when using UUIDs.

[Uber Nooblett]

1. "hd_" is not a drive type that *buntu is using any more for /dev designation of hard drives. Since Feisty, the new atapi driver makes them all "sd_",

Here ide drives are hdX.

Note
After linux-image-2.6.20-14-generic and etc everything is SATA (hda->sda)but after linux-image-2.6.20-15-generic (2.6.20-15.25) to 2.6.20-15.27 sda -> hda again ;)
Topic: Everything is SATA
http://kubuntuforums.net/forums/index.php?topic=3081634.0

And In Gutsy hda is hda.


You can remove UUID's from fstab and use /dev's.
And sometimes:
fstab UUID's?
http://ubuntuforums.org/showthread.php?t=223182

also had /etc/fstab replaced during an upgrade, and after the reboot my ext3 partitions were mounted, but NTFS ones weren't. After I changed back UUID=... to /dev/sdX for NTFS partitions, everything was mounted again on boot.
and

Here the new UUID magic fails to work with LVM volumes (especially annoying if your rootfs is on LVM).

Why UUID:

UUIDs are unique identifiers genereated on file system creation. No matter if you change how the hd is connected to your system (for example primary/secondary master/slave for IDE) the UUID never changes, whereas the device node can change. Thus the association between mount point and partition is more robust when using UUIDs.



the first time I wrote the fstab for Gutsy, i didnt use UUIDs and had the same issue, so I added them in to see if they did anything, but no joy as you can see

[dibl]

And In Gutsy hda is hda.



Wellllllllll, let me just keep it confused, by noting that the blkid output in my post above is from Gutsy Beta installed just last night, with zero manipulation on my part. So it obviously tagged my Maxtor IDE drive as /dev/sda!

@Snowhog -- yeah, I googled the SEC_TYPE and see it is something other than the installed filesystem type, although I didn't really find the actual definition of it. I wonder if this is something for laptops, versus desktops? I'm running on big desktop box, and don't need the power-saving features -- I wonder if that makes a difference in this matter? :P

[dibl]

Here's the fstab that Gutsy wrote last night when I installed the Beta (64-bit):


# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb1
UUID=b1869c3e-b13a-4772-914c-bcc6db718967 / reiserfs notail 0 1
# /dev/sdb2
UUID=a6c2ba7b-8492-4746-92af-5182dcb4daab /home reiserfs defaults 0 2
# /dev/sda1
UUID=f222f97f-278f-4db5-8642-513294f30193 /media/sda1 reiserfs defaults 0 2
# /dev/sda3
UUID=adf641ca-f64e-4311-bc30-86bfcdcb669c /media/sda3 reiserfs defaults 0 2
# /dev/sdc1
UUID=1ddd0144-0875-4667-9f98-e90a23f58ff3 /media/sdc1 reiserfs defaults 0 2
# /dev/sdc2
UUID=710efad8-9f97-4bcd-8f57-8f8cc1facc2f /media/sdc2 reiserfs defaults 0 2
# /dev/sdc3
UUID=f1912a56-2e5c-45ce-b91b-3ebbe69e20f4 /media/sdc3 reiserfs defaults 0 2
# /dev/sdd1
UUID=cffddf89-57f3-40ab-a97f-40bb1ea45f16 /media/sdd1 reiserfs defaults 0 2
# /dev/sdd3
UUID=9b7658da-59e1-4b2b-a4b9-fa3ee11b68cf /media/sdd3 reiserfs defaults 0 2
# /dev/sde1
UUID=d182b7c3-298c-49b3-ac66-b378033b815c /media/sde1 reiserfs defaults 0 2
# /dev/sdd2
UUID=94d4d572-3581-491b-90dc-e5f619c65908 none swap sw 0 0
# /dev/sdf1
UUID=A8FC3435FC33FC5E /media/NTFSTUFF ntsf user,noauto,exec 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0


The only thing I added was the line for the USB thumb drive, which I had to make a mount point for. You will note that the sda2 partition, which is a swap partition for E-Live, isn't mounted.

[Rog131]

Wellllllllll, let me just keep it confused, by noting that the blkid output in my post above is from Gutsy Beta installed just last night, with zero manipulation on my part. So it obviously tagged my Maxtor IDE drive as /dev/sda!


Here's the fstab that Gutsy wrote last night when I installed the Beta (64-bit):

Hmm - I have 32 version. Is there difference between 32 vs 64 ?

:~$ blkid
/dev/sda1: UUID="b5b21967-81b8-417d-a2a5-e6c603bcdbb5" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="4319687d-5dd9-481f-b081-5fa1d21cde72" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: UUID="f505860a-9d5e-4386-b6a8-9b6b97134f23" TYPE="swap"
/dev/sda4: UUID="30172fdc-6826-499c-8770-0f8608e8559f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: UUID="75bb010f-19d2-42e5-a136-15711d8fa4a6" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: UUID="11ef7adc-f027-42e5-9fdb-c68a39019f83" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb3: UUID="2c6f4d74-7362-46d1-b335-89ddb913037a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb4: UUID="b5078222-b866-4c87-8402-0c445fc48dac" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda1: LABEL="SYSTEM" UUID="0E5D-19FE" TYPE="vfat"
/dev/hda5: LABEL="SWAP" UUID="3606-1C07" TYPE="vfat"
/dev/hda6: LABEL="DATA" UUID="2A3D-1CD4" TYPE="vfat"
/dev/hda7: LABEL="STORAGE" UUID="333B-1CDD" TYPE="vfat"
/dev/hdb1: UUID="6AF43351F4331EAF" TYPE="ntfs"


And my fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb1
UUID=75bb010f-19d2-42e5-a136-15711d8fa4a6 / ext3 defaults,errors=remount-ro 0 1
# /dev/sdb2
UUID=11ef7adc-f027-42e5-9fdb-c68a39019f83 /home ext3 defaults 0 2
# /dev/hda6
UUID=2A3D-1CD4 /media/hda6 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/hda7
UUID=333B-1CDD /media/hda7 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda2
UUID=4319687d-5dd9-481f-b081-5fa1d21cde72 /media/sda2 ext3 defaults 0 2
# /dev/sda4
UUID=30172fdc-6826-499c-8770-0f8608e8559f /media/sda4 ext3 defaults 0 2
# /dev/sdb3
UUID=2c6f4d74-7362-46d1-b335-89ddb913037a /media/sdb3 ext3 defaults 0 2
# /dev/sdb4
UUID=b5078222-b866-4c87-8402-0c445fc48dac /media/sdb4 ext3 defaults 0 2
# /dev/sda3
UUID=f505860a-9d5e-4386-b6a8-9b6b97134f23 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

Damn - seems that Kubuntu (as default) wants to check fat drives. Correcting those :(

[dibl]

Doesn't make much sense that they would have a different drive ID system for 64-bit ???

I dunno ... I guess it is what it is. :)

Rog, your IDE drives are all formatted VFAT or NTFS -- I wonder if that triggers the "hd_" designation?

[Uber Nooblett]

How odd...

When I installed Gutsy, the only things it wrote in the fstab where the hard drive it was installed on and the removeable media (DVDRW) and nothing else. I added in all the others myself

However, when I first started up gutsy, it showed the other drives, just had that error on them. They where not in the fstab though....

[Uber Nooblett]

You'll never guess what I forgot to do....

I only forgot to create the bloody mount points ::)

yes, yes, I know, I get the medal shaped like a willy for my daftness ;D

*shoots self in face with elastic band gun*

btw, in Gutsy, is there a way to reboot/shut down without loging out first? only option I have in log out is 'log out' at the mo.
Sure I'll find the option after a while, but thought I'd ask while I'm here :D

[Uber Nooblett]

nm, found the option for my last question :) no i didn't, already looks enabled there but its not

[Rog131]

btw, in Gutsy, is there a way to reboot/shut down without loging out first? only option I have in log out is 'log out' at the mo.

Topic: Logout bug???
http://kubuntuforums.net/forums/index.php?topic=3086945.0

Workaround in the konsole:

:~$ sudo shutdown -r now

-r Reboot after shutdown.
-h Halt or poweroff after shutdown.

[dibl]

You'll never guess what I forgot to do....

I only forgot to create the bloody mount points ::)


But, didn't the installation process give you that option? Ahhh, I'll bet you took the "use the whole disk" rather than "manual" approach? If you use the Alternate Install CD, and use the "manual" method when it gets to the partitioner, you get to pick the mount points for each partition, tell it whether to format or leave them as-is, and for your "extra" swap partition you can just tell it "do not use". It pretty much eliminates having to brew your own fstab file.


btw, in Gutsy, is there a way to reboot/shut down without loging out first? only option I have in log out is 'log out' at the mo.


As Rog131 notes, there have been some bugs reported.

If you just need to restart your X session (like trying your new xorg.conf file), you can Ctrl-Alt-Backspace and you don't have to shut down the rest of the system. Otherwise, my favorite non-GUI command to do a reboot is
sudo shutdown now -r :)