"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
I reported this to sysvinit because the symptoms are similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/118397
Please correct me if I'm wrong...
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.ne
Note that the screenshot was taken with a previous version of my fstab
in which I didn't use UUID's but /dev/sda1 etc. The symptoms are exactly
the same.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You
** Attachment added: "A screenshot of the prompt during boot"
http://launchpadlibrarian.net/11319008/screenshot%20fsck%20prompt.jpg
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You received this bug
Thank you for your bug report.
Can you attach the output of the following command, please?
sudo mount /dev/disk/by-uuid/b9682ea8-9076-4417-be3c-3240d9b57dac
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Checkfs fails on USB partition because initialization isn't finished y
Hi,
Thanks for your reaction. Mounting it doesn't give any output. As you
see in the log I had to unmount it first.
Cheers,
Aron
** Attachment added: "mount.txt"
http://launchpadlibrarian.net/14831339/mount.txt
--
Checkfs fails on USB partition because initialization isn't finished yet;
pr
Thank you for the information provided.
I've tried to reproduce this bug and I got the same result so I can confirm it.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
Checkfs fails on USB partition because initialization isn't finish
The script which mounts all the partitions listed in fstab is
/etc/init.d/mountall.sh, which is part of the package initscripts.
The reason why putting "sleep 5" in checkfs.sh works is because checkfs is
executed before mountall (according to /etc/rcS.d).
If you have some questions, just ask. :-)
Thanks for picking this up and explaining what causes it. I guess this is where
I wait until this is fixed and I can update my checkfs.sh to the default again?
:)
If you or any developer need any more info from me, just ask.
--
Checkfs fails on USB partition because initialization isn't finishe
"sleep 5" in checkfs.sh solves the problem, but I am curious that why not
executing S35mountall.sh earlier than S30checkfs.sh?
Will that solve the problem as well? Or that will cause another
problems?
Thanks for helps in advanced.
--
TL
--
Checkfs fails on USB partition because initialization
As a matter of fact I don't think the mountall script should be run
before checkfs. fsck will fail when run on a mounted volume. The problem
here is not that the volume isn't mounted, it's that the volume isn't
available yet as a device.
For me the solution has been to build the drive in the PC an
I just ran into this bug after installing Ubuntu Netbook Remix (9.04) on
my Eee PC 900A. I have an internal 4GB SDD that I mount as root (/) and
a 8GB SD card that I mount as /home.
Looks like there might be a way to trap the failure as fsck fails with
an 8. I'm going to experiment with catching 8
I should also add that my setup did not cause the same problem when
running Easy Peasy 1.0 (8.10 based). That booted just fine, no problems
with fsck.
--
Checkfs fails on USB partition because initialization isn't finished yet;
prompts on every boot
https://bugs.launchpad.net/bugs/182616
You rec
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
On Fri, 2009-05-08 at 06:31 +, Thomas Lee wrote:
> "sleep 5" in checkfs.sh solves the problem, but I am curious that why not
> executing S35mountall.sh earlier than S30checkfs.sh?
>
Err, because you can't check filesystems until you've mounted them?
Scott
--
Scott James Remnant
sc...@ubunt
78 matches
Mail list logo
