damox's rambling http://blog.damox.net !? Sat, 14 Jan 2012 02:54:43 +0000 en-US hourly 1 http://wordpress.org/?v=3.5.1 Oracle Solaris 11 (11/11) – Replacing a Bad Drive (ZFS) http://blog.damox.net/?p=171 http://blog.damox.net/?p=171#comments Sat, 14 Jan 2012 02:53:27 +0000 damox http://blog.damox.net/?p=171 Continue reading →]]> This is just a quick post to show the process I took to replace a degraded drive from my pool.

First; lets have a look at the pool showing the degraded drive.

damox@Starburst:~$ zpool status tank
[...]
        NAME         STATE     READ WRITE CKSUM
        tank         DEGRADED     0     0     0
          raidz2-0   ONLINE       0     0     0
            c6t12d0  ONLINE       0     0     0
            c6t11d0  ONLINE       0     0     0
            c6t13d0  ONLINE       0     0     0
            c6t14d0  ONLINE       0     0     0
            c4t25d0  ONLINE       0     0     0
            c4t26d0  ONLINE       0     0     0
            c4t27d0  ONLINE       0     0     0
            c4t28d0  ONLINE       0     0     0
            c3t17d0  ONLINE       0     0     0
            c3t18d0  ONLINE       0     0     0
          raidz2-1   DEGRADED     0     0     0
            c3t19d0  ONLINE       0     0     0
            c3t20d0  ONLINE       0     0     0
            c6t35d0  ONLINE       0     0     0
            c6t36d0  ONLINE       0     0     0
            c6t37d0  DEGRADED     0     0     0 too many errors
            c6t38d0  ONLINE       0     0     0
            c4t29d0  ONLINE       0     0     0
            c4t30d0  ONLINE       0     0     0
            c4t31d0  ONLINE       0     0     0
            c4t32d0  ONLINE       0     0     0
        cache
          c3t33d0    ONLINE       0     0     0
[...]

We identify the problem drive (in this case a drive that has too many errors + failed to resilver) and set it to OFFLINE so that no further read/write attempts are made to it.

In this case c6t37d0 is degraded and will be set to OFFLINE.

damox@Starburst:~$  zpool offline tank c6t37d0
[...]
        NAME         STATE     READ WRITE CKSUM
        tank         DEGRADED     0     0     0
          raidz2-0   ONLINE       0     0     0
            c6t12d0  ONLINE       0     0     0
            c6t11d0  ONLINE       0     0     0
            c6t13d0  ONLINE       0     0     0
            c6t14d0  ONLINE       0     0     0
            c4t25d0  ONLINE       0     0     0
            c4t26d0  ONLINE       0     0     0
            c4t27d0  ONLINE       0     0     0
            c4t28d0  ONLINE       0     0     0
            c3t17d0  ONLINE       0     0     0
            c3t18d0  ONLINE       0     0     0
          raidz2-1   DEGRADED     0     0     0
            c3t19d0  ONLINE       0     0     0
            c3t20d0  ONLINE       0     0     0
            c6t35d0  ONLINE       0     0     0
            c6t36d0  ONLINE       0     0     0
            c6t37d0  OFFLINE      0     0     0
            c6t38d0  ONLINE       0     0     0
            c4t29d0  ONLINE       0     0     0
            c4t30d0  ONLINE       0     0     0
            c4t31d0  ONLINE       0     0     0
            c4t32d0  ONLINE       0     0     0
        cache
          c3t33d0    ONLINE       0     0     0
[...]

Next I turned off the server and physically replaced the drive (after some pain physically located the drive. Note to self: label you drives/ports next time chump).

Using the ‘format’ command we get a list of available drives, knowing which drive is which I can identify the drive to be replacing the previously degraded one.

In this case c6t45d0 is the new drive to replace c6t37d0 (degraded).

root@Starburst:~# format
[...]
AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <ATA-WDC WD1500HLFS-0-4V02 cyl 18238 alt 2 hd 255 sec 63>
          /pci@0,0/pci10de,815@2/pci1014,394@0/sd@0,0
       [...]
      20. c6t38d0 <ATA-WDC WD20EARX-00P-AB51-1.82TB>
          /pci@0,0/pci10de,377@18/pci1014,394@0/sd@26,0
      21. c6t45d0 <ATA-WDC WD20EARX-00P-AB51 cyl 60798 alt 2 hd 255 sec 252>
          /pci@0,0/pci10de,377@18/pci1014,394@0/sd@2d,0
[...]

Using the replace command (zpool replace [-f] pool old_device [new_device]) we set c6t45d0 to replace c6t37d0.

Then we checkout the status of the pool to see the effect.

root@Starburst:~# zpool replace tank c6t37d0 c6t45d0
root@Starburst:~# zpool status tank
[...]
        NAME             STATE     READ WRITE CKSUM
        tank             DEGRADED     0     0     0
          raidz2-0       ONLINE       0     0     0
            c6t12d0      ONLINE       0     0     0
            c6t11d0      ONLINE       0     0     0
            c6t13d0      ONLINE       0     0     0
            c6t14d0      ONLINE       0     0     0
            c4t25d0      ONLINE       0     0     0
            c4t26d0      ONLINE       0     0     0
            c4t27d0      ONLINE       0     0     0
            c4t28d0      ONLINE       0     0     0
            c3t17d0      ONLINE       0     0     0
            c3t18d0      ONLINE       0     0     0
          raidz2-1       DEGRADED     0     0     0
            c3t19d0      ONLINE       0     0     0
            c3t20d0      ONLINE       0     0     0
            c6t35d0      ONLINE       0     0     0
            c6t36d0      ONLINE       0     0     0
            replacing-4  DEGRADED     0     0     0
            c6t37d0      OFFLINE      0     0     0
            c6t45d0      ONLINE       0     0     0 (resilvering)
            c6t38d0      ONLINE       0     0     0
            c4t29d0      ONLINE       0     0     0
            c4t30d0      ONLINE       0     0     0
            c4t31d0      ONLINE       0     0     0
            c4t32d0      ONLINE       0     0     0
        cache
          c3t33d0        ONLINE       0     0     0
