Linux cyberpanel 5.15.0-156-generic #166-Ubuntu SMP Sat Aug 9 00:02:46 UTC 2025 x86_64
LiteSpeed
: 160.191.175.3 | : 216.73.216.114
Cant Read [ /etc/named.conf ]
8.2.29
aodai6801
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
sg3-utils /
examples /
[ HOME SHELL ]
Name
Size
Permission
Action
archive
[ DIR ]
drwxr-xr-x
Makefile
3.08
KB
-rw-r--r--
Makefile.freebsd
1.98
KB
-rw-r--r--
README
776
B
-rw-r--r--
forwarded_sense.txt
296
B
-rw-r--r--
nvme_dev_self_test.hex
806
B
-rw-r--r--
nvme_identify_ctl.hex
1.17
KB
-rw-r--r--
nvme_read_ctl.hex
1.79
KB
-rw-r--r--
nvme_write_ctl.hex
1.8
KB
-rw-r--r--
reassign_addr.txt
465
B
-rw-r--r--
ref_sense.txt
305
B
-rw-r--r--
scsi_inquiry.c
4.09
KB
-rw-r--r--
sdiag_sas_p0_cjtpat.txt
405
B
-rw-r--r--
sdiag_sas_p0_prbs9.txt
407
B
-rw-r--r--
sdiag_sas_p1_cjtpat.txt
464
B
-rw-r--r--
sdiag_sas_p1_idle.txt
560
B
-rw-r--r--
sdiag_sas_p1_prbs15.txt
408
B
-rw-r--r--
sdiag_sas_p1_stop.txt
359
B
-rw-r--r--
sg__sat_identify.c
7.55
KB
-rw-r--r--
sg__sat_phy_event.c
12.02
KB
-rw-r--r--
sg__sat_set_features.c
9.7
KB
-rw-r--r--
sg_compare_and_write.txt
2.42
KB
-rw-r--r--
sg_excl.c
5.98
KB
-rw-r--r--
sg_persist_tst.sh
3.54
KB
-rwxr-xr-x
sg_sat_chk_power.c
8.95
KB
-rw-r--r--
sg_sat_smart_rd_data.c
6.4
KB
-rw-r--r--
sg_simple1.c
5.87
KB
-rw-r--r--
sg_simple16.c
3.41
KB
-rw-r--r--
sg_simple2.c
6.59
KB
-rw-r--r--
sg_simple3.c
6.46
KB
-rw-r--r--
sg_simple4.c
7.25
KB
-rw-r--r--
sg_simple5.c
7.47
KB
-rw-r--r--
sg_unmap_example.txt
1.53
KB
-rw-r--r--
sgq_dd.c
37.77
KB
-rw-r--r--
transport_ids.txt
1.1
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : nvme_read_ctl.hex
# 64 byte NVMe, Read command (a NVM command) that is suitable for: # sg_raw --cmdfile=<this_file_name> --nvm --request=2048 <nvme_device> # # The address field (at byte offset 24, 8 bytes and little endian) gives # special meaning to the highest address pointers: # ffffffff fffffffe use address of data-in buffer # ffffffff fffffffd use address of data-out buffer # # The data length field (at byte offset 36, 4 bytes and little endian) # gives special meaning to the highest block counts: # fffffffe use byte length of data-in buffer # fffffffd use byte length of data-out buffer # # 512 byte logical block size is assumed. Read 4 blocks hence 2048bytes. # The first LBA read is 0x12345 and the namespace is 1. If successful # the four blocks will be read into the data-in buffer. Submission queu # 0 is used (the same queue that Admin commands use). The NVM opcode for # the Read command is 0x2 and appears in the first command byte. 02 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe ff ff ff ff ff ff ff 00 00 00 00 fe ff ff ff 45 23 01 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 # Notice NVMe uses its quirky "0's based" number of blocks so # 03 appears at byte offset 48 to mean "read 4 blocks". # # A typical invocation in Linux and FreeBSD would look like this: # sg_raw --cmdfile=nvme_read_ctl.hex --nvm -r 2048 # --outfile=t.bin /dev/nvme0 # # Notice the '--nvm' option which is needed to distiguish a NVM # command from an Admin command as Admin commands are the default # in this utility. # # This utility (and most others in the package) aligns data-in and # data-out buffers to the beginning of pages which are 4096 bytes # long at a minimum. This is the way NVMe likes things as well.
Close