[SOLVED] 2.6.32 cant detect my hard drive

Heema · 2010-01-03 21:31:39

with the recent upgrade my primary harddrive isnt dectected so it gives a kernel panic and says root device doesnt exist

but if i restart a couple of times it gets detected but doesnt detect the secondary harddrive

it works without a problem with the fallback kernel

my both drives are sata

fdisk -l                     

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x9b0b9b0b

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3824    30716248+   7  HPFS/NTFS
/dev/sda2            3825       19457   125572072+   f  W95 Ext'd (LBA)
/dev/sda5            3825       10199    51207156    b  W95 FAT32
/dev/sda6           10200       14023    30716248+   b  W95 FAT32
/dev/sda7           14024       16574    20490876    7  HPFS/NTFS
/dev/sda8           16575       16640      530113+  82  Linux swap / Solaris
/dev/sda9           16641       19457    22627521   83  Linux

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe5cc16e9

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       24027   192996846    c  W95 FAT32 (LBA)
/dev/sdb2           24028       30401    51199155    7  HPFS/NTFS

Last edited by Heema (2010-01-08 17:50:41)

jdarnold · 2010-01-03 23:33:24

My standard advice is to use "UUID=" instead of "/dev/sda" in /etc/fstab. Use the blkid to get the UUID of all your partitions, then replace the partition /dev/sd?? in your fstab with UUID=.... So, in my fstab, I have:

#/dev/sda4
UUID="303889b7-ae78-436f-85ac-da95b2280596" / ext3 defaults 0 1

Heema · 2010-01-04 00:26:16

i can try that, but in the normal kernel it doesnt even detect the hard disk in dmesg or using fdisk

in the fallback it works without a problem

Last edited by Heema (2010-01-04 00:28:26)

Heema · 2010-01-05 09:38:28

some one posted a bug report

http://bugs.archlinux.org/task/17674

fourreux · 2010-01-05 13:56:58

is there any workaround?

is it recomended to downgrade kernel version?

(and is there a thread or wiki page that specifically tells/helps downgrading the kernel. I mean do I simply try to "pacman -U /var/cache/pacman/pkg/kernel26-2.6.31.6-1-i686.pkg.tar.gz" it says that nvidia: requires kernel26>=2.6.32. so it would get more complicated.)

but I could as well wait 1 or 2 days ...

anyways, I'm relieved that it's not a hardware problem

Heema · 2010-01-05 14:10:29

fourreux wrote:

is there any workaround?
is it recomended to downgrade kernel version?
(and is there a thread or wiki page that specifically tells/helps downgrading the kernel. I mean do I simply try to "pacman -U /var/cache/pacman/pkg/kernel26-2.6.31.6-1-i686.pkg.tar.gz" it says that nvidia: requires kernel26>=2.6.32. so it would get more complicated.)
but I could as well wait 1 or 2 days ...
anyways, I'm relieved that it's not a hardware problem

my workaround for now until there is a solution, is that i am using the fallback kernel

i am sure there will be an update to fix this soon

Last edited by Heema (2010-01-05 14:13:05)

idostyle · 2010-01-05 18:07:30

Got the same problem here, googled around for some time and found this ml thread, which fits the description:

1. Kernel 2.6.32.2
2. Sata root device failing
3. Messages about "Sata link down" right before kernel panic
4. Works with some minor modifications (Failback kernel)

Didnt try the patch posted by Tejun Heo here yet, but looks promising :>

Heema · 2010-01-05 20:35:29

idostyle wrote:

Got the same problem here, googled around for some time and found this ml thread, which fits the description:
1. Kernel 2.6.32.2
2. Sata root device failing
3. Messages about "Sata link down" right before kernel panic
4. Works with some minor modifications (Failback kernel)
Didnt try the patch posted by Tejun Heo here yet, but looks promising :>

Thanks for that, i reposted this (crediting you ) in the bug report http://bugs.archlinux.org/task/17674

Heema · 2010-01-08 17:52:22

the latest update (2.6.32.3-1) solved this bug it seams

fourreux · 2010-01-08 21:07:12

indeed. everything back to normal on my system.

kaptenen · 2010-01-08 21:30:03

Hm, I got i similar problem with the 2.6.32 and the new update dosen´t help. Here is some text that shows up when updating:
http://pastebin.com/m572fd53

kaptenen · 2010-01-18 22:29:05

My problem was fixed for some time ago, the color-wrapper was the problem.

Arch Linux

#1 2010-01-03 21:31:39

[SOLVED] 2.6.32 cant detect my hard drive

#2 2010-01-03 23:33:24

Re: [SOLVED] 2.6.32 cant detect my hard drive

#3 2010-01-04 00:26:16

Re: [SOLVED] 2.6.32 cant detect my hard drive

#4 2010-01-05 09:38:28

Re: [SOLVED] 2.6.32 cant detect my hard drive

#5 2010-01-05 13:56:58

Re: [SOLVED] 2.6.32 cant detect my hard drive

#6 2010-01-05 14:10:29

Re: [SOLVED] 2.6.32 cant detect my hard drive

#7 2010-01-05 18:07:30

Re: [SOLVED] 2.6.32 cant detect my hard drive

#8 2010-01-05 20:35:29

Re: [SOLVED] 2.6.32 cant detect my hard drive

#9 2010-01-08 17:52:22

Re: [SOLVED] 2.6.32 cant detect my hard drive

#10 2010-01-08 21:07:12

Re: [SOLVED] 2.6.32 cant detect my hard drive

#11 2010-01-08 21:30:03

Re: [SOLVED] 2.6.32 cant detect my hard drive

#12 2010-01-18 22:29:05

Re: [SOLVED] 2.6.32 cant detect my hard drive

Board footer