Opened 3 years ago
Last modified 3 years ago
#1314 reopened
devices /dev/sda, /dev/sda1 are not created by the system
| Reported by: | frater | Owned by: | somebody |
|---|---|---|---|
| Keywords: | Cc: |
Description
On K26 there are no devices created in /dev to represent the blockdevices that are created when you insert a USB-disk. I have no SD-mod so I don't know the situation there....
The partitions do exist in /proc/partitions. As a workaround I created a script to create them. Because this script only runs on startup it isn't able to detect newly inserted storage....
workaround (only wget works): wget http://wd.mirmana.com/S01fixparts
Change History (3)
comment:1 Changed 3 years ago by frater
comment:2 Changed 3 years ago by BrainSlayer
- Resolution set to invalid
- Status changed from new to closed
there are never block devices created. /dev/discs is the path
comment:3 Changed 3 years ago by frater
- Resolution invalid deleted
- Status changed from closed to reopened
In K24 they correspond with the info in /proc/partitions, in K26 they do not. This causes a utility like fdisk without parameteres to fail. After I create the nodes this utility succeeds in showing the existing parameters.
If the info changes in /proc/partitions it is fine by me as long they correspond...
In K24 they are: scsi/host0/bus0/target0/lun0/disc scsi/host0/bus0/target0/lun0/part1
root@WDS:~# ls -l /dev/scsi/host0/bus0/target0/lun0/disc brw------- 1 root root 8, 0 Jan 1 1970 /dev/scsi/host0/bus0/target0/lun0/disc root@WDS:~# ls -l /dev/discs/disc0/disc brw------- 1 root root 8, 0 Jan 1 1970 /dev/discs/disc0/disc
In K26 it's: sda sda1
If one does fdisk without any parameters in K26 this utility is not able to show the proper info. After I create those nodes "manually" the utility fdisk is able to show info. Same goes for /dev/usb/lp0... Other devices like my WD Worldbook just create all these

Corresponded with Eko on this many times... I'm waiting for him to implement udev or come up with another solution.