# Boot problem after Restore **URL:** \ **Category:** SLES Install-Boot\ **Created:** [December 23, 2013, 12:35pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918 "2013-12-23T12:35:33Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 23, 2013, 12:35pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/1 "2013-12-23T12:35:33Z")
Hello, I made a Backup via DriveSnapshot of my SLES 2011 and wanted to Restore it. The Restore worked quite fine, but when I want to boot, I get the following errors: > [@](#): > > fskc failed for at least one filesystem (not /). > Please repair manually and reboot > The root file system is already mointed read-write. > attention: only control-D will reboot the system in this > maintenance mode. shutdown or reboot will not worl > give root password for maintenance Then i type in root-password and it says > [@](#): > > (repair filesystem) # I have to say that I am beginner working with SLES 2011. The restore was on different hardware. You have any ideas to help me? thank you very much. ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [December 23, 2013, 2:53pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/2 "2013-12-23T14:53:44Z")
On 23/12/2013 10:44, stefan 1304 wrote: [color=blue] > I made a Backup via DriveSnapshot of my SLES 2011 and wanted to Restore > it. > The Restore worked quite fine, but when I want to boot, I get the > following errors: > [color=green] > > > fskc failed for at least one filesystem (not /). > > Please repair manually and reboot > > The root file system is already mointed read-write. > > attention: only control-D will reboot the system in this > > maintenance mode. shutdown or reboot will not worl > > give root password for maintenance > > [/color] > > Then i type in root-password and it says > [color=green] > > > (repair filesystem) # > > [/color] > > I have to say that I am beginner working with SLES 2011. The restore was > on different hardware. > You have any ideas to help me? thank you very much.[/color] Since there is no SLES version 2011 what do you mean by “SLES 2011”? Perhaps you mean SLES 11? Please post the output from “cat /etc/\*release” so we can see which version and Service Pack (if any) you’re using. ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks. ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 23, 2013, 3:24pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/3 "2013-12-23T15:24:15Z")
Hello, at the moment I do a restore again. Think I made something wrong when I tried to use system repair option with install DVD. Yes, it is Version 11, sorry. I will give you the output on Friday. Thank you so far. ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 23, 2013, 3:59pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/4 "2013-12-23T15:59:39Z")
Hi Stefan(\_1304), I you still run into that message, check the lines above where the output from fsck is listed, to identify which file system(s) are affected. To manually repair those, run "fsck -f " and if I may recommend so, run it again until fsck reports it has nothing to fix. Also, I’d run that on any other file system at least once. Was the image created on a _running_ system? Then chances are high you won’t have too much trouble after repairing. If the image was taken from a shut-down system, it’d be interesting why there are such problems. Regards, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 23, 2013, 4:40pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/5 "2013-12-23T16:40:12Z")
Hi Jens, it was an offline image via DriveSnapshot. [http://www.drivesnapshot.de/](http://www.drivesnapshot.de/) ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 23, 2013, 4:53pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/6 "2013-12-23T16:53:04Z")
when I ran fsck -f several times, I geht erros like this: > [@](#): > > fsck.ext3: no such file or directory while trying to pen /dev/disk/…-partX > the superblock could not be read or does not describe correct ext2 filesystem > it the device is ready and it really contains an ext2 filesystem… I restored a correct running system and do not know why there are errors. the only changes are the different hardware. when I try df -ah, i only get /dev/mapper/system-root\_lv when I try fdisk -l, I can see all the partitions correct… ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 23, 2013, 5:15pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/7 "2013-12-23T17:15:17Z")
Hi Stefan, [QUOTE=stefan\_1304;18234]when I ran fsck -f several times, I geht erros like this: I restored a correct running system and do not know why there are errors. the only changes are the different hardware. when I try df -ah, i only get /dev/mapper/system-root\_lv when I try fdisk -l, I can see all the partitions correct…[/QUOTE] you seem to be running your system with logical volume management (LVM) - if you look at the /etc/fstab entries, are the partitions in question really mounted via partitions, or via (/dev/mapper/system-\*)LVM devices? If in doubt, please post the entries from /etc/fstab here. Unless these are via i.e. “LABEL=somelabel” in column one, you should run fsck against the device entry listed in that first column. If you’re totally confused by all this, it’d be helpful to also paste (in [CODE] blocks) the output of - fdisk -l - vgscan -v - vgdisplay system (and for any other VG found via vgscan) - ls -l /dev/mapper - cat /etc/fstab plus the info which file system you’re trying to repair. Regards, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 23, 2013, 8:23pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/8 "2013-12-23T20:23:02Z")
Thanks. I will answer everything on friday Merry xmas 🙂 [QUOTE=jmozdzen;18235]Hi Stefan, you seem to be running your system with logical volume management (LVM) - if you look at the /etc/fstab entries, are the partitions in question really mounted via partitions, or via (/dev/mapper/system-\*)LVM devices? If in doubt, please post the entries from /etc/fstab here. Unless these are via i.e. “LABEL=somelabel” in column one, you should run fsck against the device entry listed in that first column. If you’re totally confused by all this, it’d be helpful to also paste (in [CODE] blocks) the output of - fdisk -l - vgscan -v - vgdisplay system (and for any other VG found via vgscan) - ls -l /dev/mapper - cat /etc/fstab plus the info which file system you’re trying to repair. Regards, Jens[/QUOTE] ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 23, 2013, 10:15pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/9 "2013-12-23T22:15:11Z")
Hi Stefan, [QUOTE=stefan\_1304;18239]Thanks. I will answer everything on friday Merry xmas :)[/QUOTE] happy holidays to you (and anyone else reading this thread, too)! I may be online only a few moments until early January, so please don’t feel forgotten if I won’t be responding immediately 🙂 Regards, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 27, 2013, 10:14am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/10 "2013-12-27T10:14:10Z")
So hello again, I hope I can help you with the information. Because it would be much to type in, I hope sp, that photos are quite ok too. thank you. - /etc/fstab entries [http://s14.directupload.net/file/d/3484/clbarsng\_jpg.htm](http://s14.directupload.net/file/d/3484/clbarsng_jpg.htm) - fdisk -l [http://s1.directupload.net/file/d/3484/tnndnaev\_jpg.htm](http://s1.directupload.net/file/d/3484/tnndnaev_jpg.htm) - vgscan -v [http://s7.directupload.net/file/d/3484/z3mktszx\_jpg.htm](http://s7.directupload.net/file/d/3484/z3mktszx_jpg.htm) - vgdisplay system [http://s1.directupload.net/file/d/3484/qvtefmv6\_jpg.htm](http://s1.directupload.net/file/d/3484/qvtefmv6_jpg.htm) ls -l /dev/mapper [http://s14.directupload.net/file/d/3484/gdtql9t9\_jpg.htm](http://s14.directupload.net/file/d/3484/gdtql9t9_jpg.htm) cat /etc/fstab [http://s14.directupload.net/file/d/3484/6wtgpw36\_jpg.htm](http://s14.directupload.net/file/d/3484/6wtgpw36_jpg.htm) [QUOTE=jmozdzen;18235]Hi Stefan, you seem to be running your system with logical volume management (LVM) - if you look at the /etc/fstab entries, are the partitions in question really mounted via partitions, or via (/dev/mapper/system-\*)LVM devices? If in doubt, please post the entries from /etc/fstab here. Unless these are via i.e. “LABEL=somelabel” in column one, you should run fsck against the device entry listed in that first column. If you’re totally confused by all this, it’d be helpful to also paste (in [CODE] blocks) the output of - fdisk -l - vgscan -v - vgdisplay system (and for any other VG found via vgscan) - ls -l /dev/mapper - cat /etc/fstab plus the info which file system you’re trying to repair. Regards, Jens[/QUOTE] ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 27, 2013, 11:37am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/11 "2013-12-27T11:37:48Z")
and when I try fsck: [http://s1.directupload.net/file/d/3484/yhtmvljd\_jpg.htm](http://s1.directupload.net/file/d/3484/yhtmvljd_jpg.htm) ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 27, 2013, 11:48am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/12 "2013-12-27T11:48:52Z")
I tried every task you wrote on the server from which I made backup and the output ist the same like on the server I restored. live system is running, restored server is not running. hope you can help. thank you very much. ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 28, 2013, 1:14am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/13 "2013-12-28T01:14:45Z")
Hi Stefan, the trouble is that your partitions are referenced by disk id in fstab - as the new server has a different physical disk, its disk id is different, too. Use an editor of your choice (i.e. “vi”) to change the “/dev/disk/by-id/scsi-3600…-partX” device entries in /etc/fstab of the restored system to “/dev/sdaX” (i.e. to “/dev/sda5 /hana/shared ext3 acl,user…”). Of course, you may as well change the entry to the id of the current SCSI disk (see “ls -l /dev/disk/by-id” on the new server). You may want to manually run “fdisk -f /dev/sda1” (5,6,7,8,9), until no more errors are reported, before rebooting the server. Regards, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 28, 2013, 11:02am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/14 "2013-12-28T11:02:25Z")
Hi Jens, thanks for your excellent answer. that sounds fine. The disks of the new server are others. When I understand it right, it is enough when it says in the fstab where every partition is mapped? For example: /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /hana/shared ext3 /dev/sda6 … /dev/sda7 … /dev/sda8 … /dev/sda9 I can delete the information in the fstab with SCSI disk ID and so on because I does not need it there? ist that correct? thank you very much. king regards. Stefan [QUOTE=jmozdzen;18281]Hi Stefan, the trouble is that your partitions are referenced by disk id in fstab - as the new server has a different physical disk, its disk id is different, too. Use an editor of your choice (i.e. “vi”) to change the “/dev/disk/by-id/scsi-3600…-partX” device entries in /etc/fstab of the restored system to “/dev/sdaX” (i.e. to “/dev/sda5 /hana/shared ext3 acl,user…”). Of course, you may as well change the entry to the id of the current SCSI disk (see “ls -l /dev/disk/by-id” on the new server). You may want to manually run “fdisk -f /dev/sda1” (5,6,7,8,9), until no more errors are reported, before rebooting the server. Regards, Jens[/QUOTE] ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 28, 2013, 11:06am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/15 "2013-12-28T11:06:44Z")
Or I will do ls -l /dev/disk/by-id, there I can have a look which are the correct entrys for SCSI and put them instead of the wrong entrys in fstab? this way would be faster? ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 28, 2013, 1:03pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/16 "2013-12-28T13:03:31Z")
Hi Stefan, [QUOTE=stefan\_1304;18284]Or I will do ls -l /dev/disk/by-id, there I can have a look which are the correct entrys for SCSI and put them instead of the wrong entrys in fstab? this way would be faster?[/QUOTE] unlike in your other response, you here state correctly that you need to _replace_ the entries with the correct values. Your disk device(s) (and partitions, too) can be referenced by different names in Linux. I.e., for decades the typical name would have been /dev/sda for your first SCSI disk (/dev/sda1 being the first partition on that disk), but what if you have more than one disk? They’d be sda, sdb and so on, but in which _order_? Therefore, additional names were added, like “use disk ID”, “use device location on system bus”, “use file system label” and so on. In your case, the partitions to mount are referenced by device id plus partition number. As the device ID has changed, you’ll either need to adjust that to the correct new value or use some other reference (hence my earlier suggestion to use /dev/sda\*, as your server currently has only a single disk, no question on who’s who will come up… and it’s easier to type for you 😃 ) You may not _delete_ the entries in /etc/fstab, but need to _correct_ them. These entries tell the system which file systems on which device (partition) to mount. Regards, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 30, 2013, 10:03am UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/17 "2013-12-30T10:03:39Z")
Hi Jens, this moment I tested the changes in fstab and it seems to be good. I changed for every entry the scsi ID. When I set df -ah I see everything correct. Another problem is that I do not have any GUI after starting. I tried to do startx and it does not work. When I try it said > [@](#): > > fatals server error: > no screens found is it a wrong command or are there any other commands left to have GUI? So far thank you so much for solving the first error. King regards. Stefan [QUOTE=jmozdzen;18285]Hi Stefan, unlike in your other response, you here state correctly that you need to _replace_ the entries with the correct values. Your disk device(s) (and partitions, too) can be referenced by different names in Linux. I.e., for decades the typical name would have been /dev/sda for your first SCSI disk (/dev/sda1 being the first partition on that disk), but what if you have more than one disk? They’d be sda, sdb and so on, but in which _order_? Therefore, additional names were added, like “use disk ID”, “use device location on system bus”, “use file system label” and so on. In your case, the partitions to mount are referenced by device id plus partition number. As the device ID has changed, you’ll either need to adjust that to the correct new value or use some other reference (hence my earlier suggestion to use /dev/sda\*, as your server currently has only a single disk, no question on who’s who will come up… and it’s easier to type for you 😃 ) You may not _delete_ the entries in /etc/fstab, but need to _correct_ them. These entries tell the system which file systems on which device (partition) to mount. Regards, Jens[/QUOTE] ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [December 30, 2013, 12:54pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/18 "2013-12-30T12:54:42Z")
GUI is now working too. I tried with this commands: > [@](#): > > Sudo /usr/sbin/sax2 –ra > su (to become root) > sax2 -r (reprobe your video card) > startx > init 5 ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [December 30, 2013, 5:48pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/19 "2013-12-30T17:48:52Z")
Hi Stefan, sounds like you got this up&running yourself - it most probably had to do with a change in video hardware. If any problems remain, please open a new thread for those, to keep threads focused on a single problem 🙂 If your machine is up&running now, they Hey! You made it a problem of 2013 - 2014 may now come! A happy new year to you all, Jens ---
**Author:** ![stefan\_1304](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefan\_1304](https://forums.suse.com/u/stefan_1304)\ **Post date:** [January 13, 2014, 3:55pm UTC](https://forums.suse.com/t/boot-problem-after-restore/24918/20 "2014-01-13T15:55:59Z")
Sorry, that I am writing again. I tried to restore the server once again on the same hardware, but it does not work again. I do not have the screen with > [@](#): > > (repair filesystem) # when I start normal, there I have: > [@](#): > > Reading all physical volumes, this may take a while… > no volume group found > volume group “system” not found > volume group “system” not found > could not find /dev/system/root\_lv. > want me to fail back to /dev/system/root\_lv? (Y/n) it does not matter if I choose yes or no, the screen comes again the next boot. I tried to do automatic repaid with the installation DVD with no success. When I boot with installation DVD and choose rescue mode, I can logon with user root. rescue login: root when I execute fdisk -l I can see every partition. file \etc\fstab is empty and when I fill it with the correct partitions the system do not seems to remember it. and when I look in /dev there is no folder called system. is there any way where I do not have problems like this when I restore SLES 11 on another HW? can anyone help? thank you. [Next page](https://forums.suse.com/t/boot-problem-after-restore/24918.md?page=2)