[...]

After the resilvering process is complete (took me roughly 12 hours) we check the status again to see the effect.

root@Starburst:~# zpool status tank
[...]
        NAME         STATE     READ WRITE CKSUM
        tank         ONLINE       0     0     0
          raidz2-0   ONLINE       0     0     0
            c6t12d0  ONLINE       0     0     0
            c6t11d0  ONLINE       0     0     0
            c6t13d0  ONLINE       0     0     0
            c6t14d0  ONLINE       0     0     0
            c4t25d0  ONLINE       0     0     0
            c4t26d0  ONLINE       0     0     0
            c4t27d0  ONLINE       0     0     0
            c4t28d0  ONLINE       0     0     0
            c3t17d0  ONLINE       0     0     0
            c3t18d0  ONLINE       0     0     0
          raidz2-1   ONLINE       0     0     0
            c3t19d0  ONLINE       0     0     0
            c3t20d0  ONLINE       0     0     0
            c6t35d0  ONLINE       0     0     0
            c6t36d0  ONLINE       0     0     0
            c6t45d0  ONLINE       0     0     0
            c6t38d0  ONLINE       0     0     0
            c4t29d0  ONLINE       0     0     0
            c4t30d0  ONLINE       0     0     0
            c4t31d0  ONLINE       0     0     0
            c4t32d0  ONLINE       0     0     0
        cache
          c3t33d0    ONLINE       0     0     0
[...]

You could scrub the pool now to check for errors (which you should be doing anyway – “If you have consumer-quality drives, consider a weekly scrubbing schedule. If you have datacenter-quality drives, consider a monthly scrubbing schedule. — ZFS Best Practices Guide“

]]> http://blog.damox.net/?feed=rss2&p=171 2 Oracle Solaris 11 (11/11) – VNC http://blog.damox.net/?p=138 http://blog.damox.net/?p=138#comments Sat, 10 Dec 2011 05:07:44 +0000 damox http://blog.damox.net/?p=138 Continue reading →]]> This guide will cover how to setup a basic VNC connection to a Solaris 11 machine. There is also an optional step to allow for persistent VNC connections.

Step 1
Configure GDM to include ‘[security] DisallowTCP=false’ and ‘[xdmcp] Enable=true’.

$ sudo gedit /etc/gdm/custom.conf

# GDM configuration storage

[daemon]

[security]
DisallowTCP=false

[xdmcp]
Enable=true

[greeter]

[chooser]

[debug]

Step 2
Configure X-Server to accept remote connections.

$ sudo svccfg -s application/x11/x11-server
svc:/application/x11/x11-server> setprop options/tcp_listen = boolean: true
svc:/application/x11/x11-server> end

Step 3
Configure the VNC service (you could change the ‘-geometry 1280×720′ to whatever resolution you would like).

$ sudo svccfg -s xvnc-inetd
svc:/application/x11/xvnc-inetd> setprop inetd_start/exec = astring: "/usr/bin/Xvnc -geometry 1280x720 -inetd -query localhost -once securitytypes=none"
svc:/application/x11/xvnc-inetd> setprop inetd/wait = boolean: true
svc:/application/x11/xvnc-inetd> end

** The line highlighted red is optional – only do this if you want your VNC connection to persist (as well as any potential security issues)

Step 4
Disable and the re-enable the GDM and VNC-inetd services for the changes to take effect.

$ su root
Password:
# svcadm disable gdm xvnc-inetd; svcadm enable gdm xvnc-inetd

Step 5
Point your favourite VNC client at your Solaris server and test if it accepts your VNC connection – you should be presented with a Username/Password login screen.

If you performed the optional step to make your connections persist – close your favourite VNC client and then reconnect – if you remained logged in you have a persistent connections.

]]> http://blog.damox.net/?feed=rss2&p=138 10 Oracle Solaris 11 (11/11) – Sickbeard + SABnzbd Install (Advanced) http://blog.damox.net/?p=118 http://blog.damox.net/?p=118#comments Sat, 10 Dec 2011 04:52:10 +0000 damox http://blog.damox.net/?p=118 Continue reading →]]> Following up on the basic install of Sickbeard and SABnzbd this guide will cover how to install SickBeard and SABnzbd as services so that they start automatically at Solaris start-up.

This guide was done on a fresh install of Oracle Solaris 11 (11/11) – (get it here) – with a basic install performed according to this.

Step 1
Save these two XML documents somewhere:

sabnzbd.xml
sickbeard.xml

** This guide assumes the username: USERNAME the group: other and the install directory: /opt/Sickbeard/ and ‘/opt/SABnzbd/‘ however you can change all of these in the XML documents yourself.

Step 2
Move the XML documents to the ‘/var/svc/manifest/site/’ directory.

$ sudo cp sabnzbd.xml /var/svc/manifest/site/sabnzbd.xml
$ sudo cp sickbeard.xml /var/svc/manifest/site/sickbeard.xml

Step 3
Import the XML documents.

