Topic: linux mount SD722

[Lil Kim Jong-Il]

Has anyone here had success mounting an SD722 on linux? 

I see the FW link attach and hardware scanner sees the drive as a fat32 volume.  But mount complains.

[it-goes-to-eleven]

Do it all the time.  But.. Not on all of my linux systems.  Some kernels have some firewire support compiled in but not enough.  Or maybe the functionality isn't all there in some versions. I do all my transfers under 2.6.11 knoppix.

# dmesg | tail
SCSI device sdb: 78242977 512-byte hdwr sectors (40060 MB)
sdb: Write Protect is on
sdb: Mode Sense: a9 e4 a0 00
SCSI device sdb: drive cache: write back, no read (daft)
SCSI device sdb: 78242977 512-byte hdwr sectors (40060 MB)
sdb: Write Protect is on
sdb: Mode Sense: a9 e4 a0 00
SCSI device sdb: drive cache: write back, no read (daft)
 sdb: sdb1


I believe there were some changes in the latest release from SD. I don't recall the message:
SCSI device sdb: drive cache: write back, no read (daft)

And it only mounts read-only now.  I'm not much concerned about the read only for normal use but it is a new 'problem' that will come up when I need to copy a new firmware to the drive.

[fozzy]

I think firewire support is native in 2.6+  I had some success w/ a 2.4 kernel and fedore though.  I did have issues w/ my via card and the 722 on windows and linux but the new adaptec one i got works flawlessly in both systems

[Lil Kim Jong-Il]

OK, well then possibly I'm doing something wrong.  I'm running FC2 with recent updates.  I have no problem mounting a FAT32/VFAT firewire drive in an external box, but it doesn't like the SD722. 

Wow, so you updated the SD722 and now cannot write to the HD via FW?  That sounds like a really f'd up problem.  Does it work from an XP machine?  A work around would be to load the new firmware via CF drive if you have a way to load one.

Thanks for the help.  I'll try again and dump the log when the 722 comes home from Phil.

[pigiron]

sdb: Write Protect is on
sdb: Mode Sense: a9 e4 a0 00

ahhh... so you got the read-only thing with 2.6.11 now too. I poured thru the code until about 2AM without success... haven't had time to get back to it... but I'll have to soon 'cause the hard drive is starting to fill up    When they gonna get us some firmware with file delete?

I'll try again and dump the log when the 722 comes home from Phil.

yea... throw the log and the mount message up here and we might be able to bring some light.

[tchoub]

Do it all the time.  But.. Not on all of my linux systems.  Some kernels have some firewire support compiled in but not enough.  Or maybe the functionality isn't all there in some versions. I do all my transfers under 2.6.11 knoppix.

ah, another Knoppix user ! +T   

[it-goes-to-eleven]

Yep, knoppix on my old vaio laptop (where I mount the 722 and rsync to my gentoo desktop).  When I first got the vaio around 2001, it took a lot of effort to get the hardware working (and wireless).. It is nice to just throw knoppix on and have everything work..

I'm not sure if this read-only thing is a linux issue or an sd issue. It could be either at this point. Just odd that it only surfaced after my 722 upgrade.  It would be interesting to know if it happens on more recent kernels or versions of knoppix, etc. Good to hear I'm not the only one..

Pigiron, you might want to just format the 722. I don't really delete anything from mine. I don't format after every show as some seem to but I usually don't let it get much more than about half full.

When I spoke to Justin he said linux was unsupported and seemed a little surprised I was using it.  Perhaps we need to send some nice notes to SD just to let them know they have customers who prefer Linux.

The irony is.. Even though I have to use windows for audio software, I don't really trust it for something as important as copying masters off the 722.

[pigiron]

I'm not sure if this read-only thing is a linux issue or an sd issue. It could be either at this point. Just odd that it only surfaced after my 722 upgrade.  It would be interesting to know if it happens on more recent kernels or versions of knoppix, etc. Good to hear I'm not the only one..

Pigiron, you might want to just format the 722. I don't really delete anything from mine. I don't format after every show as some seem to but I usually don't let it get much more than about half full.

When I spoke to Justin he said linux was unsupported and seemed a little surprised I was using it.  Perhaps we need to send some nice notes to SD just to let them know they have customers who prefer Linux.

ok... it was cold as hell this weekend, so I rolled up my sleeves and went kernel diving long into the nights... and I see what's going on with the "write protect" problem...

Freelunch, your cut and paste of the Mode Sense data above was a BIG help to zeroing in... so tanks.

here's a clue... turn your 78242977 hdwr sectors into hex (0x04 a9 e4 a1) and now compare that with your Mode Sense data  and this explains why my Mode Sense data is so different from yours, since I have a 80G drive in the 722.

I've bounced back and forth at least 6 times between thinking this is a linux or SD problem... mostly due to the totally insane SCSI specification docs... so I wanted to verify that your "write protect" problem started only after you upgraded the firmware on the 722... with no changes to your linux kernel... correct???

And if you guys could tell me the version of your 722 firmware and linux kernel (that either works or fails) that'd help a bunch also.

In the mean time, I've got a work around... but it ain't easy. Let me know if you need (or want) it.

[it-goes-to-eleven]

I am running the 1.60 firmware and the knoppix box I mount the 722 on is running 2.6.11.

Writing to the 722 worked fine until the upgrade. I know it worked because I was able to copy the new firmware over.

I shouldn't need to write to the 722 until the next firmware upgrade and I could always do that under windows. So it isn't a huge problem for me.  Though if SD doesn't know their changes are breaking stuff, maybe it won't work under linux at all in the next release..

[mmedley.]

You guys should post this info over on SD Forums to see if any other users might have feedback. Looks like good info to have and share.

+T

[Lil Kim Jong-Il]

OK, I have the unit here.  This is the log entry when the drive is attached:

ieee1394: Node added: ID:BUS[0-00:1023]  GUID[00121b00004ce783]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
scsi3 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
  Vendor: SoundDev  Model: 722  HDD          Rev:
  Type:   Direct-Access                      ANSI SCSI revision: 06
SCSI device sdc: 156301489 512-byte hdwr sectors (80026 MB)
SCSI device sdc: drive cache: write back, no read (daft)
 sdc: sdc1
Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi3, channel 0, id 0, lun 0,  type 0


When I attempt to mount the drive, I get:

FAT: bogus sectors-per-track value
VFS: Can't find a valid FAT filesystem on dev sdc1.

wtf?