Announcement

Collapse
No announcement yet.

The Colonel's 11 secret herbs and spices, or trouble with linux images...

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    The Colonel's 11 secret herbs and spices, or trouble with linux images...

    I have attached a list of system spec's, which a sticky requests,
    in a text file.

    The following images are installed:
    linux-image-2.6.32-38-generic
    Installed version: 2.6.32-38.83

    linux-image-2.6.32-41-generic
    Installed version: 2.6.32-42.94

    linux-image-2.6.32-42-generic
    Installed version: 2.6.32-42.96

    linux-image-2.6.32-45-generic
    Installed version: 2.6.32-45.102
    However, I must manually select the earliest,
    DURING EACH BOOT.

    Otherwise, the system usually hangs,
    forever showing the marching dots, under the Ubuntu graphic.
    When I get a message, it refers to cryptswap1...

    I would rather have the system able to boot, unattended,
    and assume the latest image is usually better.

    Anyone?
    Attached Files
    Last edited by elludium_q-36; Jan 14, 2013, 11:07 PM.
    Tags: boot, cryptswap, kernel, linux image, linux-image
    • Top
    • Bottom
    #2
    Without knowing the exact wording of the error message, it's difficult for us to help you troubleshoot problems.
    • Top
    • Bottom

    Comment

      #3
      Error Message.

      True...

      resume: libgcrypt version: 1.4.4
      resume: Could not stat the resume device file '/dev/mapper/cryptswap1
      Please type in the full path name to try again or press ENTER to boot the system
      I tried searching for a reference to this problem, in vain.

      Hopefully, someone knows the answer, so the next person may search.

      Thanks.
      • Top
      • Bottom

      Comment

        #4
        Please show the output of
        Code:
        cat /etc/fstab
        and
        Code:
        ll /dev/disk/*
        • Top
        • Bottom

        Comment

          #5
          Q-bert says: "@#$ ^&*@ !#"

          Anyone remember the classic arcade game Qbert?

          The characer cursed in ascii/symbols...


          *I tried to reduce/resize images, but BBcode didn't work*

          Unfortunately, now, with all kernels, I see:
          resume: libgcrypt version: 1.4.4
          resume: Could not stat the resume device file '/dev/mapper/cryptswap1
          Please type in the full path name to try again or press ENTER to boot the system
          The /home/ directory is encyrpted, and I would like access to my data...
          I tried some "ecryptfs" related commands, but hit brick walls.
          In case it's not clear, or someone hasn't read the thread,
          I'm unable to boot into this particular environment,
          and receive the message above.

          Currently I'm booting from 10.04, via a HDD, connected by USB.

          I ran the commands requested by SteveRiley,
          but removed UUIDs/GUIDs, username/hostname, volume name / partition name, etc.,
          in case such could be exploited by a potential cracker.
          Bear in mind the commands were run from my CURRENT USB HDD boot environment!

          The disk in question is mounted at /dev/sda
          That is to say the one with which I have difficulty, is sda*
          I'm booting/running on /dev/sdb

          Code:
          User@host:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' 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>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdc1 during installation
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdc2 during installation
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx none            swap    sw              0       0
user@host:~$

          Code:
          user@host:~$ ll /dev/disk/*
/dev/disk/by-id:
total 0
drwxr-xr-x 2 root root 420 2013-01-29 15:18 ./
drwxr-xr-x 6 root root 120 2013-01-29 15:18 ../
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 ata-ST320413A_7ED1S9G3 -> ../../sda
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 ata-ST320413A_7ED1S9G3-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 ata-ST320413A_7ED1S9G3-part2 -> ../../sda2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 ata-ST320413A_7ED1S9G3-part5 -> ../../sda5
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 ata-ST320413A_7ED1S9G3-part6 -> ../../sda6
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 scsi-SATA_ST320413A_7ED1S9G3 -> ../../sda
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 scsi-SATA_ST320413A_7ED1S9G3-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 scsi-SATA_ST320413A_7ED1S9G3-part2 -> ../../sda2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 scsi-SATA_ST320413A_7ED1S9G3-part5 -> ../../sda5
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 scsi-SATA_ST320413A_7ED1S9G3-part6 -> ../../sda6
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-Generic_USB_CF_Reader_9205291-0:1 -> ../../sde
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-Generic_USB_MS_Reader_9205291-0:3 -> ../../sdg
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-Generic_USB_SD_Reader_9205291-0:0 -> ../../sdd
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-Generic_USB_SM_Reader_9205291-0:2 -> ../../sdf
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-Hitachi_HDP725016GLA380_0000001E9864-0:0 -> ../../sdb
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 usb-Hitachi_HDP725016GLA380_0000001E9864-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 usb-Hitachi_HDP725016GLA380_0000001E9864-0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 usb-Hitachi_HDP725016GLA380_0000001E9864-0:0-part3 -> ../../sdb3
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 usb-HP_Photosmart_C4180_MY678C519R04J7-0:0 -> ../../sdc

/dev/disk/by-label:
total 0
drwxr-xr-x 2 root root 120 2013-01-29 15:18 ./
drwxr-xr-x 6 root root 120 2013-01-29 15:18 ../
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 ExtraStorage -> ../../sdb3
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 xxxVideo DVDxxxx -> ../../sr0
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 LockedDisk -> ../../sda2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 HDDonUSB -> ../../sdb1

/dev/disk/by-path:
total 0
drwxr-xr-x 2 root root 340 2013-01-29 15:18 ./
drwxr-xr-x 6 root root 120 2013-01-29 15:18 ../
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:0f.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:0f.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:0f.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:0f.0-scsi-0:0:0:0-part5 -> ../../sda5
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:0f.0-scsi-0:0:0:0-part6 -> ../../sda6
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:0f.0-scsi-1:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.3-usb-0:2:1.0-scsi-0:0:0:0 -> ../../sdd
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.3-usb-0:2:1.0-scsi-0:0:0:1 -> ../../sde
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.3-usb-0:2:1.0-scsi-0:0:0:2 -> ../../sdf
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.3-usb-0:2:1.0-scsi-0:0:0:3 -> ../../sdg
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.4-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:10.4-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:10.4-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 pci-0000:00:10.4-usb-0:1:1.0-scsi-0:0:0:0-part3 -> ../../sdb3
lrwxrwxrwx 1 root root   9 2013-01-29 15:18 pci-0000:00:10.4-usb-0:4:1.3-scsi-0:0:0:0 -> ../../sdc

/dev/disk/by-uuid:
total 0
drwxr-xr-x 2 root root 140 2013-01-29 15:18 ./
drwxr-xr-x 6 root root 120 2013-01-29 15:18 ../
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 xxxx-xxxx -> ../../sdb3
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 xxxx-xxxx -> ../../sda6
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -> ../../sdb1
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -> ../../sdb2
lrwxrwxrwx 1 root root  10 2013-01-29 15:18 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -> ../../sda2
user@host:~$
          At this point, I'd be happy to retrieve my data.
          HOWEVER, I've seen the following message before:
          resume: libgcrypt version: 1.4.4
          resume: Could not stat the resume device file '/dev/mapper/cryptswap1
          Please type in the full path name to try again or press ENTER to boot the system
          and would like to know how to tackle that, in the future.
          I doubt I'm the only one...

          Thanks for having a look!
          • Top
          • Bottom

          Comment

            #6
            Originally posted by elludium_q-36 View Post
            but removed UUIDs/GUIDs, username/hostname, volume name / partition name, etc.,
            in case such could be exploited by a potential cracker.
            Part of my reason for asking to see those outputs is to view the exact information in the files. Hiding them won't allow me to see whether their contents are correct. The present values have zero utility to someone who might be interested in attacking your machine.

            Originally posted by elludium_q-36 View Post
            HOWEVER, I've seen the following message before:
            You have a borked encrypted swap partition. A thread on the Ubuntu forum explains how to fix it. I would actually suggest that you discontinue using an encrypted swap partition, and instead use an ordinary one.

            If I'm reading your most recent post correctly, it appears you've completely lost access to your encrypted home folder now. Is that correct?
            • Top
            • Bottom

            Comment

              #7
              Originally posted by elludium_q-36 View Post
              Currently I'm booting from 10.04, via a HDD, connected by USB.

              I ran the commands requested by SteveRiley,
              but removed UUIDs/GUIDs, username/hostname, volume name / partition name, etc.,
              in case such could be exploited by a potential cracker.
              Bear in mind the commands were run from my CURRENT USB HDD boot environment!

              The disk in question is mounted at /dev/sda
              That is to say the one with which I have difficulty, is sda*
              I'm booting/running on /dev/sdb
              Why hide the UUIDs then tell me /dev/sdb... they basically hold the same amount of information to a cracker (basically nothing) infact /dev/sdb tells me more, it tells me you have at least two hard disk drives, the UUID even blanked out looks like an ext volume, which you freely tell us anyway that is about all you can tell/use from knowing a UUID on someones computer.
              Also, why hide your username and host name and freely give out your version info. Host name is basically useless, it is used by your computer and maby published on your local network but if they have your IP (which can be obtained when ever you use the internet) then crackers do not care about your hostname. Username is basically useless without a password or some other info, and I already know one user name on your computer: root. Version info is far more valuable as crackers can now see what version you are running and look for vulnerabilities in that version... If you are going to be paranoid about security then you may as well do it properly note: the best way to stop cracker is scissors + network cable
              • Top
              • Bottom

              Comment

              Previous template Next
              Working...
              X