[ubuntu-uk] New Kernel = No Mount?
william at mediamodus.us
Mon Jan 30 03:07:05 GMT 2006
It diff a tad on the fact that i can get.. the computer doesnt come with
raid except one but the same problem on all my ubuntu installs... its
something that has changed on the 2.6.13+ kernels that has that effect a
friend tells me.. it happends on drives that have just one partition or
some crazy thing like that.
heres the mount output on me box:
/dev/hda2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/hda1 on /boot type ext3 (rw)
/dev/hdd1 on /media/multimedia type ext3 (rw,nosuid,noatime,user_xattr)
/dev/hdc1 on /media/storage type ext3 (rw,nosuid,noatime,user_xattr)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
dev HDC is the one with the problem.. it mounts fine in kernel 2.6.12
but not in any other over that. it has just one partition.
dev HDD is the drive that DOES mount in all kernels i have tested.. it
has 2 partitions: 1 the data 2 a swap ( 400 mgs ish )
im really not sure what the problem might be, i dont think the partition
table and or format the file system has might be whats keeping it from
both HDC1 and HDD1 have similar ext3 configs... the only diff is that
HDC1 is set to LARGEFILES and HDD1 is set to LARGEFILES4 or something
Pete Ryland wrote:
> On Sun, Jan 29, 2006 at 05:00:39 -0800, William Amaral wrote:
>> the drive is ata and it shows up with both the new and ubuntu patched
>> kernel, it even detects the partition as ext3 ( it is correct ) but it
>> does not mount it.... ( in the newer kernels downloaded downloaded and
>> built from kernel.org )
>> Its bloody wierd... i never had the problem in debian... still dont..
>> just in all my ubuntu's... it affects different drives.. i dont know if
>> it has something to do with the "active-ness" of the partition ( i doubt
>> it ) but it must be something... why doesnt that drive come up and my
>> other does just fine.
>> im not sure.. might be a version conflict between kernel and gnu's mount
>> or something .
> Unlikely, mount just calls the mount system call in the kernel. It's
> definitely one of the patches added recently. Looking at:
> might help identify what might have changed to cause this. Are the reports
> in this bug:
> similar to what you are experiencing?
More information about the ubuntu-uk