hibernate problem ...

Archived topics about LMDE 1
Forum rules
alirezaimi
Level 2
Level 2
Posts: 61
Joined: Tue Feb 08, 2011 5:18 am

hibernate problem ...

Postby alirezaimi » Thu Aug 04, 2011 5:56 am

Hi
H have a problem with hibernate in my lmde(64bit),when i hibernate my laptop this error showed and turn off system!

Code: Select all

ata1.01: failed to resume link (SControl 0)
ata2.01: failed to resume link (SControl 0)

I use all solution in this forum but this problem doesn't solved.

Code: Select all

alireza@alireza-lap ~ $ sudo blkid
...
/dev/sda7: UUID="b5f10312-e7b2-402b-91de-35d493d83e16" TYPE="swap"


Code: Select all

alireza@alireza-lap ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --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    defaults        0       0
# / was on /dev/sda1 during installation
UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f /               ext3    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
proc    /proc   proc    nodev,noexec,nosuid     0       0
# /dev/sda5     /home   ext4    rw,errors=remount-ro    0       0
UUID=28679b7c-bd5a-4fc2-84d5-e795450cb72b       /home   ext4    rw,errors=remount-ro    0       0
# /dev/sda6     /       ext4    rw,errors=remount-ro    0       0
UUID=e8d056a1-28d6-44d9-b5a9-ea317b617ce9       /       ext4    rw,errors=remount-ro    0       0
# /dev/sda7     swap    swap    sw      0       0
UUID=b5f10312-e7b2-402b-91de-35d493d83e16       swap    swap    sw      0       0


Code: Select all

alireza@alireza-lap ~ $ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=b5f10312-e7b2-402b-91de-35d493d83e16


any ideas?
Thanks.

User avatar
mads
Level 6
Level 6
Posts: 1301
Joined: Wed Nov 03, 2010 3:44 pm
Contact:

Re: hibernate problem ...

Postby mads » Thu Aug 04, 2011 7:32 pm

alirezaimi wrote:

Code: Select all

alireza@alireza-lap ~ $ sudo blkid
...
/dev/sda7: UUID="b5f10312-e7b2-402b-91de-35d493d83e16" TYPE="swap"


Code: Select all

# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none            swap    sw              0       0
...
# /dev/sda7     swap    swap    sw      0       0
UUID=b5f10312-e7b2-402b-91de-35d493d83e16       swap    swap    sw      0       0


Code: Select all

alireza@alireza-lap ~ $ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=b5f10312-e7b2-402b-91de-35d493d83e16



Hi! You could try this:

1)
$ sudo swapoff /dev/sda7
$ sudo swapoff /dev/sda2

or
$ sudo swapoff –a

2)
$ sudo mkswap /dev/sda7
The output shows also shows the UUID for new swap
... UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

3) $ gksudo gedit /etc/fstab
Change swap's UUID, like this
# /dev/sda7 swap swap sw 0 0
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx swap swap sw 0 0

and comment out the line after "# swap was on /dev/sda2...", like this:
# UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none swap sw 0 0

4) $ gksudo gedit /etc/initramfs-tools/conf.d/resume
Replace the old UUID with the new one, like this
RESUME=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

5)
$ sudo swapon UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
or
$ sudo swapon –U xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

6) $ sudo update-initramfs -u

7) Reboot

alirezaimi
Level 2
Level 2
Posts: 61
Joined: Tue Feb 08, 2011 5:18 am

Re: hibernate problem ...

Postby alirezaimi » Fri Aug 05, 2011 7:21 am

Thanks u madas for your answer, I do that but swap does not work ,

Code: Select all

alireza@alireza-lap ~ $ sudo blkid
[sudo] password for alireza:
/dev/sda1: LABEL="System Reserved" UUID="76D89B21D89ADEA5" TYPE="ntfs"
/dev/sda2: UUID="B02AA7A82AA769D4" TYPE="ntfs"
/dev/sda4: UUID="1E2AB0A82ECB5AF8" TYPE="ntfs"
/dev/sda7: UUID="8afd3408-7c66-4c69-b194-3508c8e6bfef" TYPE="swap"
/dev/sda5: UUID="28679b7c-bd5a-4fc2-84d5-e795450cb72b" TYPE="ext4"
/dev/sda6: UUID="e8d056a1-28d6-44d9-b5a9-ea317b617ce9" TYPE="ext4"
/dev/sda8: UUID="7dd5fc28-74d1-44d9-a983-61bf1e34d90b" TYPE="ext4"

Code: Select all

alireza@alireza-lap ~ $ cat /etc/initramfs-tools/conf.d/resume
RESUME=UUID=8afd3408-7c66-4c69-b194-3508c8e6bfef

Code: Select all

