Choose style:

Author Topic: Disk mount notification at boot [SOLVED]  (Read 934 times)

0 Members and 1 Guest are viewing this topic.

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4808
  • Karma: 1013
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 8 Respin-2 (64-bit)
Disk mount notification at boot [SOLVED]
« on: March 02, 2016, 03:10:11 pm »
Hi all, I'm not sure if this is really a problem or just a quirk  ;).  I used Clonezilla to make images of three of my partitions.  As I expected, that went very well.  My /boot, / and /home are nicely backed up and safe on an external drive.  I took the opportunity to sling a different distro onto the old Fujitsu Siemens AMILO li3710 using the same partition table as for Peppermint Six; just to have a tinker around with  The distro in question was SparkyLinux, a very nice Debian Testing based distro from Poland.  Again no issues,  The SparkyLinux home folder was symlinked to the /DATA partition That was manually mounted in fstab and away she went.  The job was really effortless to do.  Anyway, I decided to sling the saved Peppermint Images back on the computer.  That naturally went without a hitch.  The three partitions were restored and the machine booted up.  Just after the progress splash screen I receive a warning to, "press S to skip mounting or press M to manually mount" or, words to that effect.  I left it and the computer booted up as normal.  I checked fdisk -l, blkid and fstab for inconsistencies and they all check out as far as I can see.
Code: [Select]
andy@andy-AMILO-Li3710 ~ $ sudo fdisk -l
[sudo] password for andy:

Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00088042

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      820407      409180   83  Linux
/dev/sda2          821248    42764287    20971520   83  Linux
/dev/sda3        42764288    84709375    20972544   83  Linux
/dev/sda4        84711422  1465147391   690217985    5  Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5        84711424  1448372223   681830400   83  Linux
/dev/sda6      1448374272  1465147391     8386560   82  Linux swap / Solaris

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x205239d8

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048  1953525167   976761560   83  Linux
andy@andy-AMILO-Li3710 ~ $
and  blkid
Code: [Select]
andy@andy-AMILO-Li3710 ~ $ sudo blkid
/dev/sda1: UUID="f91087f5-bc7d-4738-8567-7b5196762d6a" TYPE="ext4"
/dev/sda2: UUID="a1a75cdf-4d30-4133-b6a2-01be29123559" TYPE="ext4"
/dev/sda3: UUID="f874bdbb-2456-4af2-bf0a-66b73c756144" TYPE="ext4"
/dev/sda5: UUID="b5ccb4b7-9133-4abc-8b74-9ecf4f1d3d06" TYPE="ext4"
/dev/sda6: UUID="3a466731-ef46-4cad-91bc-2138ba962bc4" TYPE="swap"
/dev/sdc1: LABEL="Intenso-1TB" UUID="bcc79bfb-0e51-4cee-a287-9506fbfd9812" TYPE="ext4"
andy@andy-AMILO-Li3710 ~ $
Finally my fstab
Code: [Select]
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda2 during installation
UUID=a1a75cdf-4d30-4133-b6a2-01be29123559 /               ext4    errors=remount-ro 0    $
# /boot was on /dev/sda1 during installation
UUID=f91087f5-bc7d-4738-8567-7b5196762d6a /boot           ext4    defaults        0      $
# /home was on /dev/sda3 during installation
UUID=f874bdbb-2456-4af2-bf0a-66b73c756144 /home           ext4    defaults        0      $
# swap was on /dev/sda6 during installation
UUID=745712c9-209c-482a-93f1-77de77679dc2 none            swap    sw              0      $
# Mount DATA partition under /mnt/DATA
UUID=b5ccb4b7-9133-4abc-8b74-9ecf4f1d3d06  /mnt/DATA     ext4     defaults     0     2




                                    [ Read 17 lines ]
^G Get Help    ^O WriteOut    ^R Read File   ^Y Prev Page   ^K Cut Text    ^C Cur Pos
^X Exit        ^J Justify     ^W Where Is    ^V Next Page   ^U UnCut Text  ^T To Spell
As I said it all checks out and the computer is running like a champ.  The symlinks are all working.  For the life of me, I can't figure out why I'm receiving the advisory message at boot.  Any ideas, or am I missing something crucial  :-\?
« Last Edit: March 02, 2016, 04:21:11 pm by AndyInMokum, Reason: Marking topic as solved. »
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.

