Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Could you check the output of dmesg to see if your disk has been recognised? Have you got your /proc mounted? You could also check in there to see if the disk has been identified.
<edit>
UnSpawn, does fdisk not work on disks... when you have a blank disk, lets say, and you want to create partitions, would you not need to work on the disk rather than partition?
</edit>
If the disk has no partitions, then there is no reason to mknod /dev/hda1. Also, your dmesg shows that hdb=your cd/dvd drive... do you need to mknod /dev/hdb1? Does fdisk /dev/hda throw a paddy if you do not mknod anything? What are you trying to put onto the disk, anyway?
Yeah, you're right Thymox, guess I was thinking of fsck instead of reading "fdisk", which is sad.
Btw good work on the stats, you did as well. Which isn't sad :-]
initrd# cat /proc/partitions
major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq
fdisk without mknod anything?
initrd# fdisk
Usage: fdisk [-l] [-b SSZ] [-u] device
E.g.: fdisk /dev/hda (for the first IDE disk)
or: fdisk /dev/sdc (for the third SCSI disk)
or: fdisk /dev/eda (for the first PS/2 ESDI drive)
or: fdisk /dev/rd/c0d0 or: fdisk /dev/ida/c0d0 (for RAID devices)
...
initrd# cat /proc/partitions
major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq
demsg
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
HPT371: IDE controller on PCI bus 00 dev e0
PCI: Enabling device 00:1c.0 (0000 -> 0001)
HPT371: chipset revision 1
HPT371: not 100% native mode: will probe irqs later
HPT370: using 33MHz PCI clock
hdh: TOSHIBA MK6015MAP, ATA DISK drive
ide3 at 0x1810-0x1817,0x180e on irq 4
hdh: 11733120 sectors (6007 MB), CHS=12416/15/63
Partition check:
/dev/ide/host2/bus1/target1/lun0: [PTBL] [730/255/63] p1
...
initrd# ls /proc/ide/ -l
-r--r--r-- 1 root root 0 Jan 1 00:12 drivers
lrwxrwxrwx 1 root root 8 Jan 1 00:12 hdh -> ide3/hdh
-r--r--r-- 1 root root 0 Jan 1 00:12 hpt366
dr-xr-xr-x 3 root root 0 Jan 1 00:12 ide3
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.