alireza@alireza-lap ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --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    defaults        0       0
# / was on /dev/sda1 during installation
#UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f /               ext3    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
#UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
proc    /proc   proc    nodev,noexec,nosuid     0       0
# /dev/sda5     /home   ext4    rw,errors=remount-ro    0       0
UUID=28679b7c-bd5a-4fc2-84d5-e795450cb72b       /home   ext4    rw,errors=remount-ro    0       0
# /dev/sda6     /       ext4    rw,errors=remount-ro    0       0
UUID=e8d056a1-28d6-44d9-b5a9-ea317b617ce9       /       ext4    rw,errors=remount-ro    0       0
# /dev/sda7     swap    swap    sw      0       0
UUID=8afd3408-7c66-4c69-b194-3508c8e6bfef       swap    swap    sw      0       0


Code: Select all

alireza@alireza-lap ~ $ dmesg | grep ata
[    0.000000]  BIOS-e820: 000000009f7e0000 - 000000009f7ff000 (ACPI data)
[    0.000000] Memory: 3910552k/5636096k available (3314k kernel code, 1582384k absent, 143160k reserved, 3376k data, 596k init)
[    1.217671] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
[    1.218305] _OSC request data:1 8 1f
[    1.227575] _OSC request data:1 1f 1f
[    1.227621] _OSC request data:1 0 1d
[    1.819334] Write protecting the kernel read-only data: 6144k
[    1.922672] libata version 3.00 loaded.
[    1.964255] ata_piix 0000:00:1f.2: version 2.13
[    1.964287] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    1.964298] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[    2.119744] ata_piix 0000:00:1f.2: setting latency timer to 64
[    2.120073] scsi0 : ata_piix
[    2.120180] scsi1 : ata_piix
[    2.120872] ata1: SATA max UDMA/133 cmd 0x4078 ctl 0x408c bmdma 0x4050 irq 19
[    2.120880] ata2: SATA max UDMA/133 cmd 0x4070 ctl 0x4088 bmdma 0x4058 irq 19
[    2.120917] ata_piix 0000:00:1f.5: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[    2.120925] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    2.275406] ata_piix 0000:00:1f.5: SCR access via SIDPR is available but doesn't work
[    2.275420] ata_piix 0000:00:1f.5: setting latency timer to 64
[    2.275676] scsi2 : ata_piix
[    2.275752] scsi3 : ata_piix
[    2.276104] ata3: SATA max UDMA/133 cmd 0x4068 ctl 0x4084 bmdma 0x4030 irq 21
[    2.276106] ata4: SATA max UDMA/133 cmd 0x4060 ctl 0x4080 bmdma 0x4038 irq 21
[    3.477219] ata1.01: failed to resume link (SControl 0)
[    3.477381] ata2.01: failed to resume link (SControl 0)
[    3.633019] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    3.633048] ata2.01: SATA link down (SStatus 0 SControl 0)
[    3.633065] ata2.01: link offline, clearing class 3 to NONE
[    3.633223] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.633241] ata1.01: SATA link down (SStatus 0 SControl 0)
[    3.641350] ata1.00: ATA-8: Hitachi HTS545050B9A300, PB4OC60F, max UDMA/133
[    3.641355] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    3.657294] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633C, AC01, max UDMA/100
[    3.657297] ata2.00: applying bridge limits
[    3.657365] ata1.00: configured for UDMA/133
[    3.689075] ata2.00: configured for UDMA/100
[    6.806116] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[   16.787251] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: errors=remount-ro


why hibernate not work?

CiaW
Level 3
Level 3
Posts: 170
Joined: Fri Sep 10, 2010 11:39 am
Location: Spokane Wash, USA

Re: hibernate problem ...

Postby CiaW » Fri Aug 05, 2011 12:29 pm

I'm not sure whether this has any bearing on your hibernate issue (I'm having issues of my own, sorry!), but I did notice in your fstab it looks like your original root / partition is commented?

Code: Select all

# / was on /dev/sda1 during installation
#UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f /               ext3    errors=remount-ro 0       1

I looked again, and it looks like your / is now showing on sda6, and it's ext4 vs ext3 file system -- it's possible that might be causing some issues with hibernate. Not sure... any experts around that know if that is part of the issue?

User avatar
mads
Level 6
Level 6
Posts: 1301
Joined: Wed Nov 03, 2010 3:44 pm
Contact:

Re: hibernate problem ...

Postby mads » Sat Aug 06, 2011 1:25 pm

alirezaimi wrote:Thanks u mads for your answer, I do that but swap does not work,
why hibernate not work?

I see that you have done all the steps. I don't know why it is not working, very strange.

alirezaimi
Level 2
Level 2
Posts: 61
Joined: Tue Feb 08, 2011 5:18 am

Re: hibernate problem ...

Postby alirezaimi » Sat Aug 06, 2011 2:06 pm

mads wrote:
alirezaimi wrote:Thanks u mads for your answer, I do that but swap does not work,
why hibernate not work?

I see that you have done all the steps. I don't know why it is not working, very strange.



:roll:
Anyone ,any ideas??


Return to “Archive”

Who is online

Users browsing this forum: No registered users and 1 guest