\dev\null 22:10, 13 kovo 2026

2026-03-13T22:10:26Z

\dev\null 22:08, 13 kovo 2026

2026-03-13T22:08:45Z

\dev\null: /* Prijungimas Linux'e */

2026-03-10T22:48:04Z

Prijungimas Linux'e

\dev\null: Naujas puslapis: Vaizdas:Screenshot 2026-03-11 at 00.45.20.png G-Technology G-RAID Studio Thunderbolt 2 = Prijungimas Linux'e = Į /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT arba /etc/k...

2026-03-10T22:46:42Z

Naujas puslapis: Vaizdas:Screenshot 2026-03-11 at 00.45.20.png G-Technology G-RAID Studio Thunderbolt 2 = Prijungimas Linux'e = Į /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT arba /etc/k...

Naujas puslapis

[[Vaizdas:Screenshot 2026-03-11 at 00.45.20.png]]

G-Technology G-RAID Studio Thunderbolt 2

= Prijungimas Linux'e =

Į /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT arba /etc/kernel/cmdline rekia pridėti
iommu=pt

Pririšam thunderbolt'ą:
boltctl list
boltctl enroll <UUID>
Pvz.:
boltctl enroll 00000000-0000-0018-0004-d4032e54e050
Žiūrim ar atsiranda devaisas:
dmesg -w
Jeigu viskas ok ir buvo pakonfigytas ant JBOD, turėtų atsirasti diskai:
lsblk
Jeigu neatsirado toliau žiūrime dmesg kodėl..

== Papildoma info ==

c9:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11)
Controlleris taip pat exposina management console, kurios dar nepriveikiau...
lsscsi -g
[2:0:0:0] process Marvell Console 1.01 - /dev/sg2
apt install sg3-utils
sg_inq /dev/sg2

Standarinės siunčiamos komandos grąžina statusą failed. Reikia tolimesnio tyrimo.

= Reverse Engineered info =

Standartinis softas veikia kaip web aplikacija bet turi įrankį, kuris yra pacompilintas ant i386 ir tikrai ant naujų macOS neveiks, nebent turint seną macOS relyzą su mac'u kuriame yra TB2 portai galima pajungti ir išsiaškinti. Tas įrankis naudojamas backende atlikti visus juodus darbus, kuriuos vartotojas nurodo per tą web ui:
G-SPEED Studio Software Utility.app/Contents/Resources/XMLBase/cli_exeMod: Mach-O executable i386

'''Atvirkštine inžinerija išsiaiškinta šios detalės:'''

== G-SPEED Studio CLI Notes ==

This document explains how to use the bundled Promise/G-SPEED command line utility to:

* identify physical disks
* list physical disks
* map UI disk labels to CLI disk IDs
* change disk mode between ''unconfig'' and ''passthru''
* perform a few related physical-drive operations

It is based on the software bundle in this repository, especially:

* ''G-SPEED Studio Software Utility.app/Contents/Resources/XMLBase/cli_exeMod''
* the web UI code that calls physical-drive APIs

== Important terms ==

* '''PD ID''': Physical Drive ID used by backend/API/CLI operations.
* '''pdi_FlatId''': Internal drive ID field used by the web UI data model.
* '''PassThru''': What this software uses as the JBOD-like mode for a drive.
* '''Unconfigured''': A drive that is not currently passed through and not in an array.

== Important warning about numbering ==

There are two different representations in this software:

* Internal/backend ID: ''pdi_FlatId''
* Human-facing detail label: ''PD <id+1>''

That means:

* if the UI detail page says ''PD 1'', the backend ID may actually be ''0''
* if the physical drive list shows a raw numeric ID column, that raw numeric value is the one to trust for backend and CLI work

The web UI code confirms this:

* the physical drive list uses ''item.pdi_FlatId''
* the detail view displays ''PD '' plus ''getId()+1''

== Utility location ==

Bundled CLI binary:

<code bash>
"/Users/devnull/Projects/G-Drive/G-SPEED Studio Software Utility.app/Contents/Resources/XMLBase/cli_exeMod"
</code>

Short shell variable for convenience:

<code bash>
CLI="/Users/devnull/Projects/G-Drive/G-SPEED Studio Software Utility.app/Contents/Resources/XMLBase/cli_exeMod"
</code>

== Platform note ==

The bundled ''cli_exeMod'' in this repository is a Mach-O ''i386'' binary. On an ''arm64'' Mac it may not run directly unless the proper compatibility layer is available. The commands below document the intended usage from the bundled help text and the surrounding application code.

== How the software changes JBOD mode ==

The web UI does not call a special ''jbod'' command.

It changes a physical drive's configuration state through the backend method:

* ''setPhyDrvSettings''

When switching a drive into JBOD-like mode, it sets:

* ''pdsp_Flags = "PassThru"''

The equivalent CLI operation is:

<code bash>
$CLI phydrv -a mod -p <PD_ID> -s "config=passthru"
</code>

To switch back:

