What is filesystem panic?

[Rick Stevens]

Per Anton Rønning wrote:
> Rick Stevens wrote:
>> Per Anton Rønning wrote:
>>> Mikkel L. Ellertson wrote:
>>>> Per Anton Rønning wrote:
>>>>  
>>>>> Mikkel L. Ellertson wrote:
>>>>>  
>>>>>> Double check that you are accessing the correct device. USB drives
>>>>>> do not always get "assigned" the same device. (It might get assigned
>>>>>> /dev/sdd instead of /dev/sdc for example.) If you are interested in
>>>>>> the reasons for this, it should probably be a separate thread...
>>>>>>
>>>>>> Mikkel
>>>>>>         
>>>>> Oh yes, my processor is slow now. a df command shows this:
>>>>> [root at localhost trade]# df
>>>>> Filesystem           1K-blocks      Used Available Use% Mounted on
>>>>> /dev/mapper/VolGroup00-LogVol00
>>>>>                     718841144   8123212 674202912   2% /
>>>>> /dev/sda1               194442     44177    140226  24% /boot
>>>>> tmpfs                  1943548        48   1943500   1% /dev/shm
>>>>> /dev/ram0                15863       728     15135   5% /mnt/rd
>>>>> /dev/sdf1              3985612     53992   3931620   2% /media/disk
>>>>>
>>>>> The JetFlash pen is assigned to sdf1. But do I have to assign it to 
>>>>> sdc1
>>>>> for it to work??
>>>>> What consequences does this have?
>>>>>
>>>>> Brgds PAR
>>>>>
>>>>>     
>>>> Nope - but you have to use /dev/sdf instead of /dev/sdc if you want
>>>> fdisk to tell you anything about the drive. This is why you were
>>>> getting the unable to open /dev/sdc error message from fdisk.
>>>>
>>>> Mikkel
>>>>   
>>> Of course!
>>> And this is what now comes out of the woodwork:
>>> fdisk /dev/sdf1 -l
>>> Disk /dev/sdf1: 4089 MB, 4089428992 bytes
>>> 126 heads, 62 sectors/track, 1022 cylinders
>>> Units = cylinders of 7812 * 512 = 3999744 bytes
>>> Disk identifier: 0x69737369
>>>
>>> This doesn't look like a partition table
>>> Probably you selected the wrong device.
>>
>> /dev/sdf1 is a partition.  /dev/sdf is the device.  Try:
>>
>>     # fdisk -l /dev/sdf
>>
>> (that's "dash ell", by the way).  That should show you the partition
>> table on drive /dev/sdf.
> Sorry,  my mistake. I don't do these things too often.
> 
> 
> [root at localhost par]# /sbin/fdisk -l /dev/sdf
> 
> Disk /dev/sdf: 4089 MB, 4089445376 bytes
> 33 heads, 63 sectors/track, 3841 cylinders
> Units = cylinders of 2079 * 512 = 1064448 bytes
> Disk identifier: 0x7ef87cc2
> 
>   Device Boot      Start         End      Blocks   Id  System
> /dev/sdf1               1        3842     3993583    b  W95 FAT32
> 
> But I cannot see any message here that points out what goes wrong -
> why it is set to readonly.

There's nothing wrong with the partition from what I can see.

I'm afraid I've purged the previous messsages in this thread (stupid, I
know), but I do have a few questions.  I'm sure you've answered them
before, but I don't have the data handy.  Bear with me.

1. When you plug the device in, does it automount?

2. If it does automount, run "mount" as root and post the line
regarding that device.  It should start with "/dev/sdf1".

3. The system should mount it somewhere in the /media directory.
If it does, did the system choose the mountpoint name or did you
create a directory that it mounts as?

I can try to help you off-list if you wish.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer                      ricks at nerd.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-   UNIX is actually quite user friendly.  The problem is that it's  -
-              just very picky of who its friends are!               -
----------------------------------------------------------------------