Re: failed to start remount root and kernel file system
Hi, I managed to install the sysvinit and purge the systemd, it works. Just for the records, Best regards, lina On Thu, Oct 16, 2014 at 9:09 PM, Darac Marjal mailingl...@darac.org.uk wrote: On Thu, Oct 16, 2014 at 08:58:37PM +0800, lina wrote: I installed the lvm and its dependencies, it shows /local-premount/lvm: not found problem persists ... Well, if you're not using LVM, then yes that won't apply. It wasn't possible to tell that from your fstab. Basically, the error you're getting is telling you that the initramfs can't find the disk with UUID=4c106bc2-cb98-4795-9cff-6da66d0da771. If you're able to use the break=premount option, then you can run blkid in the shell to see what block devices are available at that point. If the device with that UUID isn't in the list, then you'll need to look at your system to work out why not (has the device gone missing? has the UUID (which is a property of the file system) changed? has some subsystem (LVM in *my* case) not started?). On Thu, Oct 16, 2014 at 8:25 PM, lina lina.lastn...@gmail.com wrote: * Add break=premount to the end of your kernel commandline and boot At the grub stage, there is no reaction to the e or c I pressed. * If you have panic=something set, remove it. For some reason, those two options conflict and you won't get a shell, even though you explicitly asked for one * The initramfs will break out to a shell before any file systems are mounted. * At the shell run lvm vgchange -ay. This will make all your LVM LVs available * Press Ctrl+D to exit the shell and continue booting. * With the system now up (hopefully), create the following file as /etc/initramfs-tools/scripts/local-premount/lvm #!/bin/sh lvm vgchange -ay * Make the file executable (chmod +x ...) * Rebuild the initramfs with sudo update-initramfs -u Your system should now boot reliably. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able
Re: failed to start remount root and kernel file system
On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016085550.GD6116@tal
Fwd: failed to start remount root and kernel file system
On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cag9cjmk546cb+x4a2a8fklb39f7p-cupwkndmxksw0soc8w...@mail.gmail.com
Re: failed to start remount root and kernel file system
It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJmkymSri6BWfHkywAfstPYSY7jw3a=wjc+mjtfw20yb...@mail.gmail.com
Re: failed to start remount root and kernel file system
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048 I am still not clear about how to fix it. It is exactly like the problem mentioned in this bug. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJm=wbbkadygkng4yqs6quu32+ekubbf78fnfy-imbmp...@mail.gmail.com
Re: failed to start remount root and kernel file system
On Thu, Oct 16, 2014 at 05:54:26PM +0800, lina wrote: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048 I am still not clear about how to fix it. It is exactly like the problem mentioned in this bug. Ah, I ran into that problem myself the other day. My solution was: * Add break=premount to the end of your kernel commandline and boot * If you have panic=something set, remove it. For some reason, those two options conflict and you won't get a shell, even though you explicitly asked for one * The initramfs will break out to a shell before any file systems are mounted. * At the shell run lvm vgchange -ay. This will make all your LVM LVs available * Press Ctrl+D to exit the shell and continue booting. * With the system now up (hopefully), create the following file as /etc/initramfs-tools/scripts/local-premount/lvm #!/bin/sh lvm vgchange -ay * Make the file executable (chmod +x ...) * Rebuild the initramfs with sudo update-initramfs -u Your system should now boot reliably. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJm=wbbkadygkng4yqs6quu32+ekubbf78fnfy-imbmp...@mail.gmail.com signature.asc Description: Digital signature
[lina.lastn...@gmail.com: Re: failed to start remount root and kernel file system
Lina, could you post to the list only, please. I haven't dived into systemd issues -- so can't help you, hoping someone else can. I see you refer to a [1], but it is not there! :) - Forwarded message from lina lina.lastn...@gmail.com - Date: Thu, 16 Oct 2014 17:29:18 +0800 From: lina lina.lastn...@gmail.com To: Chris Bannister cbannis...@slingshot.co.nz Subject: Re: failed to start remount root and kernel file system On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. - End forwarded message - -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016110550.GC8648@tal
Re: failed to start remount root and kernel file system
* Add break=premount to the end of your kernel commandline and boot At the grub stage, there is no reaction to the e or c I pressed. * If you have panic=something set, remove it. For some reason, those two options conflict and you won't get a shell, even though you explicitly asked for one * The initramfs will break out to a shell before any file systems are mounted. * At the shell run lvm vgchange -ay. This will make all your LVM LVs available * Press Ctrl+D to exit the shell and continue booting. * With the system now up (hopefully), create the following file as /etc/initramfs-tools/scripts/local-premount/lvm #!/bin/sh lvm vgchange -ay * Make the file executable (chmod +x ...) * Rebuild the initramfs with sudo update-initramfs -u Your system should now boot reliably. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJm=wbbkadygkng4yqs6quu32+ekubbf78fnfy-imbmp...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJmk0MOkS7MwhfMbXxyFCEdpvOA5fEk70efDY=5_nte8...@mail.gmail.com
Re: failed to start remount root and kernel file system
I installed the lvm and its dependencies, it shows /local-premount/lvm: not found problem persists ... On Thu, Oct 16, 2014 at 8:25 PM, lina lina.lastn...@gmail.com wrote: * Add break=premount to the end of your kernel commandline and boot At the grub stage, there is no reaction to the e or c I pressed. * If you have panic=something set, remove it. For some reason, those two options conflict and you won't get a shell, even though you explicitly asked for one * The initramfs will break out to a shell before any file systems are mounted. * At the shell run lvm vgchange -ay. This will make all your LVM LVs available * Press Ctrl+D to exit the shell and continue booting. * With the system now up (hopefully), create the following file as /etc/initramfs-tools/scripts/local-premount/lvm #!/bin/sh lvm vgchange -ay * Make the file executable (chmod +x ...) * Rebuild the initramfs with sudo update-initramfs -u Your system should now boot reliably. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie for a long period. Yes, it is caused by the last update of the systemed and util-linux. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJm=wbbkadygkng4yqs6quu32+ekubbf78fnfy-imbmp...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAG9cJm=7ifppv0cr_xcy6bjood8dk_rgrdjo4b-o+mkcchy...@mail.gmail.com
Re: failed to start remount root and kernel file system
On Thu, Oct 16, 2014 at 08:58:37PM +0800, lina wrote: I installed the lvm and its dependencies, it shows /local-premount/lvm: not found problem persists ... Well, if you're not using LVM, then yes that won't apply. It wasn't possible to tell that from your fstab. Basically, the error you're getting is telling you that the initramfs can't find the disk with UUID=4c106bc2-cb98-4795-9cff-6da66d0da771. If you're able to use the break=premount option, then you can run blkid in the shell to see what block devices are available at that point. If the device with that UUID isn't in the list, then you'll need to look at your system to work out why not (has the device gone missing? has the UUID (which is a property of the file system) changed? has some subsystem (LVM in *my* case) not started?). On Thu, Oct 16, 2014 at 8:25 PM, lina lina.lastn...@gmail.com wrote: * Add break=premount to the end of your kernel commandline and boot At the grub stage, there is no reaction to the e or c I pressed. * If you have panic=something set, remove it. For some reason, those two options conflict and you won't get a shell, even though you explicitly asked for one * The initramfs will break out to a shell before any file systems are mounted. * At the shell run lvm vgchange -ay. This will make all your LVM LVs available * Press Ctrl+D to exit the shell and continue booting. * With the system now up (hopefully), create the following file as /etc/initramfs-tools/scripts/local-premount/lvm #!/bin/sh lvm vgchange -ay * Make the file executable (chmod +x ...) * Rebuild the initramfs with sudo update-initramfs -u Your system should now boot reliably. On Thu, Oct 16, 2014 at 5:47 PM, lina lina.lastn...@gmail.com wrote: It doesn't mount the /usr /var /tmp Timed out waiting for device dev-disk-by\x ... Dependency failed for /var On Thu, Oct 16, 2014 at 5:29 PM, lina lina.lastn...@gmail.com wrote: On Thu, Oct 16, 2014 at 4:55 PM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Thu, Oct 16, 2014 at 01:00:21PM +0800, lina wrote: Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Dunno. Is it an fstab issue? I'm only guessing here because you haven't given us much information. What is the actual error message? dove systemd[1]: /usr appears to be on its own filesystem and is not already mounted, this is not a supported setup. # /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 proc /proc proc defaults 0 0 # / was on /dev/sda5 during installation UUID=2a687c3c-ffb4-4577-9781-beb6b88eb71b / ext4 errors=remount-ro 0 1 # /backup was on /dev/sda14 during installation UUID=114ea034-62b3-4266-b80f-e8bd43c90bfe /mnt/backup ext4 defaults,noauto 0 2 # /boot was on /dev/sda4 during installation UUID=f38f09c1-8cc3-485f-8235-1b23fc26fcc9 /boot ext4 defaults 0 2 # /home was on /dev/sda7 during installation UUID=c826cf6e-a284-4741-a8e4-89b75991d801 /home ext4 defaults 0 2 # /scratch was on /dev/sda13 during installation UUID=25ad7887-39b1-4375-b9aa-0840cb84cb75 /scratch ext4 defaults 0 2 # /tmp was on /dev/sda8 during installation UUID=ba00a966-7352-4749-b478-788fea4f1a83 /tmp ext4 defaults 0 2 # /usr was on /dev/sda9 during installation UUID=49ce4cbd-7ac8-4b2d-84da-85143d214ee3 /usr ext4 defaults 0 2 # /usr/local was on /dev/sda10 during installation UUID=f013d06c-641d-4340-a620-9aeb3ce9a356 /usr/local ext4 defaults 0 2 # /var was on /dev/sda11 during installation UUID=4c106bc2-cb98-4795-9cff-6da66d0da771 /var ext4 defaults 0 2 # /var/local was on /dev/sda12 during installation UUID=97068b98-deae-4d79-baa1-0e3110aa18b6 /var/local ext4 defaults 0 2 # swap was on /dev/sda6 during installation UUID=0dc0ac69-7e3a-43d5-8582-aac085053f83 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 # mac was on /dev/sda2 /dev/sda2 /mnt/mac hfsplus ro,nouser,noauto,noexec 0 0 I haven't had to diagnose any systemd booting issues, yet, cause it hasn't failed. So have you any strange configurations --- do you need to mount anything over nfs, for example. Is this your laptop? Is it encrypted? laptop, no encrypted All these are just guesses, but hopefully someone will be able to help if they know the error messages etc. Oh, is this a new Jessie box, *OR*, have you been running Jessie for a while and the latest update caused this? I have been running Jessie
Re: [lina.lastn...@gmail.com: Re: failed to start remount root and kernel file system
On Vi, 17 oct 14, 00:05:50, Chris Bannister wrote: Lina, could you post to the list only, please. I haven't dived into systemd issues -- so can't help you, hoping someone else can. I see you refer to a [1], but it is not there! :) ... dove systemd[1]: /usr appears to be on its own filesystem and is not ^^ already mounted, this is not a supported setup. If you mean this [1] that is the PID number (because systemd can also run as a user instance). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: [lina.lastn...@gmail.com: Re: failed to start remount root and kernel file system
On Thu, Oct 16, 2014 at 09:13:47PM +0300, Andrei POPESCU wrote: On Vi, 17 oct 14, 00:05:50, Chris Bannister wrote: Lina, could you post to the list only, please. I haven't dived into systemd issues -- so can't help you, hoping someone else can. I see you refer to a [1], but it is not there! :) ... dove systemd[1]: /usr appears to be on its own filesystem and is not ^^ already mounted, this is not a supported setup. If you mean this [1] that is the PID number (because systemd can also run as a user instance). Ahhh! OK. Thanks for the clarification. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017015005.GB22902@tal
failed to start remount root and kernel file system
Any suggestions about failed to start remount root and kernel file system Is it due to updating issue? some package like systemd, or util-linux? Jessie box. Thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cag9cjmno8wkjhfh109vdbkx8jky7pwm2qaetsl+wotrzuc0...@mail.gmail.com
