| 2008-05-04 20:05:23 |
JP Vossen |
bug |
|
|
added bug |
| 2008-05-04 20:15:27 |
nglnx |
bug |
|
|
assigned to wubi |
| 2008-05-05 22:36:09 |
Agostino Russo |
wubi: status |
New |
Confirmed |
|
| 2008-05-05 22:36:09 |
Agostino Russo |
wubi: importance |
Undecided |
Low |
|
| 2008-05-05 22:47:53 |
Agostino Russo |
wubi: assignee |
|
ago |
|
| 2008-05-06 08:46:42 |
Agostino Russo |
bug |
|
|
added subscriber Evan Dandrea |
| 2008-05-06 22:26:09 |
Agostino Russo |
None: assignee |
|
ago |
|
| 2008-05-06 22:27:05 |
Agostino Russo |
bug |
|
|
assigned to lupin |
| 2008-05-06 22:27:30 |
Agostino Russo |
lupin: status |
New |
Confirmed |
|
| 2008-05-06 22:27:30 |
Agostino Russo |
lupin: assignee |
|
ago |
|
| 2008-05-06 22:27:30 |
Agostino Russo |
lupin: importance |
Undecided |
Low |
|
| 2008-05-06 22:27:44 |
Agostino Russo |
initramfs-tools: status |
New |
Confirmed |
|
| 2008-05-06 23:05:45 |
Agostino Russo |
bug |
|
|
added attachment 'initramfs-tools_0.85eubuntu37.debdiff' (initramfs-tools patch) |
| 2008-05-06 23:25:23 |
Agostino Russo |
wubi: status |
Confirmed |
Invalid |
|
| 2008-05-06 23:25:35 |
Agostino Russo |
lupin: status |
Confirmed |
Fix Committed |
|
| 2008-05-06 23:26:06 |
Agostino Russo |
initramfs-tools: status |
Confirmed |
In Progress |
|
| 2008-05-09 16:34:29 |
Evan |
bug |
|
|
added attachment 'lupin-ntfsdirty.diff' (lupin-ntfsdirty.diff) |
| 2008-05-09 17:45:17 |
Evan |
lupin: status |
Fix Committed |
Invalid |
|
| 2008-05-09 17:45:30 |
Evan |
bug |
|
|
assigned to lupin (Ubuntu) |
| 2008-05-09 17:45:43 |
Evan |
initramfs-tools: status |
In Progress |
Fix Committed |
|
| 2008-05-09 17:45:59 |
Evan |
initramfs-tools: importance |
Undecided |
Medium |
|
| 2008-05-09 17:45:59 |
Evan |
initramfs-tools: milestone |
|
ubuntu-8.04.1 |
|
| 2008-05-09 17:46:48 |
Evan |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2008-05-09 17:47:13 |
Evan |
initramfs-tools: status |
Fix Committed |
Confirmed |
|
| 2008-05-09 17:47:32 |
Evan |
lupin: importance |
Undecided |
Medium |
|
| 2008-05-09 17:47:32 |
Evan |
lupin: status |
New |
Fix Committed |
|
| 2008-05-09 17:47:32 |
Evan |
lupin: milestone |
|
ubuntu-8.04.1 |
|
| 2008-05-09 17:48:22 |
Evan |
lupin: status |
New |
Fix Committed |
|
| 2008-05-09 17:48:22 |
Evan |
lupin: milestone |
|
ubuntu-8.04.1 |
|
| 2008-05-09 17:50:40 |
Evan |
description |
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
While it kind of gives clues if you think about it and don't panic, it's not all that relevant. It's also not even there if you are booting in the default quiet/splash screen mode (I understand the reasons for that default, but I think it's a bad idea as it masks stuff like this).
Possible Solutions
1) Insert some kind of shim program at some earlier point in the boot process (if possible) that detects the NTFS dirty flag (see http://www.google.com/search?q=ntfs+%22dirty+flag%22) and bounce out the of the quiet/splash screen to provide a *useful and non-scary* error message.
2) Edit the text of the error already provided (shown above) to be more useful and less scary. This solution is less ideal because it still requires the user not to panic, to reboot, and to think of hitting ESC and choosing recovery mode before getting help. Solution 1 or something that Just Does The Right Thing is preferred.
Possible text for the error message:
----- cut here -----
Ubuntu can't boot because the Windows NTFS file-system's "dirty flag" is set. That usually means the Windows either crashed or failed to start completely. (You didn't turn Windows off in the middle of starting up or shutting down, did you?)
To fix this, simply reboot into Windows, let it fully start, log in, ideally run a "Check Disk" (see http://support.microsoft.com/kb/315265), then gracefully shut down. Once you restart, Ubuntu should be able to use the NTFS partition and boot normally.
----- cut here -----
See also:
https://bugs.launchpad.net/ubuntu/+source/qtparted/+bug/57580 |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty. The first patch addresses this in lupin, and thus only affects Wubi users:
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
While it kind of gives clues if you think about it and don't panic, it's not all that relevant. It's also not even there if you are booting in the default quiet/splash screen mode (I understand the reasons for that default, but I think it's a bad idea as it masks stuff like this).
Possible Solutions
1) Insert some kind of shim program at some earlier point in the boot process (if possible) that detects the NTFS dirty flag (see http://www.google.com/search?q=ntfs+%22dirty+flag%22) and bounce out the of the quiet/splash screen to provide a *useful and non-scary* error message.
2) Edit the text of the error already provided (shown above) to be more useful and less scary. This solution is less ideal because it still requires the user not to panic, to reboot, and to think of hitting ESC and choosing recovery mode before getting help. Solution 1 or something that Just Does The Right Thing is preferred.
Possible text for the error message:
----- cut here -----
Ubuntu can't boot because the Windows NTFS file-system's "dirty flag" is set. That usually means the Windows either crashed or failed to start completely. (You didn't turn Windows off in the middle of starting up or shutting down, did you?)
To fix this, simply reboot into Windows, let it fully start, log in, ideally run a "Check Disk" (see http://support.microsoft.com/kb/315265), then gracefully shut down. Once you restart, Ubuntu should be able to use the NTFS partition and boot normally.
----- cut here -----
See also:
https://bugs.launchpad.net/ubuntu/+source/qtparted/+bug/57580 |
|
| 2008-05-09 17:51:07 |
Evan |
description |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty. The first patch addresses this in lupin, and thus only affects Wubi users:
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
While it kind of gives clues if you think about it and don't panic, it's not all that relevant. It's also not even there if you are booting in the default quiet/splash screen mode (I understand the reasons for that default, but I think it's a bad idea as it masks stuff like this).
Possible Solutions
1) Insert some kind of shim program at some earlier point in the boot process (if possible) that detects the NTFS dirty flag (see http://www.google.com/search?q=ntfs+%22dirty+flag%22) and bounce out the of the quiet/splash screen to provide a *useful and non-scary* error message.
2) Edit the text of the error already provided (shown above) to be more useful and less scary. This solution is less ideal because it still requires the user not to panic, to reboot, and to think of hitting ESC and choosing recovery mode before getting help. Solution 1 or something that Just Does The Right Thing is preferred.
Possible text for the error message:
----- cut here -----
Ubuntu can't boot because the Windows NTFS file-system's "dirty flag" is set. That usually means the Windows either crashed or failed to start completely. (You didn't turn Windows off in the middle of starting up or shutting down, did you?)
To fix this, simply reboot into Windows, let it fully start, log in, ideally run a "Check Disk" (see http://support.microsoft.com/kb/315265), then gracefully shut down. Once you restart, Ubuntu should be able to use the NTFS partition and boot normally.
----- cut here -----
See also:
https://bugs.launchpad.net/ubuntu/+source/qtparted/+bug/57580 |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty. The first patch addresses this in lupin, and thus only affects Wubi users:
http://launchpadlibrarian.net/14400134/lupin-ntfsdirty.diff
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
While it kind of gives clues if you think about it and don't panic, it's not all that relevant. It's also not even there if you are booting in the default quiet/splash screen mode (I understand the reasons for that default, but I think it's a bad idea as it masks stuff like this).
Possible Solutions
1) Insert some kind of shim program at some earlier point in the boot process (if possible) that detects the NTFS dirty flag (see http://www.google.com/search?q=ntfs+%22dirty+flag%22) and bounce out the of the quiet/splash screen to provide a *useful and non-scary* error message.
2) Edit the text of the error already provided (shown above) to be more useful and less scary. This solution is less ideal because it still requires the user not to panic, to reboot, and to think of hitting ESC and choosing recovery mode before getting help. Solution 1 or something that Just Does The Right Thing is preferred.
Possible text for the error message:
----- cut here -----
Ubuntu can't boot because the Windows NTFS file-system's "dirty flag" is set. That usually means the Windows either crashed or failed to start completely. (You didn't turn Windows off in the middle of starting up or shutting down, did you?)
To fix this, simply reboot into Windows, let it fully start, log in, ideally run a "Check Disk" (see http://support.microsoft.com/kb/315265), then gracefully shut down. Once you restart, Ubuntu should be able to use the NTFS partition and boot normally.
----- cut here -----
See also:
https://bugs.launchpad.net/ubuntu/+source/qtparted/+bug/57580 |
|
| 2008-05-09 18:00:11 |
Launchpad Janitor |
lupin: status |
Fix Committed |
Fix Released |
|
| 2008-05-09 22:31:33 |
Steve Langasek |
lupin: milestone |
ubuntu-8.04.1 |
|
|
| 2008-05-09 22:32:45 |
Steve Langasek |
initramfs-tools: milestone |
ubuntu-8.04.1 |
|
|
| 2008-05-09 22:34:39 |
Steve Langasek |
initramfs-tools: milestone |
|
ubuntu-8.04.1 |
|
| 2008-05-27 06:36:31 |
Agostino Russo |
bug |
|
|
added attachment 'initramfs-tools_0.85eubuntu37.debdiff' (initramfs-tools_0.85eubuntu37.debdiff) |
| 2008-05-27 17:05:07 |
Launchpad Janitor |
initramfs-tools: status |
Confirmed |
Fix Released |
|
| 2008-05-29 15:05:26 |
Evan |
bug |
|
|
added attachment 'lupin_0.16-0.19.debdiff' (lupin_0.16-0.19.debdiff) |
| 2008-05-29 15:06:54 |
Evan |
description |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty. The first patch addresses this in lupin, and thus only affects Wubi users:
http://launchpadlibrarian.net/14400134/lupin-ntfsdirty.diff
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
While it kind of gives clues if you think about it and don't panic, it's not all that relevant. It's also not even there if you are booting in the default quiet/splash screen mode (I understand the reasons for that default, but I think it's a bad idea as it masks stuff like this).
Possible Solutions
1) Insert some kind of shim program at some earlier point in the boot process (if possible) that detects the NTFS dirty flag (see http://www.google.com/search?q=ntfs+%22dirty+flag%22) and bounce out the of the quiet/splash screen to provide a *useful and non-scary* error message.
2) Edit the text of the error already provided (shown above) to be more useful and less scary. This solution is less ideal because it still requires the user not to panic, to reboot, and to think of hitting ESC and choosing recovery mode before getting help. Solution 1 or something that Just Does The Right Thing is preferred.
Possible text for the error message:
----- cut here -----
Ubuntu can't boot because the Windows NTFS file-system's "dirty flag" is set. That usually means the Windows either crashed or failed to start completely. (You didn't turn Windows off in the middle of starting up or shutting down, did you?)
To fix this, simply reboot into Windows, let it fully start, log in, ideally run a "Check Disk" (see http://support.microsoft.com/kb/315265), then gracefully shut down. Once you restart, Ubuntu should be able to use the NTFS partition and boot normally.
----- cut here -----
See also:
https://bugs.launchpad.net/ubuntu/+source/qtparted/+bug/57580 |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here ----- |
|
| 2008-05-29 15:11:38 |
Evan |
description |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here ----- |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
A debdiff of the entire 0.19 upload, including the fix for bug 136682, can be found here:
http://launchpadlibrarian.net/14795586/lupin_0.16-0.19.debdiff |
|
| 2008-05-29 15:17:01 |
Evan |
bug |
|
|
added attachment 'initramfstools_0.85eubuntu36-0.85eubuntu38.debdiff' (initramfstools_0.85eubuntu36-0.85eubuntu38.debdiff) |
| 2008-05-29 15:17:53 |
Evan |
description |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
A debdiff of the entire 0.19 upload, including the fix for bug 136682, can be found here:
http://launchpadlibrarian.net/14795586/lupin_0.16-0.19.debdiff |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
A debdiff of the entire 0.19 upload, including the fix for bug 136682, can be found here:
http://launchpadlibrarian.net/14795586/lupin_0.16-0.19.debdiff
A debdiff of the initramfs-tools changes can be found here:
http://launchpadlibrarian.net/14795732/initramfstools_0.85eubuntu36-0.85eubuntu38.debdiff |
|
| 2008-05-29 15:18:35 |
Evan |
initramfs-tools: status |
New |
Fix Committed |
|
| 2008-05-29 15:25:27 |
Evan |
bug |
|
|
added attachment 'lupin-226622.debdiff' (lupin-226622.debdiff) |
| 2008-05-29 15:26:12 |
Evan |
description |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
A debdiff of the entire 0.19 upload, including the fix for bug 136682, can be found here:
http://launchpadlibrarian.net/14795586/lupin_0.16-0.19.debdiff
A debdiff of the initramfs-tools changes can be found here:
http://launchpadlibrarian.net/14795732/initramfstools_0.85eubuntu36-0.85eubuntu38.debdiff |
There has been much confusion surrounding the user getting dropped in the initramfs shell when the host filesystem cannot be mounted because it is dirty.
TEST CASE:
When using Ubuntu (Hardy) under wubi, if the NTFS dirty flag is set, the error message is missing or confusing.
This situation can and will occur when you restart and are not paying attention, so you miss the NT Boot loader prompt and start booting Windows, then hard-power-off to save time (can you guess how I know this?), or if/when Windows crashes. I bet this is going to be a really F.A.Q. with Wubi.
To reproduce:
1) Either shut Windows down ungracefully, or let it start half-way up, then hard-power-off to kill it
2) Reboot and attempt to go into Ubuntu
Case 1: default startup: You end up at a completely useless and scary BusyBox/(initramfs) prompt with no indication why you are there or what to do about it.
Case 2: recovery mode (verbose) startup: You still end up at a completely useless and scary BusyBox/(initramfs) prompt, but there are log lines on the screen as follows. But they are scary and confusing ("mount: ... failed: Success"? WTH?):
----- cut here (very top of my screen) -----
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda2/: Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.
Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:
mount -t ntfs-3g /dev/sda2 /root -o force
Or add the option to the relevant row in the /etc/fstab file:
/dev/sdc1 /mnt/external/ ntfs-3g defaults,force 0 0
mount: Mounting /dev/disk/by_uuid/... on /root failed: Success
mount: Mounting /root on /host failed: invalid argument
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 ... (ash)
Enter 'help' ....
(initramfs)
----- cut here -----
A diff of the required changes can be found here:
http://launchpadlibrarian.net/14795872/lupin-226622.debdiff
A debdiff of the entire 0.19 upload, including the fix for bug 136682, can be found here:
http://launchpadlibrarian.net/14795586/lupin_0.16-0.19.debdiff
A debdiff of the initramfs-tools changes can be found here:
http://launchpadlibrarian.net/14795732/initramfstools_0.85eubuntu36-0.85eubuntu38.debdiff |
|
| 2008-06-14 08:07:00 |
Agostino Russo |
lupin: status |
Fix Committed |
In Progress |
|
| 2008-06-14 08:07:17 |
Agostino Russo |
lupin: status |
Fix Released |
In Progress |
|
| 2008-06-16 09:47:16 |
Martin Pitt |
initramfs-tools: status |
Fix Committed |
Fix Released |
|
| 2008-06-16 10:36:18 |
Martin Pitt |
lupin: status |
In Progress |
Fix Committed |
|
| 2008-06-26 16:38:17 |
Agostino Russo |
lupin: status |
In Progress |
Fix Released |
|
| 2008-06-30 20:45:45 |
Steve Langasek |
lupin: status |
Fix Committed |
Fix Released |
|
| 2009-07-03 15:25:22 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/lupin |
|
| 2009-12-05 06:48:20 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/initramfs-tools |
|
| 2009-12-05 06:54:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-proposed/initramfs-tools |
|
| 2012-04-28 01:48:16 |
Gary M |
bug |
|
|
added subscriber Gary M |
| 2013-09-01 20:51:09 |
Evan |
removed subscriber Evan Dandrea |
|
|
|
