Thanks for this driver! I just purchased a Linux-based Linksys NSLU2 which is an inexpensive, tiny network storage unit where you supply your own USB2 external drive. The unit formats the drive in ext3 format. After formatting the drive with the NSLU2, I was able to mount it on my OSX box and read from it. I tried to write but got an immediate OSX crash, but for now reading will suffice!
jbuzbee nyx net
Well, it would be helpful if you could post (or mail me) the contents of your /Library/Logs/panic.log file. But given that you say you are connecting via USB, then I'd say you are running into what seems to be a fairly common problem with USB drives. Please have a look at the other panic threads in this forum and you will see that some USB drives and OS X do not work well toghther. If you have a dual USB/FireWire connection, then use the FireWire connection and you will have no problems.
If you have to use USB, then you have to expect these panics. I've found no problems in the driver, and everyone who has reported this panic and has been able to switch to FireWire (or IDE) has reported no problems with the exact same drive.
Sorry about the bad news.
Here's the log, and thanks for the hint on using firewire. I'll give it a try. I was not totally certain that the unit used a standard ext2/3 format becuase in the Linksys source distribution they include a e2fsprogs-1.34 in a directory called "modified source"
Fri Jul 9 22:51:07 2004
panic(cpu 0): ext2_cmap: allocation requested inside a block (possible filesystem corruption): qbmask=4095, inode=212994, offset=1177088, blkoff=1536
Latest stack backtrace for cpu 0:
0x0008391C 0x00083E00 0x0001EDA4 0x1F9D16A0 0x000B82BC 0x000BC100 0x000BBDC4 0x000BBBF0
0x1F9CC2E4 0x000CDB88 0x00209F38 0x0020A030 0x00244A94 0x00094400 0x03536570
Kernel loadable modules in backtrace (with dependencies):
Proceeding back via exception chain:
Exception state (sv=0x1F558000)
PC=0x9001040C; MSR=0x0000F030; DAR=0xE3E42000; DSISR=0x42000000; LR=0x90297A30; R1=0xF02846C0; XCP=0x00000030 (0xC00 - System call)
Darwin Kernel Version 7.4.0:
Wed May 12 16:58:24 PDT 2004; root:xnu/xnu-517.7.7.obj~7/RELEASE_PPC
Following up, I was able to write to the disk using the firewire interface without issue. I edited several small files, added several small files, and added a 150MB directory tree successfully. After I wrote to the device, the NSLU2 was able to use the device normally.
Jim, that is the same USB panic that others have reported. I'm glad FW is working for you.
I am connecting via the same scenario but cannot write to the disk , even through firewire. Any thoughts ??
btw check this link out. An interesting post on how to add other filsystem support on the NSLU2
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.