$ sudo svccfg import /var/svc/manifest/site/sabnzbd.xml
$ sudo svccfg import /var/svc/manifest/site/sickbeard.xml

Step 4
Enable the services.

$ sudo svcadm enable sabnzbd
$ sudo svcadm enable sickbeard

Step 5
Verify your logs.

Sickbeard log: ‘/var/svc/log/network-sickbeard:default.log’
[ Dec 10 16:57:47 Enabled. ]
[ Dec 10 16:58:02 Executing start method ("/opt/SickBeard.py --daemon"). ]
[ Dec 10 16:58:04 Method "start" exited with status 0. ]

SABnzbd log: ‘/var/svc/log/network-sabnzbd:default.log’
[ Dec 10 16:57:47 Enabled. ]
[ Dec 10 16:58:02 Executing start method ("/usr/bin/python2.6 /opt/SABnzbd.py -d -f /export/home/USERNAME/.sabnzbd/sabnzbd.ini"). ]
[ Dec 10 16:58:04 Method "start" exited with status 0. ]

Step 6
Reboot and try to visit the respecitve local addresses to see if the service is running and accessible (without you explicitly starting them first).

http://localhost:8080 <--- SABnzbd (replace localhost with the server IP if necessary - Protip: SABnzbd has to be configured from localhost before network access is allowed)
http://localhost:8081 <— Sickbeard (replace localhost with the server IP if necessary)

]]> http://blog.damox.net/?feed=rss2&p=118 7 Oracle Solaris 11 (11/11) – Sickbeard + SABnzbd Install (Basic) http://blog.damox.net/?p=95 http://blog.damox.net/?p=95#comments Sat, 10 Dec 2011 03:32:15 +0000 damox http://blog.damox.net/?p=95 Continue reading →]]> This guide will cover how to install SickBeard and SABnzbd including any dependencies you need to get up and running.

This guide was done on a fresh install of Oracle Solaris 11 (11/11) – Get it here.

Step 1: Install Everything
GNU
$ sudo pkg install developer/gnu

unrar v3.8.5
$ sudo pkg install archiver/unrar

Cheetah v2.4.4
$ cd /home/USERNAME/Downloads/
$ wget http://pypi.python.org/packages/source/C/Cheetah/Cheetah-2.4.4.tar.gz
$ tar -zxvf Cheetah-2.4.4.tar.gz
$ cd Cheetah-2.4.4
$ sudo python2.6 setup.py install

yenc v0.3
$ cd /home/USERNAME/Downloads/
$ wget http://www.golug.it/pub/yenc/yenc-0.3.tar.gz
$ tar -zxvf yenc-0.3.tar.gz
$ cd yenc-0.3
$ sudo python2.6 setup.py install

par2 v0.4
$ cd /home/USERNAME/Downloads/
$ wget http://downloads.sourceforge.net/project/parchive/par2cmdline/0.4/par2cmdline-0.4.tar.gz
$ tar -zxvf par2cmdline-0.4.tar.gz
$ cd par2cmdline-0.4
$ vi reedsolomon.cpp

Execute the following in vi to fix reedsolomon.cpp for Solaris (x64 only?).
:%s/^bool ReedSolomon/template <> bool ReedSolomon/g
Execute the following in vi to save and quit.
:wq

$ ./configure --prefix=/usr
$ make
$ sudo make install

Sickbeard
$ cd /opt
$ sudo git clone git://github.com/midgetspy/Sick-Beard.git Sickbeard
$ sudo chown -R USERNAME Sickbeard/

SABnzbd v0.6.12
$ cd /home/USERNAME/Downloads/
$ wget http://downloads.sourceforge.net/project/sabnzbdplus/sabnzbdplus/sabnzbd-0.6.12/SABnzbd-0.6.12-src.tar.gz
$ tar -zxvf SABnzbd-0.6.12-src.tar.gz
$ sudo mv SABnzbd-0.6.12/ /opt/SABnzbd/
$ sudo chown -R USERNAME /opt/SABnzbd/

Step 2: Run Everything
Running Sickbeard
$ cd /opt/Sickbeard/
$ python2.6 SickBeard.py

Running SABnzbd
$ cd /opt/SABnzbd/
$ python2.6 SABnzbd.py

After executing either Sickbeard or SABnzbd’s python script you should be presented with their respective web interface. There are numerous guides to help if you need further instructions for configuration.

To make Sickbeard and/or SABnzbd run as a service at start-up for Solaris see the advance setup entry here

SABnzbd should give an output similar to the following (which will show we have setup the dependencies correctly):

[...][SABnzbd:390] _yenc module... found!
[...][SABnzbd:398] par2 binary... found (/usr/bin/par2)
[...][SABnzbd:406] unrar binary... found (/usr/bin/unrar)
[...][SABnzbd:411] unzip binary... found (/usr/bin/unzip)
[...][SABnzbd:417] nice binary... found (/usr/gnu/bin/nice)
[...][SABnzbd:423] ionice binary... NOT found!
[...][SABnzbd:426] pyOpenSSL... found (True)

]]> http://blog.damox.net/?feed=rss2&p=95 5 PS3.Full.3.60.SDK.PS3-JoHNAaRoN http://blog.damox.net/?p=73 http://blog.damox.net/?p=73#comments Wed, 07 Sep 2011 03:03:09 +0000 damox http://blog.damox.net/?p=73 Continue reading →]]> The full 3.60 SDK includes what is listed below (The JoHNAaRoN release includes the entries indicated with a ** – What JoHNAaRoN is missing is highlighted red)