<code bash>
$CLI phydrv -a mod -p <PD_ID> -s "config=unconfig"
</code>

== Basic discovery workflow ==

Recommended order:

- List physical drives.
- Identify the correct ''PD ID''.
- Confirm whether the drive is already ''Unconfigured'' or ''PassThru''.
- Change the mode only for the target drive.
- Re-list drives to verify the new state.

== List physical drives ==

Basic listing:

<code bash>
$CLI phydrv
</code>

Explicit list action:

<code bash>
$CLI phydrv -a list
</code>

Verbose listing:

<code bash>
$CLI phydrv -v
</code>

List all SCSI devices instead of only disks:

<code bash>
$CLI phydrv -a list -l all
</code>

What to look for in output:

* Physical Drive ID
* model
* slot/location
* current status
* array membership
* current configuration status such as ''Unconfigured'' or ''PassThru''

== Identify the correct PD ID ==

=== From the web UI ===

Use the ''Physical Drives'' page.

The first numeric ID column comes from the raw internal field:

* ''pdi_FlatId''

That is the best candidate for CLI/API work.

Do not rely only on a detail screen label like ''PD 1'', because the detail screen may display ''id+1'' for humans.

=== From CLI output ===

Use:

<code bash>
$CLI phydrv -v
</code>

The bundled help text indicates the output includes physical drive information and refers to ''Physical Drive Id''.

Once you have the printed Physical Drive ID, use that exact number with ''-p''.

== Locate a drive physically ==

Blink the LED for one disk:

<code bash>
$CLI phydrv -a locate -p <PD_ID>
</code>

Example from the bundled help:

<code bash>
$CLI phydrv -a locate -p 9
</code>

Use this before changing mode if you need to confirm the exact tray/slot.

== Change a drive to JBOD-like mode ==

In this software, JBOD-like mode means ''PassThru''.

Command:

<code bash>
$CLI phydrv -a mod -p <PD_ID> -s "config=passthru"
</code>

Example:

<code bash>
$CLI phydrv -a mod -p 9 -s "config=passthru"
</code>

Expected use:

* drive should currently be ''Unconfigured''
* drive should not be part of an active array

After changing mode, verify:

<code bash>
$CLI phydrv -v
</code>

== Change a drive back from PassThru ==

To return a passed-through drive to ''Unconfigured'':

<code bash>
$CLI phydrv -a mod -p <PD_ID> -s "config=unconfig"
</code>

Example:

<code bash>
$CLI phydrv -a mod -p 9 -s "config=unconfig"
</code>

This is also what the web UI does when converting a ''PassThru'' disk back to ''Unconfigured''.

== Change drive alias ==

The CLI help says ''alias'' can only be set on a configured drive.

Example:

<code bash>
$CLI phydrv -a mod -p <PD_ID> -s "alias=MyDisk"
</code>

Do not assume alias changes are allowed in ''Unconfigured'' or ''PassThru'' state.

== Other physical-drive operations ==

Force a drive offline:

<code bash>
$CLI phydrv -a offline -p <PD_ID>
</code>

Force a drive online:

<code bash>
$CLI phydrv -a online -p <PD_ID>
</code>

Clear PFA:

<code bash>
$CLI phydrv -a clear -p <PD_ID> -t pfa
</code>

Clear stale config:

<code bash>
$CLI phydrv -a clear -p <PD_ID> -t staleconfig
</code>

These are riskier than listing/locating and should be used only when you are sure about the drive state.

== Global SATA/SAS drive settings ==

The CLI also supports global settings on SATA/SAS drives through ''phydrv -a mod'', for example:

<code bash>
$CLI phydrv -a mod -s "writecache=enable,rlacache=enable"
</code>

Drive-type-specific scope:

* ''-d sata''
* ''-d sas''
* ''-d all''

Examples:

<code bash>
$CLI phydrv -a mod -d sata -s "writecache=enable"
$CLI phydrv -a mod -d sas -s "readcache=enable,multipath=enable"
</code>

These are global settings for drives of that type, not a single-disk mode switch.

== Arrays and PD IDs ==

The CLI help for array creation uses PD IDs directly:

<code bash>
$CLI array -a add -p 1,3,5~9 -l "raid=5,capacity=50gb,stripe=256kb"
</code>

This matters because it confirms that:

* the same PD ID namespace is used across physical-drive and array commands
* the IDs you discover in ''phydrv'' are the IDs you would use when creating arrays

== Safe operating procedure ==

Before changing a disk to ''PassThru'':

- List all drives with ''phydrv -v''.
- Record the target drive's PD ID, slot, model, and current config state.
- If needed, run ''phydrv -a locate -p <PD_ID>'' to confirm the tray.
- Ensure the drive is not part of an active array you care about.
- Run ''phydrv -a mod -p <PD_ID> -s "config=passthru"''.
- Re-run ''phydrv -v'' and confirm the new state.

== Common examples ==

List drives:

<code bash>
$CLI phydrv -v
</code>

Locate drive 4:

