# Problems with Linux after full Paragon restore

**URL:** <https://forums.suse.com/t/problems-with-linux-after-full-paragon-restore/23267>\
**Category:** SLED Install-Boot\
**Created:** [November 5, 2012, 7:50pm UTC](https://forums.suse.com/t/problems-with-linux-after-full-paragon-restore/23267 "2012-11-05T19:50:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![s660117](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@s660117](https://forums.suse.com/u/s660117)\
**Post date:** [November 5, 2012, 7:50pm UTC](https://forums.suse.com/t/problems-with-linux-after-full-paragon-restore/23267/1 "2012-11-05T19:50:25Z")

</div>

Hi,  
I am running Windows Vista and Suse Linux under dual boot. After a failure, I used Paragon Hard Disk Manager to restore my disk. I re-initialized grep and booted the PC. Instead of the usual green Startup Options screen, I got the message “(HD0,7) boot message: file not found”. I was then thrown into a black and white screen that listed my boot options: Windows Vista, Suse Linux, and Failsafe. I successfully selected Windows, but when I tried to bring up Suse. I got the following series of messages –

root (HD0,7)  
File system type unknown, partition type 0x82  
Kernel boot/vmlinux oot /dev/disk/by-id/ata-ST31000528As\_iVP77IVT-part 8 repair-1 resume=dev/disk/by-id/ata-ST31000628AS\_IVP771VT-part 7 splash=silent showopts vga=0x310  
Error 17 cannot mount selected partition  
Press any key to continue.

I then ran Suse Repair System and got the green Startup Options screen. From there, I was able to select Linux successfully, but when I selected Windows, I got thrown back into the black and white boot screen and selecting Windows only caused the screen to be redisplayed.  
I have since restored from backup a second time and am at a point where I can boot into Windows from the black and white screen, but attempting Linux still brings the messages detailed above.  
I am wondering at this point if I should simply re-install Linux, but am concerned about whether it is necessary to format the Linux partitions first and whether Windows will be affected in any way.  
Thanks in advance,  
s660117

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [November 5, 2012, 8:24pm UTC](https://forums.suse.com/t/problems-with-linux-after-full-paragon-restore/23267/2 "2012-11-05T20:24:58Z")

</div>

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1  
[color=blue]

> root (HD0,7) File system type unknown, partition type 0x82[/color]

0x82 is a swap partition; you should not be having Grub point there for  
a main booting area, though it is something Grub may reference for  
resuming (from hibernate, aka suspend-to-disk) since that’s where the  
system is stored, room permitting. My guess is your menu.lst/grub.conf  
file is misconfigured to point to the wrong partition, perhaps because  
of what you did when you “re-initialized grep”.

Good luck.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v2.0.19 (GNU/Linux)  
Comment: Using GnuPG with Mozilla - [http://www.enigmail.net/](http://www.enigmail.net/)

iQIcBAEBAgAGBQJQmAR5AAoJEF+XTK08PnB5BSIP/A6nfuc0aF6BlSMYA9pbREkW  
PWeIH3x+vCn65J2QwceTdqX87SyQ/IBbS8TjuD5p0jJ3Uu61DixJncY0gwccLAaj  
fuTl6PVD19H+wAxwvw7Afup5+o0v6eHgcL4TmIxCvRqeT+XcHxLKvtWtnS2e7U/U  
QYX7SgmeWOD2daoPClS3At/RnblanPZnyv4Olr0QHtbPPfVAlpsfVmWv43T5tVeU  
J4RBTtMZu0ed096JyXS+fG/kAWokeMmXiBa8/C2CdeVcz4VZ8/ROPhmgZyFs6szC  
mezxwLhdXjzTr02ZgIV0v3lXuKBABWFj7+giXglxRS0vFeiwK7vjiw8lotSWLwWa  
cbNRLaJdlSvB56MUknrLvp9WQ0+31XlSJJklEl4zC2iRvRUfONdUA1axkic8VgJn  
/aVofrI0PgMZYx4jAziJHARrOa3are9v8qkwtmBF1wMcx3toBwn7da2fh4eXvrMM  
DAXKb0Hv8MAhssIl35GWoQIGqFTDMqnllA8sOK7px9J4G7+2syPavRgZZ76Hnx1Y  
Few6ofqCjrsqV6lDb5Zu2PEXDDm/t/00Hi2Nttkt3W0BRDPrc1q3GRHDDws34Ygj  
mIqHzEoZvJ4F9VBfvAPxP+D0gmq9Agij/c7VNO+Y7Rq4hQvR9a7HgW+0o0IYkicC  
S9xGdsTwTSKBRqwXUQKN  
=+p1I  
-----END PGP SIGNATURE-----

---

<div class="post-metadata">

**Author:** ![s660117](https://avatars.discourse-cdn.com/v4/letter/s/b19c9b/32.png) [@s660117](https://forums.suse.com/u/s660117)\
**Post date:** [November 5, 2012, 8:42pm UTC](https://forums.suse.com/t/problems-with-linux-after-full-paragon-restore/23267/3 "2012-11-05T20:42:23Z")

</div>

[QUOTE=ab;9931]-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA1  
[color=blue]

> root (HD0,7) File system type unknown, partition type 0x82[/color]

0x82 is a swap partition; you should not be having Grub point there for  
a main booting area, though it is something Grub may reference for  
resuming (from hibernate, aka suspend-to-disk) since that’s where the  
system is stored, room permitting. My guess is your menu.lst/grub.conf  
file is misconfigured to point to the wrong partition, perhaps because  
of what you did when you “re-initialized grep”.

Good luck.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v2.0.19 (GNU/Linux)  
Comment: Using GnuPG with Mozilla - [http://www.enigmail.net/](http://www.enigmail.net/)

iQIcBAEBAgAGBQJQmAR5AAoJEF+XTK08PnB5BSIP/A6nfuc0aF6BlSMYA9pbREkW  
PWeIH3x+vCn65J2QwceTdqX87SyQ/IBbS8TjuD5p0jJ3Uu61DixJncY0gwccLAaj  
fuTl6PVD19H+wAxwvw7Afup5+o0v6eHgcL4TmIxCvRqeT+XcHxLKvtWtnS2e7U/U  
QYX7SgmeWOD2daoPClS3At/RnblanPZnyv4Olr0QHtbPPfVAlpsfVmWv43T5tVeU  
J4RBTtMZu0ed096JyXS+fG/kAWokeMmXiBa8/C2CdeVcz4VZ8/ROPhmgZyFs6szC  
mezxwLhdXjzTr02ZgIV0v3lXuKBABWFj7+giXglxRS0vFeiwK7vjiw8lotSWLwWa  
cbNRLaJdlSvB56MUknrLvp9WQ0+31XlSJJklEl4zC2iRvRUfONdUA1axkic8VgJn  
/aVofrI0PgMZYx4jAziJHARrOa3are9v8qkwtmBF1wMcx3toBwn7da2fh4eXvrMM  
DAXKb0Hv8MAhssIl35GWoQIGqFTDMqnllA8sOK7px9J4G7+2syPavRgZZ76Hnx1Y  
Few6ofqCjrsqV6lDb5Zu2PEXDDm/t/00Hi2Nttkt3W0BRDPrc1q3GRHDDws34Ygj  
mIqHzEoZvJ4F9VBfvAPxP+D0gmq9Agij/c7VNO+Y7Rq4hQvR9a7HgW+0o0IYkicC  
S9xGdsTwTSKBRqwXUQKN  
=+p1I  
-----END PGP SIGNATURE-----[/QUOTE]

Ok… I redid grub and now get something very different. When I select Linux, I see a stream of messages which end with the following –

EXT3 FS on SDA8, internal journal.  
EXT3-fs: mounted filesystem with ordered data mode  
No init found. Try passing int=option to the kernal  
unmount: /dev/pts: device is busy  
(In some cases, useful info about processes that use the device is foud by lsof(8) or fuser(1))  
unmount: /dev: the device is busy  
Kernel panic - not synching attempted to kill init! that use

The boot then stops.  
s660117
