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
I am sorry but right now I am unable to help you debug this due to other
commitments, and I am changing over to 64-Bit Hardy.
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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
changed to new because new information added
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Incomplete => New
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
lspci -vvnn > lspci-vvnn.log
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/9654118/lspci-vvnn.log
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
Today it was my USB (I-pod) device would not automount.
Here is information that has been provided before
uname -a
Linux thorium 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686
GNU/Linux
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/9654117/dmesg.log
--
Superbl
Well here we go again! This morning when I powered up my PC i had the following
problems
1 - USB (I-pod) device would not automount.
so I rebooted with a shutdown -r now
2. had 3 trys at this because of all the problems noted in previous entries
3. Then I had no menus from the gnome toolbar and th
Well the problem has not been fixed. Here is the current indication:
Log of fsck -C -R -A -a
Fri Jul 6 08:50:24 2007
fsck 1.40-WIP (14-Nov-2006)
fsck.ext3: Unable to resolve 'UUID=e1298250-91d0-4524-8fea-abeffc04d4ec'
fsck died with exit status 8
Fri Jul 6 08:50:24 2007
As yo
And the next attachment here
** Attachment added: "lspci -vvnn > lspci-vvnn.log"
http://launchpadlibrarian.net/8270229/lspci-vvnn.log
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
A few days ago my son ran the following command:
sudo update-initramfs -u
Since then I have had no boot-up problems. This does not mean that the
problem is fixed, because I can go for days without having any problems,
and then get several in a row. So I would like to wait a while before I
claim t
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response.
It should be one, long line of text whic
A new problem in this saga
Two days in a row I have had the following messages on bootup.
BusyBox V1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in Shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
Of course on reboot - I have to use
Hello, I'm Bananabob's Son.
Here are a few more pieces of information.
The raid is set up using partions 3 of both drives.
Swap is on partions 2 of both drives to load balance.
Root is on partion 1 of the first drive. Partition 1 of the second drive is for
a developmental root if the need arises
Final suggestion: Start a thread in Installation & Upgrades and ask about
proper RAID configuration for Feisty.
I assume you are using "software-only RAID 1 using mdadm", correct? I did a
little poking around and it's not a simple thing, but you'll get more answers
there.
--
Superblock not r
I agree, there is something odd about your fstab. For starters, it
lists two swap partitions. If there is some advantage to that I am not
aware of it. It may even be bad. Second, couldn't your root partition
(/dev/sda1) be paired with the unused partition (/dev/sdb1) in a Raid
volume to get im
Here is the commands outout as requested.
[EMAIL PROTECTED]:~$ blkid
/dev/sda1: LABEL="System" UUID="69eb4fab-f38b-43f7-8796-39734a877b89"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="b800200b-197f-40e2-b27e-684b783e1bea"
/dev/sdb1: LABEL="Development" UUID="e4ee9322-cbbf-4252-ad3e-
Banana -
post the output of these two commands:
blkid
sudo fdisk -lu
Also, explain your hd structure. You have sda, sdb, and volume? What
are those devices and what's on them.
I'm no genius, but maybe I can help (whilst we wait for a techie to look
at this)
--
Superblock not read at boot
http
Here is my FSTAB. My question is what does it mean and how do I change
it to get it work with the new kernel? It seems to me that I am using
dev/sdxx ids!
# /etc/fstab: static file system information.
#
#
proc/proc procdefaults0 0
# /dev/sda
Okay, this is NOT exactly a bug.
It may be caused by the use of /dev/hdxx device identifiers in fstab.
Evidently this latest kernel no longer recognizes those and the partitions are
now identified as /dev/sdxx.
The problem in this case is caused by a bug in the upgrade path from Dapper to
Edgy.
E
contents /var/log/udev
** Attachment added: "udev.tar.gz"
http://launchpadlibrarian.net/8138881/udev.tar.gz
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
output of dmesg (tar.gz format)
** Attachment added: "dmesg.tar.gz"
http://launchpadlibrarian.net/8138878/dmesg.tar.gz
--
Superblock not read at boot
https://bugs.launchpad.net/bugs/120285
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Here is fstab. Some explanation:
hda - old hd with possible bad blocks - not used except to recover data now and
then
hdb - new Maxtor hd. has copy of Windows XP in hdb1 & hdb2. Ubuntu boots from
hdb6.
hdb6,7,8 are logical partitions within a container partition
** Attachment added: "content
I will be happy to provide any details possible.
This problem is reproducible. On my HP Pavilion 750c Desktop it happens on
every boot with the 2.6.20-16-386 kernel.
Simply dropping back to the 2.6.17 kernel allows the system to boot.
John
** Attachment added: "fsck log"
http://launchpadlibr
I am getting the same behavior on an HP Pavillion Desktop except mine is
consistent. It will not boot at all. I get this error EVERY time.
The only solution has been to revert to the 2.6.17 kernel. Obviously there is
nothing wrong with the superblock if I can boot with an older kernel.
--
Sup
24 matches
Mail list logo