<code bash>
$CLI phydrv -a locate -p 4
</code>

Convert drive 4 to PassThru:

<code bash>
$CLI phydrv -a mod -p 4 -s "config=passthru"
</code>

Convert drive 4 back to Unconfigured:

<code bash>
$CLI phydrv -a mod -p 4 -s "config=unconfig"
</code>

Clear stale configuration on drive 4:

<code bash>
$CLI phydrv -a clear -p 4 -t staleconfig
</code>

== What the web app code confirms ==

Relevant behavior found in the application code:

* Physical drive IDs come from ''pdi_FlatId''.
* UI detail display uses ''PD <id+1>''.
* The physical-drive settings panel offers ''Unconfigured'' and ''PassThru''.
* Saving those settings issues backend ''setPhyDrvSettings''.
* Advanced configuration code also toggles drives through ''setPhyDrvSettings''.

== Limitations of this note ==

* This document is based on bundled help text and code inspection.
* The ''cli_exeMod'' binary in this repository was not executed successfully on the current ''arm64'' host during this review.
* If you run this on the original supported platform, verify syntax with:

<code bash>
$CLI help phydrv
</code>

or:

<code bash>
$CLI phydrv -h
</code>

[[Category:Hardware]]
[[Category:Linux]]
[[Category:Mac OS X]]

← Ankstesnė versija		22:10, 13 kovo 2026 versija
455 eilutė:		455 eilutė:
	[[Category:Linux]]		[[Category:Linux]]
	[[Category:Mac OS X]]		[[Category:Mac OS X]]
		+	[[Category:ESP8266]]

← Ankstesnė versija		22:08, 13 kovo 2026 versija
30 eilutė:		30 eilutė:

	Standarinės siunčiamos komandos grąžina statusą failed. Reikia tolimesnio tyrimo.		Standarinės siunčiamos komandos grąžina statusą failed. Reikia tolimesnio tyrimo.
		+
		+
		+	= Auto power on hack'as =
		+
		+	Aparatas nepalaiko '''auto power on after power loss''', ar pan. konfigūracijos, todėl po elektros dingimo jį reikia įjungti rankiniu būdu kas labai nervuoja. Bet išeitis yra! Galima apgauti įjungimo mygtuką, kadangi jis yra aktyvus ir schema taip pat turi 5V išvestį, panaudojus [[esp8266]] mikrokontrolerį, galima jį įjungti automatiškai...
		+
		+	[[Vaizdas:Graid-auto-power-hack-IMG 8316.jpg\|700px]]
		+
		+	{\| class="wikitable"
		+	\|+ Sujungimas
		+	\|-
		+	! Board !! esp8266 !! Info
		+	\|-
		+	\| 5V \|\| 5V \|\|
		+	\|-
		+	\| GND \|\| GND \|\|
		+	\|-
		+	\| Power button \|\| D1 \|\| Gpio 5
		+	\|}
		+
		+	Supaprastinti kodą, panaudosime [https://esphome.io esphome]..
		+
		+	'''ESPHome''' konfigūracija:
		+	<syntaxhighlight lang="yaml">
		+	esphome:
		+	name: graid-power
		+	on_boot:
		+	priority: -100
		+	then:
		+	- delay: 1500ms
		+	- output.turn_on: pwrbtn
		+	- delay: 300ms
		+	- output.turn_off: pwrbtn
		+
		+	esp8266:
		+	board: d1_mini
		+
		+	logger:
		+
		+	output:
		+	- platform: gpio
		+	id: pwrbtn
		+	pin:
		+	number: GPIO5
		+	mode:
		+	output: true
		+	open_drain: true
		+	inverted: true
		+	</syntaxhighlight>
		+
		+	== Rezultatas ==
		+
		+	Gal ir nekaip atrodo bet veikia !
		+
		+	[[Vaizdas:Graid-auto-power-hack-IMG 8351.jpg\|600px]]
		+	[[Vaizdas:Graid-auto-power-hack-IMG 8352.jpg\|600px]]
		+	[[Vaizdas:Graid-auto-power-hack-IMG 8350.jpg\|600px]]

	= Reverse Engineered info =		= Reverse Engineered info =

@@ 6 eilutė: / 6 eilutė: @@
 = Prijungimas Linux'e =
-Į /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT arba /etc/kernel/cmdline rekia pridėti
+Į '''/etc/default/grub''' GRUB_CMDLINE_LINUX_DEFAULT eilutės galą arba '''/etc/kernel/cmdline''' (jeigu naudojamas [[EFI]] boot pvz ant Proxmox) reikia pridėti
   iommu=pt

G-RAID Studio - Versijų istorija

\dev\null 22:10, 13 kovo 2026

\dev\null 22:08, 13 kovo 2026

\dev\null: /* Prijungimas Linux'e */

\dev\null: Naujas puslapis: Vaizdas:Screenshot 2026-03-11 at 00.45.20.png G-Technology G-RAID Studio Thunderbolt 2 = Prijungimas Linux'e = Į /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT arba /etc/k...