René Rebe

Your good, old-fashioned rotating hard disk storage starts to develop bad sectors?

Dec 17 10:49:47 server kernel: end_request: I/O error, dev sdb, sector 300037184

One of the most easiest, quick and dirty ways to remap them on Linux (e.g. easier than fumbling with dd if= of=)?

Double check:

hdparm –read-sector 300037184 /dev/sdb

And if it is the block and still fails:

hdparm –write-sector 300037184 /dev/sdb –yes-i-know-…

Obviously this zeros the sector and all 512 or 4096 bytes that lived at that place are gone forever, and give way for fresh zeros from a spare, remapped reserve block.

Use only when you know what you are doing, your milage may vary.

Update: If you init a fresh Linux MD RAID, you may want to increase the min speed limit to get things going into production a bit faster:

echo 100000 > /proc/sys/dev/raid/speed_limit_min

Update2: If you are running in some error correcting RAID mode (e.g. not striped RAID 0 ;-) the Linux code will apparently re-write sectors and thus already automatically trigger a remap of those sectors:

end_request: I/O error, dev sdb, sector 301373665
ata2: EH complete
raid1:md0: read error corrected (8 sectors at 301373600 on sdb1)
raid1: sdb1: redirecting sector 301373600 to another mirror

After releasing our initial PDF Re/compress we received praise by first customers and users - and one popular questions: Can you actually reduce the quality much, much more?!

Our initial Re/compress will go thru all the PDF’s objects, and re-writes them in a much more compact and compressed way and also potentially recover and fix some broken files. It would also allow to reduce compression quality and down-sample the image’s resolution.

However, some interested inquires intentionally wanted way worse, smaller, and thus faster to load files. One of the most popular reason? AutoCAD CAD drawing! Those users usually use some print to PDF driver that usually results in tens (if not hundreds) of thousands of vector segments, but also potentially many small, few pixel sized (inline, sigh) image dots from 3d renderings and such. Those would usually not compress very much in our original version. This files also actually cause popular PDF viewers, like Apple’s Preview and naturally even more so Adobe’s Acrobat to hang while it was drawing all this many page content for seconds - panning and zooming was also not a very snappy affair.

Meet Re/compres 17.11 - our first major update: A newly developed “Rasterize pages to bitmap graphics” pass will convert this huge amounts of objects to just a single, highly compressed image. Using the down-sample resolution option you can create a new compressed file, intentionally with “photocopier” like reduced quality. Particularly useful when you want to mail documents to public tenders and potential clients without them having to expose all the fine, zoomable details of the original vector file!

We hope Re/compress and all its features can help you in your daily office workflow, and if you have any other wish or inquiry just let us know, too!

Re/compress PDF.

You sometimes need to print documents, invoices, boarding passes, whatever? Using Apple’s macOS Preview.app and tired of having to choose: “Scale: 100%” to have an accurate printout instead of the often arbitrary default of: “Scale to Fit: 97%” or 98% (likely due to content on margins outside of your printer’s printable page size)?

defaults write com.apple.Preview PVImagePrintingScaleMode 0
defaults write com.apple.Preview PVImagePrintingAutoRotate 0

Yep. The famous Apple usability and attention to details ;-)

How did I survive 20 years without noticing that GDB can hex print variables simply by adding /x:


p/x var


$1 = {0×4d, 0×46, 0×50, …}

;-)!

The silly name aside (sigh), it is really ridiculous that in 2017 Apple does still not allow us to update the last Beta build to the GM (Golden Master) via a delta update, and instead forces us to download and re-install the whole OS from scratch, again.

Not only for developers this really is a total waste of time (and bandwidth). There are already hundred small design details all over macOS and iOS that are not 100%ly right in the Apple eco-system anymore, this additional annoyances really add up to a way too long list in the meantime!

Testing the Beta on my 15″ Retina MacBook Pro (Late 2013) the graphic performance (e.g. editing videos, but also just browsing the web) was quite sluggish, stability awful, and there was even screen flicker and corruption during booting (hello? - where has atomic mode setting gone? ;-)

The machine run also significantly hotter and battery life was obviously much worse. If Apple did not hot-fix this in the last weeks before the GM release this might very well be the worst macOS release I witnessed to date :-/ #peakbugs

