Mageia forum

fstab wrote:# Entry for /dev/sdc1 :
UUID=8612ece5-255b-4d3e-8ebe-c7c66988f534 / ext4 acl,discard,relatime 1 1
# Entry for /dev/sdc6 :
UUID=7c3ffa94-54fd-47b5-b9a0-c308c79132da /home ext4 acl,discard,relatime 1 2
/dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0
# Entry for /dev/sda1 :
UUID=DE72CD2C72CD09EB /media/win_c ntfs-3g defaults,umask=000 0 0
# Entry for /dev/sdb1 :
UUID=FEA64E68A64E220F /media/win_c2 ntfs-3g defaults,umask=000 0 0
# Entry for /dev/sda2 :
UUID=78BACED6BACE9054 /media/win_d ntfs-3g defaults,umask=000 0 0
none /proc proc defaults 0 0
none /tmp tmpfs defaults 0 0
# Entry for /dev/sda6 :
#UUID=f728e18d-6441-48eb-9d5b-1f8bf38c1154 swap swap defaults 0 0
# Entry for /dev/sdc5 :
#UUID=c017c0d2-f6d2-47bc-a051-9e7a2b273a3e swap swap defaults 0 0

yankee495 wrote:OK,

I have a SSD as sda that is all one partition and is bootable Win7. This is physical drive one in the computer.
I have a SSD as sdb that has / and /home on it. Bootable Mageia. This is physical drive two.
I have a HDD as sdc that is a Win7 drive that I used to boot on and is still bootable if you select it as a boot device at BIOS. This is drive three.

What I done was install a SSD and put Win7 on it with it being the only drive hooked up so it is stand alone, first drive.
Then I installed Mageia on the second SSD which is where grub is. This allows booting to the old HDD with Win7. Or you can boot the Win7 SSD or Mageia SSD.

The old HDD is the third physical drive in the system. It is making a clicking noise in Win7 and stalls the computer. Something is wrong but it seems to work fine in Linux...no clicking problem. I want to just unplug it so it don't go out before I get another one to replace it.

So when I unplug it and select to boot from the second SSD I get the full boot menu, and Mageia will start to boot. Then hangs at starting home.

After stalling a bit it says failed (aborted) to renumber drives etc. Here is what is strange.

# Entry for /dev/sdc1 :
UUID=8612ece5-255b-4d3e-8ebe-c7c66988f534 / ext4 acl,discard,relatime 1 1
# Entry for /dev/sdc6 :
UUID=7c3ffa94-54fd-47b5-b9a0-c308c79132da /home ext4 acl,discard,relatime 1 2
/dev/cdrom /media/cdrom auto umask=0,users,iocharset=utf8,noauto,ro,exec 0 0
# Entry for /dev/sda1 :
UUID=DE72CD2C72CD09EB /media/win_c ntfs-3g defaults,umask=000 0 0
# Entry for /dev/sdb1 :
UUID=FEA64E68A64E220F /media/win_c2 ntfs-3g defaults,umask=000 0 0
# Entry for /dev/sda2 :
UUID=78BACED6BACE9054 /media/win_d ntfs-3g defaults,umask=000 0 0
none /proc proc defaults 0 0
none /tmp tmpfs defaults 0 0
# Entry for /dev/sda6 :
#UUID=f728e18d-6441-48eb-9d5b-1f8bf38c1154 swap swap defaults 0 0
# Entry for /dev/sdc5 :
#UUID=c017c0d2-f6d2-47bc-a051-9e7a2b273a3e swap swap defaults 0 0

The third drive is the HDD and in Partition management shows it as sdc but in fstab it is listed as sda2. The order is wrong.

Mount point: /media/win_c2
Device: sda1
Volume label: SSD1
DOS drive letter: C (just a guess)
Type: NTFS-3G
Size: 111GB (99%)
Mounted

Mount point: /
Device: sdb1
Type: Journalised FS: ext4
Size: 37GB (33%)
Mounted

DISABLED SWAP sdb5 here.

Mount point: /home
Device: sdb6
Type: Journalised FS: ext4
Size: 70GB (63%)
Mounted

Device: sdc
Size: 931GB
Name: Seagate Technology 1000524AS

I should be able to unplug the third drive as it has no system files or links to it and should not be physically in front of the other drives to cause a reorder...it should be able to disappear. I've been on this one for a long time and can't get it.

I didn't put it in code tags because cross referencing the partitions with fstab seems easier layed out. I'm as confused as a guy can get.

Any ideas?

• your post is about a rather easy problem, but by not using code tags, or clear markup, and using different sources of information
  with different layout and differing grades of information, makes it rather unclear, complex and possibly difficult ot understand.
  -> I've changed the layout and re-structured it. Only kept your original version as quote, to show the difference.
• the comments in fstab are static, once written they won't change IIRC. So the comments and the actual device names may differ
  -> use blkid, shows the device name, UUID and Labels where available, also the filesystem on it rather clearly.
• the order in fstab is irrelevant, also the names used there are only smoke and mirrors
  -> see above for blkid
• entries in fstab, for which the device is not always present, should be marked as nofail. Check the comment for that in errata:
  https://wiki.mageia.org/en/Mageia_2_Err ... t_in_fstab

yankee495 wrote:All of this is over a 1TB HDD that goes click and the computer stalls...the click is like the old HD's when you killed the power and the head parked, but it may do it once or 10 times...only in Win7, not Mageia. Very strange. I checked drivers and cables and kept coming back to the fact it is ok in Linux.

I think it is about to fail.