Offline zebedeeboss

  • Global Moderator
  • Hero
  • *****
  • Posts: 3145
  • Karma: 567
  • Life first... Peppermint a close 2nd :)
    • View Profile
  • Peppermint version(s): P10 / P9 Respin
Re: Disk mount notification at boot
« Reply #1 on: March 02, 2016, 03:29:04 pm »
looks like your swap partition has two differing UUIDs in blkid and fstab ?
Be Kind Whenever Possible...   It is Always Possible - Dalai Lama

Linux User #565092
P10 x64 Desktop - AMD Threadrippe 2950X - 64Gb RAM - NVIDIA RTX2080Ti 11Gb - 1 x 43" 1 x 27" 4k 3840x2160 - 1 x 34" 5120x2160
P10 x64 Laptop - i7-7700HQ - 8Gb RAM - Nvidia GTX1050 4Gb - 15.6" HD 1920x1080

Offline Slim.Fatz

  • Trusted User
  • Veteran
  • *****
  • Posts: 1815
  • Karma: 474
  • Where's the mouse?
    • View Profile
  • Peppermint version(s): Peppermint 7, 8.5 & 10 - 64bit
Re: Disk mount notification at boot
« Reply #2 on: March 02, 2016, 04:01:11 pm »
Hi AndyInMokum,

ditto to what zebedeeboss said -- and also comparing the UUID in blkid with that in fstab for /dev/sdc1 (which I think is your /mnt/DATA partition) I see that they are also different.

Regards,

-- Slim
"Life first -- Peppermint a close 2nd!" -- Zeb

Tread lightly: Fluxbox, JWM, i3, Openbox, awesome

Offline zebedeeboss

  • Global Moderator
  • Hero
  • *****
  • Posts: 3145
  • Karma: 567
  • Life first... Peppermint a close 2nd :)
    • View Profile
  • Peppermint version(s): P10 / P9 Respin
Re: Disk mount notification at boot
« Reply #3 on: March 02, 2016, 04:14:57 pm »
I think his data is sda5 which has the same UUID but only Andy can confirm
Be Kind Whenever Possible...   It is Always Possible - Dalai Lama

Linux User #565092
P10 x64 Desktop - AMD Threadrippe 2950X - 64Gb RAM - NVIDIA RTX2080Ti 11Gb - 1 x 43" 1 x 27" 4k 3840x2160 - 1 x 34" 5120x2160
P10 x64 Laptop - i7-7700HQ - 8Gb RAM - Nvidia GTX1050 4Gb - 15.6" HD 1920x1080

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4808
  • Karma: 1013
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 8 Respin-2 (64-bit)
Re: Disk mount notification at boot
« Reply #4 on: March 02, 2016, 04:15:35 pm »
Wow, it sure helps to have the extra sets of eyes.  I checked this so many times and totally missed it.  I'll fix that in the morning.  That computer is in the bedroom and the wife is sleeping.  I don't want to wake her up.  I'd rather poke a rabid hyena in the eye with a pointy stick than do that  ;D.  I think I can safely jump the gun and call this one, [SOLVED].  Thanks again for the extra eyes  ;).
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.

Offline AndyInMokum

  • Global Moderator
  • Hero
  • *****
  • Posts: 4808
  • Karma: 1013
  • "Keep on Rockin' in the Free World"
    • View Profile
  • Peppermint version(s): PM 9 & PM 8 Respin-2 (64-bit)
Re: Disk mount notification at boot
« Reply #5 on: March 02, 2016, 04:20:16 pm »
I think his data is sda5 which has the same UUID but only Andy can confirm
Yeah, my /DATA partition is /dev/sda5.  An issue would have only shown up if the swap space was used.  That would probably have been never too  ;).
Backup! Backup! Backup! If you're missing any of these -  you ain't Backed Up!
For my system info please L/click HERE.