Update: after fresh installation (sigh), even the boot graphic glitches prevail:

A post shared by RenéRebe™ (@renerebe) on Sep 25, 2017 at 2:23pm PDT

Update: even the Arstechnica mentions “bugs” 9 times, and “issues” 10 times, too. Nobody would have let Microsoft get away with this, and we would have called it the worst Windows Vista release ever, … Just saying, …

Update2: iMovie still has the same problem as the latest beta installation before the GM. On my above mentioned 15″ rMBP with 4k display connected and internal display closed iMovie even crashes straight away on start-up:

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0×0000000000000000, 0×0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
-[QCCGLRootContext minimalSharedContextForCurrentThread]: Inconsistent state
abort() called

Surprisingly iMovie starts when I open the internal display in addition to the external 4k display. What?

Sick & sad. Really sad.

Update 5/11/’17 this is still not fixed in the macOS 10.3.1 and iMovie 10.1.8 and not 4k related, also happens with an vintage 20″ Apple Cinema Display, :-/ ..! #peakbugs

Update 6/12/’17 this is still not fixed in the macOS 10.3.2

Some time ago I posted about wake on lan being hidden by a cryptic energy BIOS option. This week I was setting up a new test system and wondered what exactly the Linux ethtool:
Supports Wake-on: pumbg
letters actually meant. The man-page is help and it actually is quite simple and logical:

p Wake on PHY activity
u Wake on unicast messages
m Wake on multicast messages
b Wake on broadcast messages
a Wake on ARP
g Wake on MagicPackettm
s Enable SecureOntm password for MagicPackettm
d Disable (wake on nothing). This option clears all previous options.

YES!

/Applications/Application\ Loader.app/Contents/Frameworks\
/ITunesSoftwareService.framework/Versions/A/Support/altool –upload-app -f my.pkg -u me@email.com -p thepassword

Why does Apple tell nobody, let us fight with the UI and bug nightmare that is the Application Loader or Xcode!!! :-/ ???

PS: if you are using an older macOS version you may also need to download the new Apple Worldwide Developer Relations Intermediate Certificate:

https://developer.apple.com/support/certificates/expiration/

And if you install older Xcode versions on a newer macOS they can also overwrite the codesign tool or it’s support files you may get:

The product archive package’s signature is invalid. Ensure that it is signed with your “3rd Party Mac Developer Installer” certificate.

In which case for me it helped re-installing the /Applications/InstallOSX…app/Contents/SharedSupport/InstallESD.dmg’s Packages/BSD.pkg

Your milage may vary! :-/

Update:

Also:

/usr/bin/xcrun -sdk iphoneos PackageApplication -v “${RELEASE_BUILDDIR}/${APPLICATION_NAME}.app” -o “${BUILD_HISTORY_DIR}/${APPLICATION_NAME}.ipa” –sign “${DEVELOPER_NAME}” –embed “${PROVISONING_PROFILE}”

who knew?

arecord -f cd -d 0 -vv /dev/null

;-)!

ffmpeg -thread_queue_size 128 -f alsa -i default -f x11grab -isync -r 30 -ac 2 -s 1920×1080 -i :0.0+0,0 -vcodec libx264 -preset veryfast -pix_fmt yuv420p -acodec libmp3lame -ar 44100 -ab 192k -threads 4 -y Desktop.mp4

Update: w/ VAAPI e.g. for Intel’s QuickSync:

ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -thread_queue_size 64 -f alsa -i default -thread_queue_size 64 -f x11grab -isync -r 30 -ac 1 -s 1920×1080 -i :0.0+0,0 -vf ‘format=nv12,hwupload’ -threads 8 -aspect 16:9 -b:v 12500k -vcodec h264_vaapi -af “lowpass=f=7000″ -acodec aac -ab 192k -threads 8 ~/Desktop/`date ‘+%Y%m%d-%H%M%S’.mp4`

To process them in Linux install fuse-exfat, mount the SD with:

mount.exfat-fuse /dev/sdb1 /mnt/

and convert the properitary container to a standard one:

ffmpeg -i /mnt/PRIVATE/AVCHD/BDMV/STREAM/00001.MTS -codec copy myfile.mp4