While it doesn’t appear to include the complete offline installer – it does include a whole load of documentation in the /dox/ folder: File Listing + Hash (stripped .gif .jpg .png)

It also includes some Extras  ;)

**[1]-manifest
[2]-token
**[3]-Public-Cell_Doc-Apr2007-English.zip
[4]-Cell_HW_Doc-21_English.zip
**[5]-RSX-HW_Doc-16_English.zip
**[6]-NP_Dev-Users_Guide_e.pdf
**[7]-PlayStation_Store_Content-Guidelines-20110202.zip
**[8]-SNC_Documentation-360.2-English.zip
**[9]-ProDG_Documentation-360.2-English.zip
**[10]-TM_Documentation-360.1-English.zip
**[11]-Tuner_Documentation-360.2-English.zip
**[12]-HowtogetthebestfromSNCPPUtoolchainforPLAYSTATION3developmentSN008-E.pdf
**[13]-Graphics_tech_information-20060926.zip
**[14]-About_GPU_Local_Stall_e.pdf
[15]-RSX-Access_Ordering_e.pdf
**[16]-RSX-Advanced_Optimization_Using_Tuner_e.ppsx
[17]-RSX-Fragment_Program_Constant_Patch_e.pdf
[18]-RSX-Fragment_Program_Overfetch_e.pdf
[19]-RSX-Fragment_Program_Txd_e.zip
[20]-RSX-Fragment_Shader_Optimization_e.pdf
[21]-RSX-Jump_To_Self_e.pdf
[22]-RSX-Memory_Access_Sync_Bug_Detection_e.pdf
[23]-RSX-Multiple_Render_Target_e.pdf
[24]-RSX-Performance_Counter_Analysis_e.zip
[25]-RSX-Texture_Mapping_Optimization_e.pdf
**[26]-RSX_Tips_e.zip
[27]-RSX-Tuning_Fragment_Pipe_e.zip
**[28]-PS3_SDKDoc-360_01-CHM-English.zip
**[29]-PS3_SDKDoc-360_01-Help2-English.zip
**[30]-PS3_SDKDoc-360_01-HTML-English.zip
**[31]-PS3_SDKDoc-360_01-Latest-English.zip
**[32]-PS3_SDKDoc-360_01-Help_VS2010-English.zip
[33]-motion_controller_extension_device_specifications_e.zip
**[34]-PS3_SDKDoc-330_01-Web_Content-English.zip
**[35]-Public-Cell_Doc-Apr2007-Japanese.zip
[36]-Cell_HW_Doc-21_Japanese.zip
**[37]-RSX-HW_Doc-16_Japanese.zip
**[38]-NP_Dev-Users_Guide_j.pdf
**[39]-SNC_Documentation-360.2-Japanese.zip
**[40]-ProDG_Documentation-360.2-Japanese.zip
**[41]-TM_Documentation-360.1-Japanese.zip
**[42]-Tuner_Documentation-360.2-Japanese.zip
**[43]-HowtogetthebestfromSNCPPUtoolchainforPLAYSTATION3developmentSN008-J.pdf
**[44]-About_GPU_Local_Stall_j.pdf
[45]-RSX-Access_Ordering_j.pdf
**[46]-RSX-Advanced_Optimization_Using_Tuner_j.ppsx
[47]-RSX-Fragment_Program_Constant_Patch_j.pdf
[48]-RSX-Fragment_Program_Overfetch_j.pdf
[49]-RSX-Fragment_Program_Txd_j.zip
[50]-RSX-Fragment_Shader_Optimization_j.pdf
[51]-RSX-Jump_To_Self_j.pdf
[52]-RSX-Memory_Access_Sync_Bug_Detection_j.pdf
[53]-RSX-Multiple_Render_Target_j.pdf
[54]-RSX-Performance_Counter_Analysis_j.zip
[55]-RSX-Texture_Mapping_Optimization_j.pdf
**[56]-RSX_Tips_j.zipx
[57]-RSX-Tuning_Fragment_Pipe_j.zip
**[58]-PS3_SDKDoc-360_01-CHM-Japanese.zip
**[59]-PS3_SDKDoc-360_01-Help2-Japanese.zip
**[60]-PS3_SDKDoc-360_01-HTML-Japanese.zip
**[61]-PS3_SDKDoc-360_01-Latest-Japanese.zip
**[62]-PS3_SDKDoc-360_01-Help_VS2010-Japanese.zipx
[63]-motion_controller_extension_device_specifications_j.zip
**[64]-PS3_SDKDoc-330_01-Web_Content-Japanese.zip
**[65]-edge_0_3_5.zip
**[66]-edge_0_4_3.zip
**[67]-edge_1_0_0.zip
**[68]-edge_1_1_0.zip
**[69]-edge_1_1_1.zip
**[70]-edge_1_2_0.zip
**[71]-PS3_Checker-300.zip
**[72]-PS3_Generator_Tools-300.zip
**[73]-AuxDicTool-100.zip
**[74]-PS3_GPAD-SDK360.1_10.0_Installer.zip
**[75]-PS3_GPAD-SDK360.1_10.0_Zip_Install.zip
**[76]-PS3_COLLADA-141_DOM-201.zip
**[77]-PS3_COLLADA_270.1.zip
**[78]-PS3_SDK-360_001.zip
**[79]-PS3_NEST-122.zip
**[80]-NP_TCM-304.zip
**[81]-SCE_Net_Parse-114.zip
**[82]-PAMF_Tools-Command_Line-510.zip
**[83]-PAMF_Tools-510.zip
**[84]-SNCPPUToolchainforPlayStation3v360.1.zip
**[85]-ProDGforPlayStation3v360.2.0.exe
**[86]-TargetManagerForPlayStation3v360.2.0.exe
**[87]-TunerforPS3v360.2.0.exe
**[88]-PS3_at3tool-3100.zip
**[89]-PS3_celptool-100.zip
**[90]-MultiStream_Tools-141.zip
**[91]-SCREAM_Tools-101.zip
**[92]-SEdit-1200.zip
**[93]-Sulpha-101.zip
**[94]-Sulpha_showcase-10.zip
**[95]-VAGconverter-1.0.zip
**[96]-PS3_VAGPreviewer-1100.zip
**[97]-PS3_AVCAP_1_3_2.zip
**[98]-BrandGuideline_E_100729L.pdf
**[99]-BrandGuideline_J_101112L.pdf
**[100]-BrandGuideline_K_100729L.pdf
**[101]-PS_Move_logo.zip
**[102]-S2S_logo.zip
**[103]-SCE_logo.zip
**[104]-Sony_logo.zip
**[105]-Trophy_Icons.zip
**[106]-DS3_NC_SCE_Asia.pdf
**[107]-DS3_NC_SCEA.pdf
**[108]-DS3_NC_SCEE.pdf
**[109]-DS3_NC_SCEJ.pdf
**[110]-PS3_NC_AC_adaptor_WW_temp_1.00.pdf
**[111]-BDRemote(CECH-ZRC1)_NC_temp_ww_20110405.pdf
**[112]-PS3_NC_Format_Category_Names_WW_temp_1.00.pdf
**[113]-PS_Eye_Recommended_Terminology_1.10.pdf
**[114]-PSMove_charging_station_temp_20100806.pdf
**[115]-PS3_motion_controller_NC_temp_20100818.pdf
**[116]-PSMove_shooting_attachment_temp_20100806.pdf
**[117]-PSN_Terminology_guide_100_e.pdf
**[118]-ps3_nc_da_3_00.pdf
**[119]-ps3_nc_de_3_00.pdf
**[120]-ps3_nc_en_3_00.pdf
**[121]-ps3_nc_fi_3_00.pdf
**[122]-ps3_nc_fr_3_00.pdf
**[123]-ps3_nc_it_3_00.pdf
**[124]-ps3_nc_ja_3_00.pdf
**[125]-ps3_nc_ko_3_00.pdf
**[126]-ps3_nc_nl_3_00.pdf
**[127]-ps3_nc_no_3_00.pdf
**[128]-ps3_nc_pl_3_00.pdf
**[129]-ps3_nc_pt-PT_3_00.pdf
**[130]-ps3_nc_ru_3_00.pdf
**[131]-ps3_nc_es_3_00.pdf
**[132]-ps3_nc_sv_3_00.pdf
**[133]-ps3_nc_zho-Hans_3_00.pdf
**[134]-ps3_nc_zho-Hant_3_00.pdf
**[135]-surround_sound_system_NC_temp_20100930.pdf
**[136]-PS3_NC_Wireless_headset_WW_temp_1.01.pdf
**[137]-PS3_NC_Wireless_keypad_WW_temp_1.01.pdf
**[138]-PSStore_Submission-Guideline_e.pdf
**[139]-PSStore_Submission-Guideline_j.pdf
**[140]-PS_Store_In-Game_Logo_v2.0.zip
**[141]-ps3testcases_forTRC36-English.doc
**[142]-ps3testcases_forTRC36-English.pdf
**[143]-ps3trc36-English.doc
**[144]-ps3trc36-English.pdf
**[145]-ps3testcases_forTRC36-Japanese.doc
**[146]-ps3testcases_forTRC36-Japanese.pdf
**[147]-ps3trc36-Japanese.doc
**[148]-ps3trc36-Japanese.pdf
**[149]-ps3trc36-Korean.doc
**[150]-ps3trc36-Korean.pdf
**[151]-ps3testcases_forTRC37-English.doc
**[152]-ps3testcases_forTRC37-English.pdf
**[153]-ps3trc37-English.doc
**[154]-ps3trc37-English.pdf
**[155]-ps3testcases_forTRC37-Japanese.doc
**[156]-ps3testcases_forTRC37-Japanese.pdf
**[157]-ps3trc37-Japanese.doc
**[158]-ps3trc37-Japanese.pdf
**[159]-PS3_SDK-360_002.zip
**[160]-PS3_Toolchain_411-Win_360_001.zip
**[161]-PS3_Toolchain_411-Win_360_002_patch.zip
**[162]-PS3_SDK_CGTUTORIAL-240_001.zip
**[163]-PS3_SDK_Codec_SampleData.zip
**[164]-PS3_SDK_PlaygroundDemo-350_001.zip
**[165]-PS3_Sample_Showcase-100.wmv
**[166]-PS3_SDK_Samples-360_001.zip
**[167]-PS3_CP_Update-360_001.zip
**[168]-PS3DECHUpdateData.360.001.zip
**[169]-PS3DECRUpdateData.360.001.zip
**[170]-PS3_SDK_Installer_Readme_e.htm
**[171]-Manifest.imf
**[172]-Manifest.imf

]]> http://blog.damox.net/?feed=rss2&p=73 10 Can you downgrade your PS3? http://blog.damox.net/?p=52 http://blog.damox.net/?p=52#comments Sun, 04 Sep 2011 09:48:53 +0000 damox http://blog.damox.net/?p=52 Continue reading →]]> I don’t know, can you?

