LinuxQuestions.org - Cannot access my System HDD with cfdisk, during System is running from this disk

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Cannot access my System HDD with cfdisk, during System is running from this disk (https://www.linuxquestions.org/questions/debian-26/cannot-access-my-system-hdd-with-cfdisk-during-system-is-running-from-this-disk-712928/)

Cannot access my System HDD with cfdisk, during System is running from this disk

Hi,
I am new in this forum, i've read here a lot before and so i decided to register.

I have a problem with a server running a debian.
I made 3 partitions:
/dev/sda1: /
/dev/sda2: swap
/dev/sda3: /var
after installation i had todo a kernel update for my vmwareserver and there came the problems.

With my new kernel i cannot acces the hdd with cfdisk / fdisk ...

the /dev/sda files does not exists

Code:

:/#  ls /dev/ | grep sd

:/#

but /dev/sda1 is mounted ....

Code:

:/# df -h

Dateisystem          Gr▒▒e Benut  Verf Ben% Eingeh▒ngt auf

/dev/sda1              19G  3,9G  14G  23% /

tmpfs                482M    0  482M  0% /lib/init/rw

tmpfs                482M  4,0K  482M  1% /dev/shm

and in /proc/partitions there are also all 3 partitions listened

Code:

:/# cat /proc/partitions

major minor  #blocks  name



  8        0  244198584 sda

  8        1  19535008 sda1

  8        2    1951897 sda2

  8        3  222709095 sda3

This is the thing which is very strange for me

I'm not able to make a filesystem on my sda3 partition because he cannot find the /dev/sda3 file

im using kernel 2.6.28.7

I hope someone knows what I've made wrong, because google was not able to help me in this case

greez an0r0c

Post the output of

Code:

ls -Al /dev/disk/by-path/

There's an extranious "ls" in there, but it won't do any harm. What does "fdisk -l" give (try it as root/sudo).

Code:

:# ls -Al /dev/disk/by-path/

ls: /dev/disk/by-path/: Datei oder Verzeichnis nicht gefunden

Code:

:# fdisk -l

:#

I think that looks not good?

Quote:

Originally Posted by an0r0c (Post 3481831)

I think that looks not good?

That just might qualify as an understatement ...

Will need to think some more on this.

What version Debian?

Quote:

Originally Posted by an0r0c (Post 3481199)

after installation i had todo a kernel update for my vmwareserver and there came the problems.

With my new kernel i cannot acces the hdd with cfdisk / fdisk ...

Without knowing the changes, I suspect we can't help.
I don't know what version of fdisk you have, but the source I have shows /proc/partitions being run. I'm surprised you don't get a fatal error message if the device nodes don't exist.

So i checked my kernel and it's not possible that that is my kernels fault. Because my server hoster offers a netboot kernel with this kernel all the hardware should work , all but module support and I got the same problem.

fdisk version: fdisk v2.12r

in my dmesg it knows the harddisk:

Code:

scsi 0:0:0:0: Direct-Access    ATA      ST3250410AS      3.AA PQ: 0 ANSI: 5

sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

 sda: sda1 sda2 sda3

sd 0:0:0:0: [sda] Attached SCSI disk

Fusion MPT base driver 3.04.07

now i have really no idea what i have made wrong ...