I have a similiar problem here on Ubuntu Karmic Beta:
- Athlon 64 with ASRock N68PV-GS Mainboard and nForce 630 Chipset
- 2 SATA (no raid)
- sda1: root
- sdb1: my data
When trying to boot Ubuntu Karmic, after a few seconds it drops to a
BusyBox shell with the message:
"Gave up waiting for roo
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under the
No updates for 5 months and the last post said this issue was gone since
Intrepid. So close it.
-Bryan
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notif
Reinstalled 2.6.27-7 from a 8.10 LiveCD I burned oct 29.
Worked smoothly and system started from HDD after that.
Then repeated "dangerous things":
1) install NVIDIA v177 driver: rebooted ok.
2) upgrade to 2.6.27-9 by accepting all 158 updates available is next up:
rebooted ok.
I'm 100% clueless t
Tested all the boot options suggested here and in related bugs (have a link
list in bug #305714); nothing helps.
Tested (almost) all BIOS settings and physical connectors; nothing helps.
When the kernel boot from grub, it stops waiting for the disk after what looks
like a healthy "pre-boot". Sinc
>From what I understand, I have the same problem. I added bug #305714 which may
>be a duplicate of this one.
I have tried more or less all the different boot options suggested. I have two
perhaps interesting details regarding this problem:
1) my system worked for two weeks before failing to find
>From what I understand, I have the same problem. I added bug #305714 which may
>be a duplicate of this one.
I have tried more or less all the different boot options suggested. I have two
perhaps interesting details regarding this problem:
1) my system worked for two weeks before failing to find
@Kissell, it sounds like you have something more similar to bug 290153.
Does the workaround mentioned there (using the rootdelay boot option)
work for you?
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because
Sorry, but I still don't think it's exactly the same as in #294123. I did
exactly what you proposed, with waiting for the drives up to 5 minutes, but
they never showed up, no output in dmesg, no device nodes under /dev...
However, booting with the all_generic_ide option works, but disk access see
It's probably the same bug. You can start your system if you wait in the
busybox for sata drives to be loaded (check dmesg from time to time) and
then write "exit", hit enter and the system will start. I use main that
way actually. Today's update to the kernel didn't help.
--
root filesystem fail
(of course I meant "mine" not "main", sorry for my English)
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ub
Definitely - I am having a similar problem on the 2.6.27-7-generic kernel,
whereas the 2.6.24-19-generic works fine.
The details are in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294123
It doesn't seem to be quite the same, though, so I think it wouldn't be
fair to mark one or the ot
1) http://ubuntuforums.org/showthread.php?t=968424 - here is a thread on
ubuntuforums.org about it
2) people get the error even if they reinstall
3) only SATA drives are causing the problem
4) one person reported that plugging in SATA drives to all SATA slots resolved
the problem
The problem is s
okay, i had several things to blame when this problem occured... I was
assuming it was related to the SATA RAID array, because when I unplug
that array it boots just fine. But, the actual error gives a UUID of
the IDE disk in my system. The UUID is correct for the boot partition,
/boot/grub/menu
I've just upgraded from 8.04 to 8.10 and know I have this problem. My
computer is Athlon X2, nforce (don't know which version). I'll try to
boot using older kernel, but it looks like I might have to reinstall the
system. :(
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs
I've just upgraded from hardy to 8.10 via the dist-upgrade and received
this problem.
I unplugged all hard disks I didn't need and then tried to install 8.10
from CD, that worked just fine... except, the whole point of the
machine is the RAID file share, so I plugged the drives back in, and it
ha
well, if i wait long enough at the intramfs screen i can type return or
exit and that seems to kick me into gdm, and then everything works as i
need it to... except, i still don't have mdadm recognizing the drives.
fdisk -l shows all the drives, but mdadm won't assemble the array, even
manually.
I seem to have similar problems please check out.
https://bugs.launchpad.net/ubuntu/+bug/284774
I am using kubuntu 8.10
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs,
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Thanks, Michael (and Bernd). Confirming that adding "large-memory" to
lilo.conf does resolve the issue for me.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Bernd, Dwayne,
yours seems to be a different bug:
https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/221664
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a di
Hi,
I believe I am having a similar problem, although I do not have RAID on
my system. Booting my custom built 2.6.22 works fine, but booting the
current kernel (2.6.24-16 I believe) results in a shell and being told
that the disk cannot be mounted because the device or resource is busy.
I have pu
Hello Dwayne,
I also had to read Denis' posting several times - it was a bit confusing
to read. But I think not the size of initramfs is important, but the
size of the kernel. Well, 2.6.24-15-generic is still well below the 3MB
limit of Denis' findings, but 2.6.24 is definitely larger than 2.6.2
Hello Dwayne,
you are not alone, I run into the initramfs problem as well. Just a
question, are you by any chace using lilo (as I do)? Just asking due to
this http://lkml.org/lkml/2006/9/24/50
Cheers,
Bernd
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/
Thanks for the link, Bernd.
Yes, I am running lilo.
It is worth noting that the file I've been using since building my
kernel (shows up as 2.6.24.3) is actually quite large. It probably
shouldn't be, but even the 2.6.22 files are over 8 megabytes:
-rw-r--r-- 1 root root 8564557 2008-04-18 00:5
I compiled a custom 2.6.24 kernel to get around the "bad gzip magic
numbers" problem I was having. Unfortunately, I still can not use 3d
acceleration or sound with this new compiled kernel - I guess I'll be
watching for 2.6.24-17 generic. Hardy releases in 3-days ... really?
I am leaving this th
In my test, 2.6.22 was re-created fine.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Thanks for the suggestion. "pci=nomsi" does not work for me. I am
going to try generating a new 2.6.22 image to see if that works (I don't
think I have created a 2.6.22 since the move to hardy) - this should
tell me whether the problem is in creating the images or if the problem
is in loading the
Amazingly I was able to find a fix after scouring this site. The answer
was in bug #75055. If I added pci=nomsi to my kernel line in the
menu.lst file I was able to get past BusyBox. Unfortunately all is not
well. I can't seem to get Hardy to recognize my ipod and it freezes
occasionally. I'm going
I have a similar issue which I added here
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/201483.
I'm not sure how close this issue is but I get trapped in BusyBox after
I update to latest in Hardy. This seems to be a more active bug so I'm
going to keep my status here.
--
root fi
Confirmed the problem still exists for me on 2.6.24-16.
"checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd"
Nobody else seems to be getting the above message -- I am attaching my
image to this comment.
For more information, the machine is a Core2 Duo and
I am also experiencing difficulties booting 2.6.24-15.
ASUS P5K-E with 3 SATA drives in RAID-1 containing root and boot.
2.6.22-14 (and lower) boot fine. I have tried 2.6.24-12 through
2.6.24-15 and always get the following message:
"checking if image is initramfs...it isn't (bad gzip magic numb
Experiencing the same symptoms in a 64bit system based on ASUS A8V-E
Deluxe, with two identical SATA 250 Gb disks set as RAID1 and
partitioned so that /, /boot, /home and swap are on separate partitions
after upgrade from Gutsy to Hardy (on April 7th). Loading, please
wait... (I've disabled the spl
** Changed in: linux (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete => Triaged
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notif
I just encountered the same problem as Barrakketh and miekday after updating
from 7.10 to 8.04 beta.
Means I could only boot Ubuntu with the i386 kernel using only one core of my
Intel Q6600 Quadcore machine.
Updating initramfs fixed the problem for me, too.
Thanks mikeday!
--
root filesyste
I ran into this bug after upgrading from Gutsy to Hardy last night.
mikeday's suggestion (run "update-initramfs -k 2.6.24-12-generic -u")
fixed the problem for me.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification
** Changed in: ubuntu
Sourcepackagename: linux-source-2.6.24 => None
Status: New => Invalid
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subsc
Running "update-initramfs -k 2.6.24-12-generic -u" fixed the problem for
me. Anyone who can run the 386 kernel but not the generic kernel should
try that; not sure why it isn't done automatically when the kernel is
upgraded.
By the way, how to unsubscribe from a bug? My inbox is overflowing :)
--
Running "update-initramfs -k 2.6.24-12-generic -u" fixed the problem for
me. Anyone who can run the 386 kernel but not the generic kernel should
try that; not sure why it isn't done automatically when the kernel is
upgraded.
By the way, how to unsubscribe from a bug? My inbox is overflowing :)
--
appending pci=nomsi to the kernel-options in grub.conf works for my
setup, at least on the 32bit-system, reinstalling the 64bit-version
right now.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are
I've got the same problem:
Athlon64, VIA-Mainboard, SATA-Harddrive, Hardy Alpha6
lspci (done with gutsy):
00:00.0 Host bridge: VIA Technologies, Inc. K8T890 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T890 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T890 Host Bridge
00
(For the record, I am running Hardy on a HP xw4600, with two SATA
drives, booting off the first drive, not using RAID, the problem does
not appear to be a volume_id issue, it's that the drives are not being
detected or the module is not being loaded).
--
root filesystem fails to mount (sata_nv mo
I have just experienced the "waiting for root file system" bug after
upgrading from Gutsy to Hardy. I can fix the bug by booting the 386
kernel instead of the generic kernel (2.6.24-12). So it seems to be
specific to SMP, consistent with earlier reports, and is NOT fixed in
Hardy. Any tips would be
I replaced the machine with said controller for some new kit, can't test
if this issue still exist.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subs
I'm not even sure that my comment on this bug relates to the original issue
- but as far as I know yes, this still exists, at least with the latest
available Gutsy Kernel Anything 2.6.22 or newer fails to boot on my
laptop, complaining that it can't mount the root filesystem. 2.6.20 or older
wo
Hi All,
There hasn't been any recent activity in this bug for a while and we
were just wondering if this issue still exists in the latest Hardy Alpha
release? The Hardy Heron Alpha series contains an updated version of
the kernel. You can download and try the new Hardy Heron Alpha release
from h
IMHO the following bugs might be related :
https://bugs.launchpad.net/ubuntu-jeos/+bug/163113
https://bugs.launchpad.net/ubuntu/+bug/163140
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/120316
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/33269
--
root fi
I'm using Gutsy. I have created (qcow) qemu images from Feisty alternate
installer, Gutsy alternate installer and Gutsy JeOS. All these images
fail to mount the root filesystem.
I have attached a screenshot where booting the feisty image fails (I
booted without quiet splash).
I was able to boot t
I am experiencing the same problem after upgrading to Gutsy on Sun Fire
x2200 server. The Feisty kernel boots fine. Gutsy gets stuck at mounting
the root filesystem and gives a BusyBox prompt.
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You r
I can't say for certain if this is the same issue - I upgraded to the
gibbon yesterday, and upon a reboot the system would not come up. The
recovery kernel (2.6.22-14-generic, I think) shows:
BEGIN: Waiting for root filesystem
and it never boots. The Edgy kernel, 2.6.20-16, boots fine. I thought
I'm sorry, I can no longer test this bug, I don't have the laptop any
more.
- Steve
Leann Ogasawara wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out,
> we were wondering if you can still reprodu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out,
we were wondering if you can still reproduce this issue. Could you
please download and try the new version of Ubuntu from
http://www.ubuntu.com/getubuntu/do
[Expired for linux-source-2.6.17 (Ubuntu) because there has been no
activity for 60 days.]
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
After opening question #7704 here:
https://answers.launchpad.net/ubuntu/+question/7704 I was told that I
have hit this bug, so here goes.
This concerns Xubuntu v7.04 alternate CD, with linux v2.6.20.
In summary, I have an old Toshiba Satellite 200CDS laptop, with P166
processor with 48Mb memory,
(comment added to main bug description)
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
** Also affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
root filesystem fails to mount (sata_nv module is loaded)
https://bugs.launchpad.net/bugs/33269
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscr
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: Ubuntu Kernel Team => Ubuntu Kernel Team
--
root filesystem fails to mount (sata_nv module is loaded)
https://launchpad.net/bugs/33269
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
I having the same problem as justinchudgar after upgrading to edgy. The
386 kernel boots fine, but the generic hangs when it's unable to mount
the root filesystem. It's a Asus A8N-E motherboard with a X2 4400+ CPU.
After a while I'm dropped to a shell in the initrd image, and can see
that the sata_
I am having a very similar problem. I am using a Pentium D 805 dual core
on a ECS RC410L/800-Mv2.0, 3 IDE HDDs, 0 SATA devices, 1 IDE HDD. I have
tried installing from both the 6.06 alternate install CD and the 6.06
desktop CD. In either case, the system works fine, but with only 1 CPU
used. When I
This bug may be fixed in the current edgy developement system. In an
effort to track this bug to our latest distribution, it is being
targeted for edgy.
Please confirm whether this bug exists in edgy. If not, then please re-
attach all related output (e.g. dmesg, oops output) while under edgy.
La
i have a same problem
mobo:Asus K8N4.
i hop in Edgy its work fine
--
root filesystem fails to mount (sata_nv module is loaded)
https://launchpad.net/bugs/33269
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
61 matches
Mail list logo
