Dumping Guides/Linux Advice - Revision history

>Tankakern at 08:56, 20 February 2026

2026-02-20T08:56:12Z

← Older revision		Revision as of 08:56, 20 February 2026
Line 1:		Line 1:
			== Exclusive access to disc drive ==
	If you're dumping via Linux, while not required, this will save you lots of time and effort, and will fix any issues you may be having with your system taking a while to let you start dumping from your drive, or not allowing you to dump altogether, on certain discs:		If you're dumping via Linux, while not required, this will save you lots of time and effort, and will fix any issues you may be having with your system taking a while to let you start dumping from your drive, or not allowing you to dump altogether, on certain discs:

Line 10:		Line 11:

	i.e. <code>./redumper --drive=/dev/sg0</code>		i.e. <code>./redumper --drive=/dev/sg0</code>

			== Getting cheap IDE->SATA adapters to work ==
			If you connect to your old IDE drive through a IDE-SATA adapter, you can end up in a situation where your CD drive looks like a hard drive in Linux. It'll look something like this in dmesg when you insert a CD (example here is IDE->SATA->USB):

			<pre>[ 8200.963837] usb-storage 6-2.3.1:1.0: USB Mass Storage device detected
			[ 8200.964252] usb-storage 6-2.3.1:1.0: Quirks match for vid 1e91 pid de2c: 900000
			[ 8200.964381] scsi host0: usb-storage 6-2.3.1:1.0
			[ 8202.007684] scsi 0:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6
			[ 8202.008911] sd 0:0:0:0: Attached scsi generic sg0 type 0
			[ 8202.010488] sd 0:0:0:0: [sda] Spinning up disk...
			[ 8203.030395] ........................ready
			[ 8229.346098] sd 0:0:0:0: [sda] 303592 2048-byte logical blocks: (622 MB/593 MiB)</pre>

			You can see it shows up as <code>/dev/sda</code> instead of <code>/dev/sr0</code>.

			If this happens, you can usually rectify it by running the command
			<code>rescan-scsi-bus.sh --forcerescan</code>
			(It's part of sg3_utils).

>HeroponRikiBestest at 22:48, 7 August 2024

2024-08-07T22:48:43Z

← Older revision		Revision as of 22:48, 7 August 2024
Line 7:		Line 7:
	This unbinds the kernel's <code>sr</code> device driver for this drive, until you reboot, unplug and replug it, or just bind it back again via echoing to <code>bind</code> instead of <code>unbind</code>		This unbinds the kernel's <code>sr</code> device driver for this drive, until you reboot, unplug and replug it, or just bind it back again via echoing to <code>bind</code> instead of <code>unbind</code>

	Because of this, <code>/dev/sr[x]</code> no longer exists, so you'll have to specify your drive via the generic SCSI device path, <code>/dev/sg[x]</code>		Because of this, <code>/dev/sr[x]</code> no longer exists for this drive, so you'll have to specify your drive via the generic SCSI device path, <code>/dev/sg[x]</code>

	i.e. <code>./redumper --drive=/dev/sg0</code>		i.e. <code>./redumper --drive=/dev/sg0</code>

>HeroponRikiBestest at 22:48, 7 August 2024

2024-08-07T22:48:29Z

← Older revision		Revision as of 22:48, 7 August 2024
Line 5:		Line 5:
	- Do <code>echo -n "0:0:0:0" > /sys/bus/scsi/drivers/sr/unbind</code> (root permissions required)		- Do <code>echo -n "0:0:0:0" > /sys/bus/scsi/drivers/sr/unbind</code> (root permissions required)

	This unbinds the kernel's <code>sr</code> device driver for this drive, until you reboot, unplug and replug it, or just bind it back again via echoing to <code>bind</code> instead of <code>~~undbind~~</code>		This unbinds the kernel's <code>sr</code> device driver for this drive, until you reboot, unplug and replug it, or just bind it back again via echoing to <code>bind</code> instead of <code>unbind</code>

			Because of this, <code>/dev/sr[x]</code> no longer exists, so you'll have to specify your drive via the generic SCSI device path, <code>/dev/sg[x]</code>

			i.e. <code>./redumper --drive=/dev/sg0</code>

>HeroponRikiBestest: Created page with "If you're dumping via Linux, while not required, this will save you lots of time and effort, and will fix any issues you may be having with your system taking a while to let you ..."

2024-08-07T22:42:51Z

Created page with "If you're dumping via Linux, while not required, this will save you lots of time and effort, and will fix any issues you may be having with your system taking a while to let you ..."

New page

If you're dumping via Linux, while not required, this will save you lots of time and effort, and will fix any issues you may be having with your system taking a while to let you start dumping from your drive, or not allowing you to dump altogether, on certain discs:

- Get your drive's device ID by checking <code>dmesg -w</code>, or by doing <code>ls /sys/bus/scsi/drivers/sr</code>. It'll look something like <code>0:0:0:0</code>

- Do <code>echo -n "0:0:0:0" > /sys/bus/scsi/drivers/sr/unbind</code> (root permissions required)

This unbinds the kernel's <code>sr</code> device driver for this drive, until you reboot, unplug and replug it, or just bind it back again via echoing to <code>bind</code> instead of <code>undbind</code>