This post will look at the different DATE-CODES that are present on the casing of a PS3 and if that DATE-CODE relates to a console version that can currently be downgraded from 3.70 to 3.55 using dospiedra’s V2 downgrade or a FAT console alternative.

DATE-CODES

The principle behind DATE-CODES is simple: the first character represent the YEAR, and the second character represents the QUARTER of that year it that console was manufactured.

DATE-CODE of ”XY” would mean the console was manufactured in the “Y” QUARTER of YEAR “X”. Simple right?

6A - Downgradable (Never Produced?)
6B - Downgradable (Never Produced?)
6C - Downgradable (Never Produced?)
6D - Downgradable
7A - Downgradable
7B - Downgradable
7C - Downgradable
7D - Downgradable
8A - Downgradable
8B - Downgradable
8C - Downgradable
8D - Downgradable
9A - Downgradable
9B - Downgradable
9C - Downgradable (Slim Introduction?)
9D - Downgradable
0A - Downgradable
0B - Downgradable
0C - Downgradable
0D - Downgradable
1A - Downgradable (Factory Firmware 3.55 and lower only!)
1B - NOT Downgradable
1C - NOT Downgradable (Not out yet?)
1D - NOT Downgradable (Not out yet?)

The Date code can be found in the following locations (depending on your console type):

