By sgthomas ·
I have a 1 1/2T MyBookWorld ll Net Drive. It contains all of my important documents, programss, and backups. I'm unable to access it. All the folders have a gray X.

A few weeks ago I had inadvertently hit the 'sync' button and couldn't stop it. My search on 'how to' informed me that it's not removable (!@#$%^&*). Now when I check the properties of the drive, it reads 'File System CSC-CACHE' and gives me an incorrect drive size.

Can anyone give me a clue as to what to do about this dilemma?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

One or both of these may be useful

by OH Smeg Moderator In reply to CSC-CACHE

How to re-initialize the offline files cache and database
View products that this article applies to.
Article ID : 230738
Last Review : February 27, 2007
Revision : 5.3
This article was previously published under Q230738
On This Page



Method 1

Method 2

The Offline Files (CSC or Client Side Caching) cache and database has a built-in capability to restart if its contents are suspected of being corrupted. If corruption is suspected, the Synchronization Wizard may return the following error message:
Unable to merge offline changes on \\server_name\share_name. The parameter is incorrect.
Back to the top

Method 1
The Offline Files cache is a folder structure located in the %SystemRoot%\CSC folder, which is hidden by default. The CSC folder, and any files and subfolders it contains, should not be modified directly; doing so can result in data loss and a complete breakdown of Offline Files functionality.

If you suspect corruption in the database, then the files should be deleted using the Offline Files viewer. After the files are deleted out of the Offline Files viewer, a synchronization of files may then be forced using Synchronization Manager. If the cache still does not appear to function correctly, an Offline Files reset can be performed using the following procedure: 1. In Folder Options, on the Offline Files tab, press CTRL+SHIFT, and then click Delete Files. The following message appears:
The Offline Files cache on the local computer will be re-initialized. Any changes that have not been synchronized with computers on the network will be lost. Any files or folders made available offline will no longer be available offline. A computer restart is required.

Do you wish to re-initialize the cache?

2. Click Yes two times to restart the computer.

Back to the top

Method 2
If you cannot access the Offline Files tab, use this method to reinitialize the Offline Files (CSC) cache on the system by modifying the registry. Use this method also to reinitialize the offline files database/client-side cache on multiple systems. Add the following registry subkey:
Key Name: FormatDatabase
Key Type: DWORD
Key Value: 1
Note The actual value of the registry key is ignored. This registry change requires a restart. When the computer is restarting, the shell will reinitialize the CSC cache and then delete the registry key if the registry entry exists.

Warning All cache files are deleted and unsynchronized data is lost.

Or from the WD Web Site

Hacking WD MyBook

Rescue Procedure
Link to the discussion about this procedure.
Steps of recovery
100% Functional for ALL DISK SIZES.
1. Remove the HDD from MyBook World Edition (PDF Link) and connect it to your PC. In this manual i refer to the disk as /dev/sda1

cd ~
su root [enter root passwd]

2. Download the rescue files [57 MiB]

wget http://szabados.sk/mybook_we_rescue.zip
unzip mybook_we_rescue.zip
cd rescue

Begin Edit
The Mac Address of your MyBook is stored in the non partitioned par of the HD.
Once you do this you wont be able to get it back, instead you will have the Mac Address
00:90:a9:15:99:84. ?? use this comands to get the from the Image of your HD the values for your Mac Address
if you dont care or have just One Mybook skip this lines

dd if=/dev/sda bs=1 skip=24064 count=4 | od -x
dd if=/dev/sda bs=1 skip=24462 count=17 | od -c

Post them here if you like so we can figure it out how they were built

I dont know how to write them back, I hope someone edit this lines

End Edit
3. Zero fill the first 3 GiB of space on disk

dd if=/dev/zero of=/dev/sda bs=1M count=3000

Did you use the right drive letter? Did you? If not, you'll be crying, right about now?.

4. Copy the contents of rescue.img to the disk

dd if=rescue.img of=/dev/sda

5. Create the first 3 system partitions

sfdisk /dev/sda < SDA_PTAB

6. Create the last partition at the end of the disk

cfdisk /dev/sda

At the end of the disk there is much free space, create there a PRIMARY partition, set it to be TYPE=fd
This is because this manual is usable for all kind of disks big enough? So you can do this also with a 500G, 750G, 1000G or bigger disk. So the partition at the end is variable size dependent on the disk.

// *begin edit - If you've encountered problems with read-only mounts of /dev/sda4 after this rescue procedure, then redo the whole tutorial. In exchange for TYPE=fd use TYPE=83 within step 5 and you'll be fine!

Some Linux distributions do automounting new partitions? So umount them if possible.

umount /dev/sda1
umount /dev/sda3
umount /dev/sda4

7. Format 4th partition with no space reserved for UID 0

mkfs.ext3 -m 0 /dev/sda4

Low Space rescue: You need about 4 GiB of free space for this rescue procedure, if you do not have enough follow the steps bellow.

// *begin edit - There's no need for any local disk space beyond the storage of the compressed rescue files. Every time you see a sequence like this:

bunzip2 filename.bz2
dd if=filename#.bz2.out of=/dev/sda#

instead do this:

bunzip2 <filename#.bz2 >/dev/sda#

This will decompress the files on the fly, which will not only save you from needing massive amounts of free local disk space, but also it will take only a fraction of the time.

Needless to say that if you do it this way you can skip the "not enough free space" steps.

// * end edit

You do not have to do this if you have enough free space?

mkdir /mnt/sda4
mount /dev/sda4 /mnt/sda4 -t ext3
cd ..
mv rescue /mnt/sda4
cd /mnt/sda4/rescue

8. Unpack and copy the contents of the 1. system partition

You'll need cca 3 GiB of free space.

bunzip2 SDA1_IMA.BZ2
dd if=SDA1_IMA.BZ2.out of=/dev/sda1

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

9. Unpack and copy the contents of the swap [2nd] partition

You'll need cca 100 MiB of free space.

bunzip2 SDA2_IMA.BZ2
dd if=SDA2_IMA.BZ2.out of=/dev/sda2

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

10. Unpack and copy the contents of 3rd system partition

You'll need cca 1 GiB of free space.

bunzip2 SDA3_IMA.BZ2
dd if=SDA3_IMA.BZ2.out of=/dev/sda3

If you see a message like this: "I/0 or other error, bailing out. Possible reson follows. No space left on device" Follow the "Low Space rescue" described at step 6 and then continue from where you stooped

11. Turn off fsck for all [NON SWAP] system partitions

tune2fs -c -1 -i 0 /dev/sda1
tune2fs -c -1 -i 0 /dev/sda3
tune2fs -c -1 -i 0 /dev/sda4

12. Edit /etc/fstab

mkdir sda1
mount -t ext3 /dev/sda1 sda1
nano sda1/etc/fstab

/dev/md4 MUST BE REPLACED BY /dev/sda4!

Save it by pressing CTRL + X, Y, ENTER.
Or use any other editor you like? [Nano is quite simple]

umount sda1


13. poweroff the computer

Plug the drive back to MyBook and be happy its running again


M$ Knowledge Base Article


WD Hacking WB Mybook World


Collapse -

Changing the MAC address of MyBook

by ruud.broers In reply to One or both of these may ...

The MAC address is stored in ASCII at 5F8E through 5F9E as part of the boot code.

The actual code reads:
bootargs=mem=32M console=ttyS0,115200 root=/dev/md1 netdev=0,0,0x0090A925,0x7AA1,eth0

However, simple patching will not work, as the CRC32 will be messed up. CRC32 is stored (LSB first) in the 4 bytes starting at 5E00.
CRC32 is calculated over 1FFC (x2000 -4) bytes, starting at 5E04. With the above MAC address, the CRC32 is 523DC6BF.

YOU MUST RECALCULATED the CRC32 and patch it as well.

Related Discussions

Related Forums