I have an 040 cube with NextStep 3.3 installed on a SCSI2SD. It starts up and functions fine. When I hit the power button to shut down I get the options to Log Out or Power Off. When I click Power Off the shutdown window goes away immediately, but it takes 15-20 minutes until the dock goes away. I've waited up to 30 minutes past that point for it to shut down on its own without success.
Alt+Command+* does force reboot the computer okay.
Using 'halt' in NMI also works okay.
Is there something I can do to determine what is preventing a normal shutdown? Is this delay typical when using SCSI2SD?
Hello: A few questions do you have networking set up? What is the speed of your sd card? The Extreme Pro cards verse regular SD cards make huge a difference in terms of performance and shut down.
The card is a SanDisk Edge 16GB Micro SD HC I (4)
https://www.amazon.com/gp/product/B00FZVQPBC/ref=oh_aui_search_asin_title?ie=UTF8&psc=1I do have a network config, but the cube is not attached to my network at the moment. If I disconnect it from the network physically, do I need to remove the internet config settings?
EDIT: I changed from local domain to netinfo. It gets rid of the dock much more quickly but still hangs at the gray screen and doesn't shut down.
I switched to a SanDisk Pro Extreme card and still have the same symptom. It goes to the gray screen quickly, but doesn't shut down. I waited about four minutes. Anything else I can try?
I would suggest checking your SCSI cable. Which SCSI2SD version? Have you updated to the latest firmware?
Quote from: barcher174 on May 14, 2019, 09:12:55 PMI would suggest checking your SCSI cable. Which SCSI2SD version? Have you updated to the latest firmware?
The SCSI2SD is 5.0b. I updated the firmware when I installed the card a couple months ago. It looks like the latest firmware available is from 2018 so I should be up to date.
Everything else works okay otherwise and it shut down normally when I had the original HDD connected. The cable seems unlikely.
Also, the hang is the same when I just try to log out rather than shut down. It goes to a gray screen pretty quickly and then hangs there.
Is there a way to monitor the shutdown process to see where it's getting stuck? Or is there a log somewhere that might have that info?
Update:
I opened the NMI console (cmd+cmd+~) and typed msg while the cube was hung at the grey screen. I see the following looping. Does this just mean a bad sector on the disk? Why would that be the case on both cards? Anything I can do to repair it?
I did try running fsck, but it checks out okay.
nmi> msg
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
IO error on pageout: error = 5.
vnode_pageout: failedTarget 0: NOT READY; retry 1!
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
Target 0: NOT READY; retry 4
Target 0: NOT READY; retry 5
Target 0: NOT READY; retry 6
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
Target 0: NOT READY; retry 1
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
Target 0: NOT READY; retry 4
Target 0: NOT READY; retry 5
Target 0: NOT READY; retry 6
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
Target 0: NOT READY; retry 1
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
Target 0: NOT READY; retry 4
Target 0: NOT READY; retry 5
Target 0: NOT READY; retry 6
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
Target 0: NOT READY; retry 1
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
Target 0: NOT READY; retry 4
Target 0: NOT READY; retry 5
Target 0: NOT READY; retry 6
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
IO error on pageout: error = 5.
vnode_pageout: failedTarget 0: NOT READY; retry 1!
Target 0: NOT READY; retry 1
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
Target 0: NOT READY; retry 4
Target 0: NOT READY; retry 5
Target 0: NOT READY; retry 6
Target 0: NOT READY; retry 7
Target 0: NOT READY; retry 8
Target 0: NOT READY; retry 9
Target 0: NOT READY; retry 10
Target 0: NOT READY; retry 11
Target 0: NOT READY; retry 12
Target 0: NOT READY; retry 13
Target 0: NOT READY; retry 14
Target 0: NOT READY; retry 15
Target 0: NOT READY; retry 16
Target 0: NOT READY; retry 17
Target 0: NOT READY; retry 18
Target 0: NOT READY; retry 19
sd0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656
Target 0: NOT READY; retry 1
Target 0: NOT READY; retry 2
Target 0: NOT READY; retry 3
nmi>
Can you post your scsi2sd config file? you might have an issue with the drive definition
Quote from: evolver56k on May 16, 2019, 12:30:05 PMCan you post your scsi2sd config file? you might have an issue with the drive definition
Here's the current config:
https://pastebin.com/RLXL7kU3
Hello: How are you doing the installation of NeXTSTEP 3.3 to the scsi2sd? Is it from using a saved Drive or ISO image using the DD (disk duplicate command) using terminal.app utility on MACOS X then copying the saved image to your sd. Then booting that newly created sd on your NeXT ? Or is the image on the SD from an original NeXTSTEP3.3 CD install or using buildisk from your original hard drive?
What happens if you choose to logout first then power off from the login screen? Do you have the password set for the me account so when you logout you have a login screen appear and can login as root or me ? If when you boot up it goes directly into the operating system , you need to set up a password for me , using the calendar icon , click to open preferences , click the padlock in the preferences panel , set the password.
So it lloks like error is referring d0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656 to a bad sector on your sd card, this may be an artifact from a previous install say on older hard drive then moving data to your new sd drive.
When you format the sd card does it give any errors for example using MACOSX utilities Master Boot Record Fat32?
What is your current set up .... as it gives us a starting point.....
What drive do you have jumper to be SCSI ID 0 ?
Do you currently have a hard drive ?,+ SD drive ? CDrom Drive? Floppy Drive? on your Cube?
Quote from: Rob Blessin Black Hole on May 16, 2019, 03:18:38 PMHello: How are you doing the installation of NeXTSTEP 3.3 to the scsi2sd? Is it from using a saved Drive or ISO image using the DD (disk duplicate command) using terminal.app utility on MACOS X then copying the saved image to your sd. Then booting that newly created sd on your NeXT ? Or is the image on the SD from an original NeXTSTEP3.3 CD install or using buildisk from your original hard drive?
I created a CD and floppy drive partition on the SCSI2SD, DD'd the installation disk images to those and installed onto SCSI ID0 HD partition.
Quote from: undefinedWhat happens if you choose to logout first then power off from the login screen?
It hangs at the grey screen indefinitely just like a shut down.
Quote from: undefinedDo you have the password set for the me account so when you logout you have a login screen appear and can login as root or me ?
I've only been using root. I don't think I have another user account set up but will check.
UPDATE: I do have a me account but haven't been using it. Should that make a difference?
Quote from: undefinedIf when you boot up it goes directly into the operating system , you need to set up a password for me , using the calendar icon , click to open preferences , click the padlock in the preferences panel , set the password.
It boots to a login screen. I log in as root.
Quote from: undefinedSo it lloks like error is referring d0 (0,0) sense key:0x2 additional sense code: 0x4
SCSI Block in error = 2285632; Partition a F.S. sector 1142656 to a bad sector on your sd card, this may be an artifact from a previous install say on older hard drive then moving data to your new sd drive.
It's a fresh install.
Quote from: undefinedWhen you format the sd card does it give any errors for example using MACOSX utilities Master Boot Record Fat32?
It didn't when it was new, but I haven't formatted it since installing NeXTStep
Quote from: undefinedWhat is your current set up .... as it gives us a starting point.....
What drive do you have jumper to be SCSI ID 0 ?
Do you currently have a hard drive ?,+ SD drive ? CDrom Drive? Floppy Drive? on your Cube?
The optical drive is plugged into power, but disconnected from SCSI. If it's not plugged into power, the machine won't turn on.
The HDD was removed, but worked okay when it was installed. It was just old, loud and sounded like it was dying.
The SCSI2SD is plugged into the SCSI bus that the HDD was on. I didn't change jumper settings on the SCSI2SD or MLB. SCSI2SD is configured with ID0=HDD, ID1=HDD, ID2=Floppy, ID3=CDROM.
Nothing is plugged into the external SCSI bus.
Hello: By the way ....this is genius: I created a CD and floppy drive partition on the SCSI2SD, DD'd the installation disk images to those and installed onto SCSI ID0 HD partition.
I'm trying this method for install and has my wheels turning.... doh, I always use an actual not virtual floppy drive and CDrom drive but this virtual foo rocks.
I wonder if you reassign the block , if that will clear up the error then let it shut down? As it appears something is causing it to hang. SCSI Block in error = 2285632; Partition a F.S. sector 1142656
Best Regards Rob Blessin
Are you using the molex power cable to supply power to the scsi2sd, or just using power supplied via the scsi cable?
I have a v5.0b in my turboslab that doesn't have this issue, connected with 5v power. I also have a v5.0 in a MacSE only using scsi cable supplied power.
I'm not sure if there's a difference in the cube vs slab in whether or not you need to supply extra power to the board, if that's your setup
Hmm, I've been getting similar hangs during regular operation of my 040 Cube as well and continue to search for a solution.
I guess I'd like to get a better understanding of what this error message really means—rather than just get a working config to really get to the bottom of what's going on.
Essentially right after boot up after I install NextStep 3.3 on the SCSI ID 0 disk, once I acknowledge some errors about disks being unreadable (such as the floppy), /tmp/console.log output indicates:
sd0 (0,0): sense key:0x2 additional sense code:0x4
SCSI Block in error = 2276528; Partition a F.S. sector 1138104
along with a bunch of "Target 0: NOT READY; retry <x>" errors.
I've tried a couple of different drive geometries, such as one config file reported working here from the forums, as well as looking up specs from some old Seagate drives and configuring the geometry (sectorsPerTrack, headsPerCylinder) to match the real physical devices. I am using a SCSI2SD v6, with latest firmware, and powering it via the molex connector.
I always seem to be able to get through a complete install of the basic NextStep 3.3 (using the same SCSI2SD with partitions for a floppy and CD), but then hit these SCSI errors. The numbers change per configuration, but it's always the same kind of failure.
Further I've tried to add "padding" between the allocated devices on the SCSI2SD, but that didn't seem to make a difference.
Did you try the active termination jumper on the scsi2sd?
I tried removing the active termination jumpers and just got a SCSI bus error on boot.
I noticed that if I don't log in, I can restart or shutdown from the login screen okay. Restart/Shutdown from the login screen takes ~20 seconds.
I checked my config again and it seems inline with what others have said works ok.
I am powering via the molex connector, but that seems fine too. It's not like I suddenly lose power or have other unexpected errors. It's only when I go to shut down. I'll try powering it via USB instead for the heck of it though. IIRC, Joey's *is*powered via USB.
Any other suggestions?
Hello NeXT Community: From a NeXT hardware/ software factory engineer :
Comments for "NeXTStep 3.3 on an 040 cube won't shut down" completely with SCSI Target Not Ready, Sense Key 0x2, Additional Sense Code 0x4 errors seen.
SCSI Sense Key 0x2 is "NOT READY". SCSI ASC 0x4 is "LOGICAL UNIT NOT READY".
These keys and codes are generated by the SCSI Target device, in this case the SCSI2SD and its firmware.
This is the firmware on the SCSI2SD reporting back to the SCSI initiator (the NeXT sd/sc driver) that the target is not ready for some reason. The NeXT driver waits then retries. If the target device never becomes ready then things will just hang.
Given that the error is device firmware generated and happens only at shutdown, the cause is unlikely related to termination or power issues. It's more likely related to issues with device state handling in the SCSI2SD firmware, perhaps tickled by SCSI START STOP UNIT commands sent by the NeXT system around shutdown.
I'd suspect the SCSI hang mentioned in the thread is a SCSI2SD firmware device/lun state housekeeping issue and not a speed issue with a slower sd card. The 20+ retries the NeXT SCSI driver uses give plenty of time for any reasonable device. The SCSI2SD device firmware is likely endlessly reporting not ready because of the setting of a device state flag.
Some (all?) of the source for SCSI2SD firmware appears to be online. Note the device state checks in its doTestUnitReady() function along with the errors it returns:
http://www.codesrc.com/gitweb/index.cgi?p=SCSI2SD.git;a=blob_plain;f=software/SCSI2SD/src/disk.c Additionally, one of the posts in the thread mentioned that the hang isn't seen when powering down or restarting from the login screen (as opposed to restarting or powering down when being logged in). This suggests the difference has nothing to do with the speed of the card media in the device, but instead could be related to the non-root devices configured on the SCSI2SD device. When the user logs in, additional devices get accessed and their filesystems mounted. Since those additional devices are configured to emulate a floppy or CD, they're reported and mounted as removable SCSI devices. Removable SCSI devices get sent SCSI START STOP UNIT commands at NeXT shutdown so the media can be ejected from a typical SCSI device. The SCSI2SD firmware's handling of device state and START/STOP UNIT commands could be a fruitful area to investigate and debug
While the longer term solution likely requires changes to the SCSI2SD firmware (since NS3.3 isn't going to change), there may be a possible workaround that avoids triggering the issue. That is if the issue does relate to the handling of emulated *removable* type SCSI devices on the SCSI2SD device, then just don't configure the SCSI2SD device to emulate removable SCSI devices (ie floppies or CDs). Instead configure the "floppy" or "CD" devices to be non-removable type 0 "disk" devices of the same size as the "floppy" or "CD" you want. (i.e. perhaps test out replacing any device types of 1, 2 and 3 in the config with type 0 device of the same ("floppy" or "CD") size in the config file.)
Also a quick glance though the SCSI2SD firmware code makes it appear there's no great reason to configure a SCSI2SD "floppy" device "3" when using a SCSI2SD with NeXTStep. Configuring a floppy device on the SCSI2SD just slows things down to the device by inserting wait states.
Good luck.
I had the same issue on a Nextstation turbo. Closing session or shutdown were hanging all the time (no new login prompt).
By just deactivating the floppy disk emulation in scsci2sd, it works fine now.
Thanks for the help,
Quote from: elemenoh on May 15, 2019, 11:39:21 AMThe SCSI2SD is 5.0b. I updated the firmware when I installed the card a couple months ago. It looks like the latest firmware available is from 2018 so I should be up to date.
This is factually inaccurate. There were two firmware revisions for SCSI2SD V5.x in 2019, the latest of which, 4.8.4, was released on December 9th of 2019. Please ensure you are using 4.8.4. You can download it from www.scsi2sd.com/v5/files/v4.8.4/firmware (
http://www.scsi2sd.com/v5/files/v4.8.4/firmware)