PS3 FAT: Sticker on the back.
PS3 Slim (CECH2 Series): Sticker on the bottom.
PS3 Slim (CECH3 Series): Sticker on the back.

UPDATE 1: I have been told that only consoles that come with firmware 3.55 and lower from factory are the only consoles that the downgrade should be attempted with.

]]> http://blog.damox.net/?feed=rss2&p=52 12 PS3.Full.3.40.SDK.PS3-DUPLEX http://blog.damox.net/?p=38 http://blog.damox.net/?p=38#comments Fri, 02 Sep 2011 03:49:14 +0000 damox http://blog.damox.net/?p=38 Continue reading →]]> Doesn’t look “Full” to me.

The full 3.40 SDK includes the following: (DUPLEX release includes the entries indicated with a ** and bolded)


[1]-Public-Cell_Doc-Apr2007-English.zip
[2]-Cell_HW_Doc-21_English.zip
[3]-RSX-HW_Doc-15_English.zip
[4]-NP_Dev-Users_Guide_e.pdf
[5]-ProDG_Documentation-340.1-English.zip
[6]-TM_Documentation-340.1-English.zip
[7]-Tuner_Documentation-340.1-English.zip
[8]-SN-DBS_Documentation-2.0.49-English.zip
[9]-Howtogetthebestfrom...SN008-E.pdf
[10]-Graphics_tech_information-20060926.zip
[11]-About_GPU_Local_Stall_e.pdf
[12]-RSX-Access_Ordering_e.pdf
**[13]-RSX-Advanced_Optimization_Using_Tuner_e.ppsx
[14]-RSX-Fragment_Program_Constant_Patch_e.pdf
[15]-RSX-Fragment_Program_Overfetch_e.pdf
[16]-RSX-Fragment_Program_Txd_e.zip
[17]-RSX-Fragment_Shader_Optimization_e.pdf
[18]-RSX-Jump_To_Self_e.pdf
[19]-RSX-Memory_Access_Sync_Bug_Detection_e.pdf
[20]-RSX-Multiple_Render_Target_e.pdf
[21]-RSX-Performance_Counter_Analysis_e.zip
[22]-RSX-Texture_Mapping_Optimization_e.pdf
[23]-RSX_Tips_e.zip
[24]-RSX-Tuning_Fragment_Pipe_e.zip
[25]-PS3_SDKDoc-340_01-CHM-English.zip
[26]-PS3_SDKDoc-340_01-Help2-Japanese.zip
[27]-PS3_SDKDoc-340_01-HTML-English.zip
[28]-PS3_SDKDoc-340_01-Latest-English.zip
**[29]-PS3_Store_Content-Guidelines-20080728.zip
[30]-PS3_SDKDoc-330_01-Web_Content-English.zip
[31]-Public-Cell_Doc-Apr2007-Japanese.zip
[32]-Cell_HW_Doc-21_Japanese.zip
[33]-RSX-HW_Doc-15_Japanese.zip
[34]-NP_Dev-Users_Guide_j.pdf
[35]-ProDG_Documentation-340.1-Japanese.zip
[36]-TM_Documentation-340.1-Japanese.zip
[37]-Tuner_Documentation-340.1-Japanese.zip
[38]-SN-DBS_Documentation-2.0.49-Japanese.zip
[39]-Howtogetthebest...SN008-J.pdf
[40]-About_GPU_Local_Stall_j.pdf
[41]-RSX-Access_Ordering_j.pdf
**[42]-RSX-Advanced_Optimization_Using_Tuner_j.ppsx
[43]-RSX-Fragment_Program_Constant_Patch_j.pdf
[44]-RSX-Fragment_Program_Overfetch_j.pdf
[45]-RSX-Fragment_Program_Txd_j.zip
[46]-RSX-Fragment_Shader_Optimization_j.pdf
[47]-RSX-Jump_To_Self_j.pdf
[48]-RSX-Memory_Access_Sync_Bug_Detection_j.pdf
[49]-RSX-Multiple_Render_Target_j.pdf
[50]-RSX-Performance_Counter_Analysis_j.zip
[51]-RSX-Texture_Mapping_Optimization_j.pdf
[52]-RSX_Tips_j.zip
[53]-RSX-Tuning_Fragment_Pipe_j.zip
[54]-PS3_SDKDoc-340_01-CHM-Japanese.zip
[55]-PS3_SDKDoc-340_01-HTML-Japanese.zip
[56]-PS3_SDKDoc-340_01-Latest-Japanese.zip
[57]-PS3_SDKDoc-330_01-Web_Content-Japanese.zip
**[58]-edge_0_3_5.zip
**[59]-edge_0_4_3.zip
**[60]-edge_1_0_0.zip
**[61]-edge_1_1_0.zip
**[62]-edge_1_1_1.zip
**[63]-edge_1_2_0.zip
**[64]-PS3_Checker-289.zip
**[65]-PS3_Generator_Tools-289.zip
**[66]-AuxDicTool-100.zip
**[67]-PS3_GPAD-SDK340.1_10.0_Installer.zip
**[68]-PS3_GPAD-SDK340.1_10.0_Zip_Install.zip
**[69]-PS3_COLLADA-141_DOM-201.zip
**[70]-PS3_COLLADA_270.1.zip
**[71]-PS3_NEST-122.zip
**[72]-NP_TCM-303.zip
**[73]-SCE_Net_Parse-114.zip
**[74]-PAMF_Tools-Command_Line-510.zip
**[75]-PAMF_Tools-510.zip
**[76]-SNCPPUToolchainforPlayStation3v340.1.zip
**[77]-ProDGforPlayStation3v340.1.0.exe
**[78]-TargetManagerForPlayStation3v340.1.0.exe
**[79]-TunerforPS3v340.1.0.exe
**[80]-SN-DBSv2.0.49.44.exe
**[81]-PS3_at3tool-3100.zip
**[82]-PS3_celptool-100.zip
**[83]-MultiStream_Tools-141.zip
**[84]-SCREAM_Tools-101.zip
**[85]-SEdit-1200.zip
**[86]-Sulpha-101.zip
**[87]-Sulpha_showcase-10.zip
**[88]-VAGconverter-1.0.zip
**[89]-PS3_VAGPreviewer-1100.zip
**[90]-PS3_AVCAP_1_3_2.zip
[91]-BrandGuideline_E_100729L.pdf
[92]-BrandGuideline_J_100729L.pdf
**[93]-S2S_logo.zip
**[94]-SCE_logo.zip
**[95]-Sony_logo.zip
**[96]-Trophy_Icons.zip
[97]-DS3_NC_SCE_Asia.pdf
[98]-DS3_NC_SCEA.pdf
[99]-DS3_NC_SCEE.pdf
[100]-DS3_NC_SCEJ.pdf
[101]-PS3_NC_AC_adaptor_WW_temp_1.00.pdf
[102]-PS3_NC_Format_Category_Names_WW_temp_1.00.pdf
[103]-PS_Eye_Recommended_Terminology_1.10.pdf
[104]-PSMove_charging_station_temp_20100806.pdf
[105]-PS3_motion_controller_NC_temp_20100818.pdf
[106]-PSMove_shooting_attachment_temp_20100806.pdf
[107]-PSN_Terminology_guide_100_e.pdf
[108]-PS3_NC_v1.0_CS.pdf
[109]-PS3_NC_v1.0_CT.pdf
[110]-PS3_NC_v1.12_J.pdf
[111]-PS3_NC_v1.0_K.pdf
**[112]-PS3_NC_1.01_SCEA.zip
**[113]-PS3_NC_1.01_SCEE.zip
[114]-PS3_NC_1.01_SCEE_En.pdf
[115]-PS3_NC_Wireless_headset_WW_temp_1.01.pdf
[116]-PS3_NC_Wireless_keypad_WW_temp_1.01.pdf
[117]-PSStore_Submission-Guideline_e.pdf
[118]-PSStore_Submission-Guideline_j.pdf
**[119]-PS_Store_In-Game_Logo_v2.0.zip
[120]-ps3testcases_forTRC35-English.pdf
[121]-ps3trc35-English.doc
[122]-ps3trc35-English.pdf
[123]-ps3testcases_forTRC35-Japanese.pdf
[124]-ps3trc35-Japanese.doc
[125]-ps3trc35-Japanese.pdf
[126]-ps3trc35-Korean.doc
[127]-ps3trc35-Korean.pdf
[128]-ps3trc36-English.doc
[129]-ps3trc36-English.pdf
[130]-ps3trc36-Japanese.doc
[131]-ps3trc36-Japanese.pdf
**[132]-PS3_SDK-340_001.zip
**[133]-PS3_SDK-341_001.zip
**[134]-PS3_Toolchain_411-Win_340_001.zip
**[135]-PS3_SDK_CGTUTORIAL-240_001.zip
**[136]-PS3_SDK_Codec_SampleData.zip
**[137]-PS3_SDK_PlaygroundDemo-340_001.zip
**[138]-PS3_Sample_Showcase-100.wmv
**[139]-PS3_SDK_Samples-340_001.zip
**[140]-PS3_CP_Update-240_001.zip
**[141]-PS3DECHUpdateData.341.001.zip
**[142]-PS3DECRUpdateData.341.001.zip

 

]]> http://blog.damox.net/?feed=rss2&p=38 2 ‘Byte Swapping’ Your PS3 NOR Dumps http://blog.damox.net/?p=20 http://blog.damox.net/?p=20#comments Fri, 02 Sep 2011 03:36:03 +0000 damox http://blog.damox.net/?p=20 Continue reading →]]> A few people have either asked how to ByteSwap their NAND/NOR dumps or have needed to and not known how – I am going to show you ;)

