Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
problems mounting zip disk after system update
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
tuclogicguy
n00b
n00b


Joined: 17 Dec 2013
Posts: 15

PostPosted: Thu Jan 23, 2014 6:11 pm    Post subject: problems mounting zip disk after system update Reply with quote

I have an IDE Zip drive on my system. I have the following line in my /etc/fstab:
Code:
/dev/sdb4      /mnt/zip   auto      noauto,user   0 0

Prior to doing the system upgrade, all I had to do to use the Zip drive was to shove a disk into the drive and type
Code:
mount /mnt/zip

Now, following the system upgrade, when I type
Code:
mount /mnt/zip
I get
Code:
mount: special device /dev/sdb4 does not exist
Multiple attempts to mount the zip disk give the same error message.

I have discovered that I can type
Code:
mount /dev/sdb /mnt/zip
(I guess this is like trying to mount sector 0, instead of a specific partition) and I get
Code:
mount: /dev/sdb is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
This causes the above error messages but seems to cause the MBR of the zip disk to be read and the /dev/sdb4 device to get created. From then on I can type
Code:
mount /mnt/zip
and the mount succeeds.

I am still booting with the same kernel as before the system upgrade so something in the upgrade caused the behavior to change. Before, it appears that simply shoving in the zip disk caused the /dev/sdb4 device name to be created and I didn't have to do anything else before mounting the zip disk. How can I get the previous behavior back? Thanks.
Back to top
View user's profile Send private message
massimo
Veteran
Veteran


Joined: 22 Jun 2003
Posts: 1226

PostPosted: Fri Jan 24, 2014 7:15 am    Post subject: Reply with quote

I think in my case it was kmod-static-nodes which was missing in the sysinit run-level - check using rc-update.
_________________
Hello 911? How are you?
Back to top
View user's profile Send private message
tuclogicguy
n00b
n00b


Joined: 17 Dec 2013
Posts: 15

PostPosted: Fri Jan 24, 2014 11:25 pm    Post subject: Reply with quote

I did
Code:
rc-update add kmod-static-nodes sysinit
and rebooted. The /dev/sdb4 device still is not created on boot and I still get
Code:
# mount /mnt/zip
mount: special device /dev/sdb4 does not exist

I am thinking there must be some service I need running in order to have removable disks scanned when they are inserted and the applicable /dev/sd* entries created automatically. What would that be?

Any other suggestions?
Back to top
View user's profile Send private message
tuclogicguy
n00b
n00b


Joined: 17 Dec 2013
Posts: 15

PostPosted: Sat Jan 25, 2014 2:52 am    Post subject: Reply with quote

Quote:
I am thinking there must be some service I need running in order to have removable disks scanned when they are inserted and the applicable /dev/sd* entries created automatically.
Is this what udev is supposed to do? "top" indicates that udevd is running.

I noticed that one thing that got updated in the system upgrade was udev, to version 208. I suspect that this udev update is what caused the change in behavior I'm reporting. I wonder if I need to configure udev somehow to handle the zip drive properly.

Any suggestions?
Back to top
View user's profile Send private message
tuclogicguy
n00b
n00b


Joined: 17 Dec 2013
Posts: 15

PostPosted: Sat Jan 25, 2014 9:29 pm    Post subject: Reply with quote

I just stumbled onto some additional insight.

1. insert zip disk into drive; the drive light flashes very briefly
"ls /dev" shows that the /dev/sdb4 node is not created
2. I execute this command:
Code:
eject --trayclose /dev/sdb
A Zip drive doesn't have a tray, BUT I notice that the drive light comes on for a few seconds seemingly indicating that the system is querying the disk contents.
"ls /dev" shows that the /dev/sdb4 node is created
Now I can mount and umount /mnt/zip and read the contents of the disk.
3. I execute the command:
Code:
eject -s /dev/sdb
The zip disk is ejected.
"ls /dev" shows that the /dev/sdb4 node has disappeared.

Thus, it appears that the fundamental problem is that the system does not recognize that a disk has been inserted into the zip drive. It takes the "eject --trayclose" command to trigger something in the system that a disk has been inserted.

Prior to the last system upgrade, it didn't work like this. All I had to do was insert a zip disk and the system would detect it and create the appropriate /dev/sdb4 node. I'm suspecting the latest version of udev, but maybe something else is the real culprit.

Anybody else have any insights?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum