Smoke 7 message "PARTITION MANAGER:testing speed disk

Home Page forums Autodesk/Discreet Flame and Smoke Smoke 7 message "PARTITION MANAGER:testing speed disk

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #203111
    Anonymous
    Inactive

    Hello to everyone
    We have an Smoke 7 .0.14 system build on an Octane 2 with IRIX 6.5.28 and 4 GB of RAM and an Octane’s Video option with MXE graphics card.Also the Octane2 has a cardcage with a QL12160 SCSI controller. Ours Stones are 2 old D1000 stone boxes with 6 stones 7200 RPM of 9GB each per box.These D1000 boxes always has been connected to the SCSI port of of this QL12160 SCSI controller. Smoke 7 starts perfectly and works OK everytimes.
    A few days ago I had to digitize a tape on a Pal Project that previously It has been created for me. I started Smoke, I login to the previously Pal project I created,then go to library,started the input clip module and digitize the clip and save it into the library.
    At this point all works fine but when I want to load the clip to the editdesk a message appears, it says- “PARTITION MANAGER:testing speed disk” and Smoke freezes.
    What can I do?
    Someone can help me to solve this or explain to me why this happens?
    Any help would be appreciated. Thank you to all

    #218334
    Shannon Gans
    Participant

    “PARTITION MANAGER:testing speed disk” should not cause any issues with a fully working system. It’s something smoke does frequently.

    Because the system hangs there I wonder if you have a disk starting to die in the array.

    There are several tools you can use to see what is happening.
    If you have the fronts on the d1000’s remove them and look at the lights. A lit disk light = no activity so you may find one disk without a light on, or a disk light goes out when it hangs.

    Run /usr/discreet/sw/tools/stone-test -r -f PAL do all of the disk lights flash together?

    Run up sw_config – do you have any sick or dead disks?

    Use /usr/discreet/sw/tools/sw_print_config.
    You will get something similar this:
    ./sw_print_config

    Number of Disks: 4

    [ 0] Serial:0228a921 A: 4 T: 0 L: 0 Status:FLRW Recovered: 0 Unrecovered: 0
    [ 1] Serial:0328a921 A: 4 T: 0 L: 1 Status:FLRW Recovered: 0 Unrecovered: 0
    [ 2] Serial:0028a921 A: 5 T: 0 L: 0 Status:FLRW Recovered: 0 Unrecovered: 0
    [ 3] Serial:0128a921 A: 5 T: 0 L: 1 Status:FLRW Recovered: 0 Unrecovered: 0

    Number of Partitions: 1

    Partition 0

    FS Id: 102
    Offset: 0
    Length: 853078016
    Capacity: 3412312064
    Bandwidth: 400
    FS I-node Size: 1024
    Number of Data Disks: 4
    Disks: 0 1 2 3
    No parity disks
    Number of Sick Disks: None
    Number of Dead Disks: None

    Have a look at the recovered and unrecovered error count for each disk. Are they both zero?

    If you have errors over many disks, are they all on one controller as it can also be a controller/cable fault.?

    Regards

    Chris
    Freelance Engineer

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.
Copy link
Powered by Social Snap