You will need the following:

  • FlowRebuilder v.4.1.3.2 (.rar MD5: 39323C1A72DC745B2C0233C1DE0615C2)
  • Your NOR Dump (I will be using NOR_3.70_OFW.bin)
–Tutorial Start–
Step 1: Run FlowRebuilder v.4.1.3.2.exe
FlowRebuilder
Step 2: Under ‘Operation’ select: ‘Byte Reverse and extract a NOR dump file.
Step 3: Under ‘Select the Input Dump File’ browse to the NOR dump you want to byte swap.
Step 4: Click ‘Execute Operation’
FlowRebuilder Running
Step 5: Wait for the operation to complete – Once it has completed you should now have two files: your original NOR_3.70_OFW.bin and NOR_3.70_OFW.bin.REV – (located where your original dump is)
—
The file NOR_3.70_OFW.bin (that has NOT been byte swapped) at OFFSET:200 looks like the following (FI.I):
Non ByteSwapped Dump
OFFSET:420 will read ‘saceru_eoldare‘
The file NOR_3.70_OFW.bin.REV (that HAS been byte swapped) at OFFSET:200 looks like the following (IFI.):

Dump Byte Swapped

OFFSET:420 will read ‘asecure_loader‘
]]> http://blog.damox.net/?feed=rss2&p=20 3 Playstation 3 Downgrade (dospiedra v2) http://blog.damox.net/?p=6 http://blog.damox.net/?p=6#comments Thu, 01 Sep 2011 06:06:58 +0000 damox http://blog.damox.net/?p=6 Continue reading →]]> In this quick tutorial I will cover how to downgrade your PS3 (NOR flash type only) using dospiedra’s latest downgrade method.

