Mikkel L. Ellertson wrote:
Per Anton Rønning wrote:
> But now the pen seems to be really stuck, just look at this:
>
> [root@localhost disk]# /sbin/fdisk /dev/sdc
> Unable to open /dev/sdc
>
> And also:
> [root@localhost disk]# /sbin/fdisk /dev/sdc1
> Unable to open /dev/sdc1
>
> This is not a disaster, it just means that I have to consider this flash
> pen obsolete and buy a new one.
> I have been using it for backup of some hard disk directories, so it is
> no big deal if I lose whats on it, since my harrdisk is intact.
>
> Perhaps I should buy a removable HD instead.
>
> BRGDS
> PAR
>
>
Plug the drive in, and then run "tail /var/log/messages" to see what
messages are generated. I would not be surprised to if the problem
was that the drive was assigned a different letter. Also, you do not
want to use fdisk on anything but the base drive. Using it on
/dev/sdc1 will produce all kinds of interesting errors on a good drive.
Mikkel
Sorry, I discovered this too late (The eyes stand in the way of eyesight):
[root@localhost trade]# tail /var/log/messages
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Write Protect is off
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Assuming drive
cache: write through
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] 7987198 512-byte
hardware sectors (4089 MB)
:
:
It says sdf, not sdc. Is that the problem maybe?
Brgds
PAR