Re: [Gtkpod-questions] Read-Only

[phantomjinx <p.g...@ph...>]

Tamas Dobozy wrote:
> Dear P.G.
>
> Thanks so much for getting back to me. It's rare that I actually get 
> responses to my posts, for some reason. I did as you asked and here's 
> what I got, in total:
>
> Aug 26 14:51:39 tamas-laptop kernel: [10526.839449] sd 6:0:0:0: [sdb] 
> 58605120 512-byte hardware sectors: (30.0 GB/27.9 GiB)
> Aug 26 14:51:39 tamas-laptop kernel: [10526.840571] sd 6:0:0:0: [sdb] 
> Write Protect is off
> Aug 26 14:51:39 tamas-laptop kernel: [10526.840577] sd 6:0:0:0: [sdb] 
> Mode Sense: 68 00 00 08
> Aug 26 14:51:39 tamas-laptop kernel: [10526.840583] sd 6:0:0:0: [sdb] 
> Assuming drive cache: write through
> Aug 26 14:51:39 tamas-laptop kernel: [10526.840593]  sdb: [mac] sdb1 
> sdb2 sdb3
> Aug 26 14:51:39 tamas-laptop kernel: [10526.855498] sd 6:0:0:0: [sdb] 
> Attached SCSI removable disk
> Aug 26 14:51:39 tamas-laptop kernel: [10526.855651] sd 6:0:0:0: 
> Attached scsi generic sg2 type 0
> Aug 26 14:51:40 tamas-laptop kernel: [10527.778578] hfs: Filesystem 
> was not cleanly unmounted, running fsck.hfsplus is recommended.  
> mounting read-only.
> Aug 26 14:51:40 tamas-laptop kernel: [10528.188220] hfs: Filesystem 
> was not cleanly unmounted, running fsck.hfsplus is recommended.  
> mounting read-only.
> Aug 26 14:51:40 tamas-laptop hald: mounted /dev/sdb3 on behalf of uid 
> 1000
>
> As you can see, at the very bottom, it's telling me that my filesystem 
> was not cleanly unmounted, which doesn't make sense, since I always 
> eject via software, and then wait until the iPod itself tells me it's 
> safe to disconnect before actually pulling the plug.
>
> Can you advise me further on what to do?
>
> Thanks,
> Tamas
That's pretty useful then. Seems you didnt unmount the ipod on a 
previous occasion. Thus, it would like you to run fsck on it.

So what to do:

1) Unmount ipod
2) Remove and reinsert if you want to be sure.
3) Don't mount the ipod!
4) su to root in a terminal
5) run the command "/sbin/fsck.hfsplus /dev/sdb3" where sdb3 I think is 
the offending partition according to your log.

See how that works for you.

PGR