You will need the following:

–Tutorial Start–
Step 1: Dump the NOR of your PS3 using the ProgSkeet Device and Software. Make sure you dump your NOR a number of times and verify that both the read is valid and that all the dumps are exactly the same.
  • Make sure you have ByteSwap checked, so we can eliminate the usage of FlowRebuilder.
  • Your dump should be exacltly 16,777,216 bytes.
  • Save the dump as NOR_3.70_OFW.bin for this guide.
ProgSkeet Flasher
  • Spansion NOR: 128KB sector, 128 sectors
  • Samsung NOR: 4KB sector, 4096 sectors
  • Macronix NOR: 128KB sector, 128 sectors
Step 2: Open NOR_3.70_OFW.bin with HxD. Make sure OFFSET 200 reads “IFI” and nothing else (otherwise you might need to go back and ByteSwap your dump)
NOR_3.70_OFW.bin open in HxDStep 3: Open the 6 patches found inside the downgrade v2 archive with HxD.
6 Patches open in HxDStep 4: Now we want to patch our NOR_3.70_OFW.bin with the 6 patches provided.

patch1: OFFSET 0C0010 LENGTH 6FFFE0
patch2: OFFSET 7C0010 LENGTH 6FFFE0
patch3: OFFSET 80000 LENGTH 20000
patch4: OFFSET A0000 LENGTH 20000
patch5: OFFSET 40000 LENGTH 20000
patch6: OFFSET 60000 LENGTH 20000

For each patch perform the following (using patch 1 as an example):

  • Open patch1 and select all (ctrl+a) and copy (ctrl+c).
  • Open NOR_3.70_OFW.bin and goto (ctrl+g) OFFSET 0C0010

HxD Goto OFFSET

  • Paste write with ctrl-b (not Paste Insert! – the file size should never change) the changes you make should be coloured red.
Red changes in HxD

Keep repeating (using the different offsets for each patch) until all 6 patches have been applied.

Step 5: Save patched NOR_3.70_OFW.bin as NOR_downgrade.bin

Step 6: Flash NOR_downgrade.bin to the PS3 using the ProgSkeet Device and Software.

Step 7: Turn on the PS3 but do not press anything. Wait 1 minute or so, and remove power from the PS3 - we need to put it into factory service mode.

Step 8: Format a FAT32 thumb-drive and place the following files on it.

  • usb:\\Lv2diag.self (Get this file from the Lv2Diag-patch-par-Jaicrab.zip archive – ‘\Lv2Diag-patch-par-Jaicrab\STEP1\Lv2diag.self’)
  • usb:\\PS3UPDAT.PUP (Rename 355checkoff.PUP to PS3UPDAT.PUP)

Step 9: Plug the thumb-drive with the files from step 8 into the right-most USB port on the PS3.

Step 10: Boot the PS3 into Factory Service Mode (see other guides on how to achieve this)

Step 11: Wait for the PS3 to power off automatically (this should take somewhere between 10-20 minutes)

Step 12: Remove the USB from the right-most USB port on the PS3.

Step 13: Power on the PS3  – you should now see the XMB.

Step 14: Shutdown the PS3 again.

Step 15: Replace the first stage Lv2diag.self with the second stage Lv2diag.self on the thumb-drive and re-plug the thumb-drive into the right-most USB port on the PS3.

  • usb:\\Lv2diag.self (Get this file from the Lv2diag_355.rar archive – ‘\\Lv2diag_355\Archivo 2\Lv2diag.self’)
  • usb:\\PS3UPDAT.PUP (Keep from before)

Step 16: Power on the PS3 - Wait for the PS3 to power off automatically (this should take somewhere between 10-20 seconds)

Step 17: Remove the USB from the right-most USB port on the PS3.

Step 18: Boot the PS3 and enjoy your 3.55 CFW No Check by dospiedra (equivalent to 3.55 CFW by kweaw)

]]> http://blog.damox.net/?feed=rss2&p=6 29