.
>
> What I first found were instructions to create an empty file of the
> propper size, 'mkudffs file', loop mount it, copy files to it, unmount
> and burn to the BD disc.
>
>
According to the internet K3B and Brasero are both able to burn BlueRay
Data Disks. I haven't t
On Fri, 2025-01-24 at 18:23 +, Tim Woodall wrote:
> On Fri, 17 Jan 2025, Bob McGowan wrote:
>
> > Hello list,
> >
> > I've been trying to figure out how to use my BD disc writer to
> > create
> > backups of files.
> >
> > What I first found were instructions to create an empty file of the
>
On Fri, 17 Jan 2025, Bob McGowan wrote:
Hello list,
I've been trying to figure out how to use my BD disc writer to create
backups of files.
What I first found were instructions to create an empty file of the
propper size, 'mkudffs file', loop mount it, copy files to it, unmount
and burn to the
Hi,
i wrote:
> > Nearly half a life ago, my own endeavor with ISO 9660 and optical media
> > began with creating a tool which does this splitting automatically:
> >
> > http://scdbackup.webframe.org/main_eng.html
> > http://scdbackup.webframe.org/examples.html
Roy J. Tellason, Sr. wrote:
> Th
On Sunday 19 January 2025 03:37:06 am Thomas Schmitt wrote:
> Nearly half a life ago, my own endeavor with ISO 9660 and optical media
> began with creating a tool which does this splitting automatically:
>
> http://scdbackup.webframe.org/main_eng.html
> http://scdbackup.webframe.org/examples.h
On Mon, Jan 20, 2025 at 09:49:19AM +0100, Thomas Schmitt wrote:
[...]
> (Due to its purpose and the proximity to some words from the iberian
> peninsula, i would visualize it as a smiling sausage which burns at
> both ends.)
Yikes. Chorizo al infierno :-)
Cheers
--
t
signature.asc
Descriptio
On Monday, 20 January 2025 05:49:19 GMT-4 Thomas Schmitt wrote:
> Hi,
>
> Bob McGowan wrote:
> > The -options_from_file is
> > exactly what I was needing and works perfectly.
>
> Congrats.
> I'm glad that UDF was not a hard requirement.
>
> > Just one last question. How do you pronounce "xorriso"?
Hi,
Bob McGowan wrote:
> The -options_from_file is
> exactly what I was needing and works perfectly.
Congrats.
I'm glad that UDF was not a hard requirement.
> Just one last question. How do you pronounce "xorriso"? :)
Rarely. :))
Normally i only write about it. But i think of it with german
p
Hi Thomas,
On Sun, 2025-01-19 at 09:37 +0100, Thomas Schmitt wrote:
> Hi,
>
> Bob McGowan wrote:
> > One question, what I would like to see is a duplicated
> > directory/file
> > hierachy on the destination. I have lists of file names in groups
> > just
> > short of 25G, but I can't find an eas
Hi,
Bob McGowan wrote:
> One question, what I would like to see is a duplicated directory/file
> hierachy on the destination. I have lists of file names in groups just
> short of 25G, but I can't find an easy way to send the file names to
> any of the programs and have them maintain the hierarch
Hello Thomas,
On Sat, 2025-01-18 at 09:42 +0100, Thomas Schmitt wrote:
> > Hi,
> >
> > Bob McGowan wrote:
> > > > I've been trying to figure out how to use my BD disc writer to
> > > > create
> > > > backups of files.
> >
> > I do this by Rock Ridge enhanced ISO 9660 on BD-R and BD-RE media,
> >
On Sat, 2025-01-18 at 14:25 -0500, Sarunas Burdulis wrote:
> Are you trying to script/automate?
>
> If not, just use xfburn (GUI). I'm writing Bluray 25GiB M-disks using
> xfburn regularly (archiving a backups' snapshot directory on NAS).
>
> --
> Šarūnas B
Hi,
Sarunas Burdulis wrote:
> just use xfburn (GUI).
Xfburn does indeed Blu-ray by help of libburn.
But it does no UDF, because it uses libisofs for filesystem production.
Insofar the result is supposed to be similar to the results of the xorriso
runs which i proposed, but without MD5 checksums i
Are you trying to script/automate?
If not, just use xfburn (GUI). I'm writing Bluray 25GiB M-disks using
xfburn regularly (archiving a backups' snapshot directory on NAS).
--
Šarūnas Burdulis
Dartmouth Mathematics
https://math.dartmouth.edu/~sarunas
· https://useplain
Hi,
Bob McGowan wrote:
> I've been trying to figure out how to use my BD disc writer to create
> backups of files.
I do this by Rock Ridge enhanced ISO 9660 on BD-R and BD-RE media,
following this example from the man page of xorriso:
xorriso \
-abort_on FATAL \
-for_backup -disk_dev_i
On Fri, 2025-01-17 at 23:37 -0800, Bob McGowan wrote:
> Hello list,
>
> I've been trying to figure out how to use my BD disc writer to create
> backups of files.
>
> What I first found were instructions to create an empty file of the
> propper size, 'mkudffs file', loop mount it, copy files to it
Hello list,
I've been trying to figure out how to use my BD disc writer to create
backups of files.
What I first found were instructions to create an empty file of the
propper size, 'mkudffs file', loop mount it, copy files to it, unmount
and burn to the BD disc.
Doing this resulted in a BD disk
Hello folks,
Just to follow up on this thread, here's how it played out:
-- I gave up on EFI, and use just BIOS boot
-- each drive has three partitions: a space for grub-install, am mdadm
md0 /boot and a btrfs raid1c3 root partition
-- grub-install on each dev manually, and I probably need an apt
e're screwed and the
corruption may be copied to other disks, but that's already the case
with other partitions in a raid (nowadays there are consistency
checks...);
- if it has a problem that is visible enough for the md layer to
remove the disk from the array, t
Hello folks,
Thanks kindly -- and my apologies for picking this up after a while;
fell sick here...
A few questions:
-- If I have multiple drives, do I modify the script to have multiple
efi2, efi3, ..., efiX ?
-- it seems that the script above privileges /boot/efi over /boot/efi2
-- in this ca
On Fri, 20 Sep 2024, Florent Rougon wrote:
Le 20/09/2024, Tim Woodall a écrit:
Because the script will abort after the mount fails.
root@dirac:~# cat test.sh
#!/bin/bash
set -e
mount /boot/efi2
echo "do important stuff"
root@dirac:~# ./test.sh
mount: /boot/efi2: /dev/sda2 already mounted
Le 20/09/2024, Tim Woodall a écrit:
> Because the script will abort after the mount fails.
>
> root@dirac:~# cat test.sh
> #!/bin/bash
>
> set -e
>
> mount /boot/efi2
>
> echo "do important stuff"
>
> root@dirac:~# ./test.sh
> mount: /boot/efi2: /dev/sda2 already mounted on /boot/efi2.
>d
On Fri, 20 Sep 2024, Florent Rougon wrote:
Le 20/09/2024, Tim Woodall a ?crit:
Haven't looked at the script but assuming it's run set -e, then your
suggestion will fail if it's already mounted.
Why?
Because the script will abort after the mount fails.
root@dirac:~# cat test.sh
#!/bin/ba
Le 20/09/2024, Tim Woodall a écrit:
> Haven't looked at the script but assuming it's run set -e, then your
> suggestion will fail if it's already mounted.
Why?
--
Florent
On Thu, 19 Sep 2024, Florent Rougon wrote:
Hi,
Le 19/09/2024, Andy Smith a ?crit:
I don't think the answer, on Debian, has changed since I asked the
same question in 2020:
https://lists.debian.org/debian-user/2020/11/msg00455.html
There is a script at [1] to install as, e.g.,
/etc/gru
Hi,
Le 19/09/2024, Andy Smith a écrit:
> I don't think the answer, on Debian, has changed since I asked the
> same question in 2020:
>
> https://lists.debian.org/debian-user/2020/11/msg00455.html
There is a script at [1] to install as, e.g.,
/etc/grub.d/90_copy_to_boot_efi2, so that it is a
Hi,
On Wed, Sep 18, 2024 at 08:21:10PM -0400, Boyan Penkov wrote:
> So, what are folks doing these days to mirror /efi and /boot?
[ TL;DR: You already found it - have two separate EFI System
Partitions, sync one to the other manually using e.g. rsync
whenever one changes, add path
Hello folks,
New machine, new opportunity to get up to speed with the contemporary
best practices for multiple disks on UEFI.
The behavior I'd like -- and, I suspect, the behavior we'd all like --
is the machine stays bootable and data is preserved if any disk fails.
Specifically, wha
hello Andy,
thanks for the detailed answer.
Andy Smith writes:
> Hello,
>
> On Fri, Dec 29, 2023 at 06:17:07PM +0100, Felix Natter wrote:
>> Andy Smith writes:
>> > But to be absolutely sure you may wish to totally ignore md0 and
>> > its member devices during install as all their data and the
Hello,
On Fri, Dec 29, 2023 at 06:17:07PM +0100, Felix Natter wrote:
> Andy Smith writes:
> > But to be absolutely sure you may wish to totally ignore md0 and
> > its member devices during install as all their data and the
> > metadata on their member devices will still be there after
> > install
hi Steve,
thanks for the quick reply!
Steve McIntyre writes:
> fnat...@gmx.net wrote:
>>
>>I have /dev/md0 mounted at /storage which consists of two HDDs.
>>
>>Now I would like to add an SSD drive for better performance of
>>VMs. Usually, before doing this, I m
mance of
>> VMs. Usually, before doing this, I make sure that all of my disks are
>> mounted using UUID and not device names. I do not think this is
>> the case for the two member HDDs of md0 (cat /proc/mdstat).
>> Is there an easy way to fix this?
>
> What are you t
fnat...@gmx.net wrote:
>
>I have /dev/md0 mounted at /storage which consists of two HDDs.
>
>Now I would like to add an SSD drive for better performance of
>VMs. Usually, before doing this, I make sure that all of my disks are
>mounted using UUID and not device names. I do not
Hi Felix,
On Fri, Dec 29, 2023 at 04:46:10PM +0100, Felix Natter wrote:
> I have /dev/md0 mounted at /storage which consists of two HDDs.
>
> Now I would like to add an SSD drive for better performance of
> VMs. Usually, before doing this, I make sure that all of my disks are
>
hello Debian experts,
I have /dev/md0 mounted at /storage which consists of two HDDs.
Now I would like to add an SSD drive for better performance of
VMs. Usually, before doing this, I make sure that all of my disks are
mounted using UUID and not device names. I do not think this is
the case for
On 07/10/2022 15:39, Andy Smith wrote:
Yeah, it's a mess with EFI. I wrote this in November 2020:
"Redundancy for EFI System Partition: what do people do in
2020?"
https://lists.debian.org/debian-user/2020/11/msg00455.html
(worth reading replies for more authoritative answe
Hi,
On Fri, Oct 07, 2022 at 02:50:06PM +0100, Andrew Wood wrote:
> How can I ensure that the system is capable of booting from either remaining
> disk in the event of a failure?
Yeah, it's a mess with EFI. I wrote this in November 2020:
"Redundancy for EFI System Partition: what do people do
In the past when Ive had 2 disks in a RAID1 mirror Ive been able
replicated the MBR on both such that the system is capable of booting
from either in the event of a failure using the command
dpkg-reconfigure grub-pc which then allowed both disks to be selected.
I was under the impression the
On 2020-08-20 14:58, Andy Smith wrote:
... dm-integrity can now be used with LUKS (with or
without encryption) to add checksums that force a read error when
they don't match. When there is redundancy (e.g. LVM or MD) a read
can then come from a good copy and the bad copy will be repaired.
So,
On Thu, Aug 20, 2020 at 01:34:58PM -0700, David Christensen wrote:
> On 2020-08-20 08:32, rhkra...@gmail.com wrote:
> >On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
> >>Contraty to the other (very valid) points, my backups are always on
> >>a LUKS drive, no partition table. Ratio
Hello,
On Thu, Aug 20, 2020 at 05:30:20PM -0400, Dan Ritter wrote:
> David Christensen wrote:
> > Some people have mentioned md RAID. tomas has mentioned LUKS. I believe
> > both of them add checksums to the contained contents. So, bit-rot within a
> > container should be caught by the contain
David Christensen wrote:
> On 2020-08-20 08:32, rhkra...@gmail.com wrote:
> I have been pondering bit-rot mitigation on non-checksumming filesystems.
>
>
> Some people have mentioned md RAID. tomas has mentioned LUKS. I believe
> both of them add checksums to the contained contents. So, bit-r
On 2020-08-20 08:32, rhkra...@gmail.com wrote:
On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
Contraty to the other (very valid) points, my backups are always on
a LUKS drive, no partition table. Rationale is, should I lose it, the
less visible information the better. Best if i
On 2020-08-20 04:39, Thomas Schmitt wrote:
Hi,
a while ago i asked about the periodic knocking noise after each 4 seconds
of my freshly bought 4 TB HDD WD4003FRYZ. We came to the conclusion that
this was a reason to return the disk to the seller. "Click of Death" et.al.
I did and got a replacem
On Thursday, August 20, 2020 03:43:55 AM to...@tuxteam.de wrote:
> Contraty to the other (very valid) points, my backups are always on
> a LUKS drive, no partition table. Rationale is, should I lose it, the
> less visible information the better. Best if it looks like a broken
> USB stick. No partit
Thomas Schmitt wrote:
> ---
>
> So my next question to recent HDD buyers:
>
> What 4 TB HDD should i want for best reliability and no noises when idle ?
> Any recent experiences ?
Toshiba and Hitachi (owned by WD but not produc
Hi,
a while ago i asked about the periodic knocking noise after each 4 seconds
of my freshly bought 4 TB HDD WD4003FRYZ. We came to the conclusion that
this was a reason to return the disk to the seller. "Click of Death" et.al.
I did and got a replacement disk. That one knocks less loudly, more l
On Thu, 20 Aug 2020 09:43:55 +0200
wrote:
> On Wed, Aug 19, 2020 at 02:41:02PM -0700, David Christensen wrote:
> > On 2020-08-19 03:03, Urs Thuermann wrote:
> > >David Christensen writes:
> >
> > >>When using a drive as backup media, are there likely use-cases
> > >>that benefit from conf
On Wed, Aug 19, 2020 at 02:41:02PM -0700, David Christensen wrote:
> On 2020-08-19 03:03, Urs Thuermann wrote:
> >David Christensen writes:
>
> >>When using a drive as backup media, are there likely use-cases that
> >>benefit from configuring the drive with no partition, a single PV,
> >>single V
On 2020-08-19 03:03, Urs Thuermann wrote:
David Christensen writes:
When using a drive as backup media, are there likely use-cases that
benefit from configuring the drive with no partition, a single PV,
single VG, single LV, and single filesystem vs. configuring the drive
with a single partit
David Christensen writes:
> Thanks for the explanation. It seems that pvcreate(8) places an LVM
> disk label and an LVM metadata area onto disks or partitions when
> creating a PV; including a unique UUID:
>
> https://www.man7.org/linux/man-pages/man8/pvcreate.8.html
Yes, co
disks or partitions when
creating a PV; including a unique UUID:
https://www.man7.org/linux/man-pages/man8/pvcreate.8.html
When using a drive as backup media, are there likely use-cases that
benefit from configuring the drive with no partition, a single PV,
single VG, single LV, and single
Urs Thuermann writes:
> IMO the best solution is to use LVM. I use it since 2001 on most
> drives and I don't have partitions. And I prefer to use device names
> over using the *UUID or *LABEL prefixes. With LVM, device names are
> predictable /dev/mapper/- with symlinks
> /dev//.
Following u
David Christensen writes:
> AIUI the OP was mounting an (external?) drive partition for use as a
> destination for backups. Prior to upgrading to Testing, the root
> partition was /dev/sda1 (no LVM?) and the backup partition was
> /dev/sdb1 (no LVM?). After upgrading to Testing, the root partit
On 2020-08-18 11:27, Urs Thuermann wrote:
"Rick Thomas" writes:
The /dev/sdx names for devices have been unpredictable for quite a
while. Which one is sda and which sdb will depend on things like
timing -- which one gets recognized by the kernel first.
The best solution is to either use UUID
"Rick Thomas" writes:
> The /dev/sdx names for devices have been unpredictable for quite a
> while. Which one is sda and which sdb will depend on things like
> timing -- which one gets recognized by the kernel first.
>
> The best solution is to either use UUID or LABEL when you fsck
> and/or mo
Hi,
i wrote:
> > I only deem *UUID as safe,
Nicolas George wrote:
> UUID can get duplicated too. Just have somebody copy the whole block
> device with "good ol' dd".
Yes, sure. A HDD of mine got by the Debian installation 128 GPT slots of
128 bytes. So the primary GPT including "protective MBR"
e identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#
# / was on /dev/sda1 during installation
UUID=3f50ca38-20f3-4a12-880c-a1283ac6e41b / ext4
errors=remount-ro 0
Thomas Schmitt (12020-08-18):
> I only deem *UUID as safe, unless the same names on different devices
> are intented and always only one of those devices will be connected.
UUID can get duplicated too. Just have somebody copy the whole block
device with "good ol' dd".
Regards,
--
Nicolas Geor
Hi,
didier gaumet wrote:
> give a name to the underlyning [GPT] partition
Let me add the hint that a GPT partition "name" is a user defined string
(in fstab and lsblk: PARTLABEL=) whereas the partition UUIDs in GPT
get handed out by partition editors automatically as random data
(human readable a
On Mon, Aug 17, 2020, at 4:42 PM, hobie of RMN wrote:
> Hi, All -
>
> My brother has been issuing "mount /dev/sdb1" prior to backing up some
> files to a second hard disk. He lately upgraded to 'testing', and it
> appears (from result of running df) that what the system now calls
> /dev/sdb1 is w
Hello,
Apparently, it is also possible to either:
- give a name to the filesystem (use e2label to do so, the filesystem being
ext4) and mount the filesystem by using this name as a parameter of the mount
command instead of /dev/sd* or an UUID
- give a name to the underlyning partition (use par
ue identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#'
--
John Doe
rrors=remount-ro)
Here's the full output:
root@shelby:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if
On 2020-08-17 16:42, hobie of RMN wrote:
Hi, All -
My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk. He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now calls
/dev/sdb1 is what he has thought of a
Hi, All -
My brother has been issuing "mount /dev/sdb1" prior to backing up some
files to a second hard disk. He lately upgraded to 'testing', and it
appears (from result of running df) that what the system now calls
/dev/sdb1 is what he has thought of as /dev/sda1, the system '/'
partition.
Tha
On 2020-07-25 07:25, Thomas Schmitt wrote:
See below for the full output of smartctl -a.
I saved one drive that had the click of death (and died shortly
thereafter). My notes indicated it passed the manufacturer diagnostic
tests, but failed the manufacturer full erase procedure. The last S
On 2020-07-25 02:16, Thomas Schmitt wrote:
David Christensen wrote:
Click of death.
At least this is the reality which i will present to the disk vendor
while negotiating about replacement.
But personally i still have doubts that it is this particular problem.
The knocking is not "Click-clic
Hi,
i quoted smartctl:
> > 4 Start_Stop_Count0x0012 100 100 000Old_age Always -
> > 18
> > 9 Power_On_Hours 0x0012 100 100 000Old_age Always -
> > 19
> > 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always -
> >
On Sat, Jul 25, 2020 at 04:25:16PM +0200, Thomas Schmitt wrote:
> 4 Start_Stop_Count0x0012 100 100 000Old_age Always
> - 18
> 9 Power_On_Hours 0x0012 100 100 000Old_age Always
> - 19
> 12 Power_Cycle_Count 0x0032 100
> Stefan Monnier wrote:
>> I guess it's still spin-down
^
like
Sorry, my fingers didn't obey my brain,
Stefan
Hi,
Reco wrote:
> It's all other lines that are interesting here.
> I.e. 'Vendor Specific SMART Attributes with Thresholds' section.
I wanted to wait with the long list until the self-test is done.
See below for the full output of smartctl -a.
Stefan Monnier wrote:
> I guess it's still spin-dow
> It is its way of saying it's an unsupported feature and you cannot
> disable drive heads parking this way. Was worth the shot.
I guess it's still spin-down: WD drives support it but just ignore the
APM settings of "how long to wait before spin-down" and use their own
algorithm instead.
On Sat, Jul 25, 2020 at 11:16:16AM +0200, Thomas Schmitt wrote:
> Reco wrote:
> > It's simple:
> > smartctl -t long /dev/sda
>
> The short test yielded
> Num Test_DescriptionStatus Remaining LifeTime(hours)
> LBA_of_first_error
> # 1 Short offline Completed with
Hi,
rhkra...@gmail.com wrote:
> You might not have read the entire [Click_of_death] article.
Indeed. Now i need to search my old loudspeakers in order to compare
the sound file on Wikipedia with the disk's sound.
D. R. Evans wrote:
> I can say that my experience (YMMV) is that 100% of the drive
Hi.
On Fri, Jul 24, 2020 at 11:35:34PM +0200, Thomas Schmitt wrote:
> Reco wrote:
> > Have you tried to disable drive heads parking via hdparm?
>
> hdparm -J ?
> The man page says "The factory default is eight (8) seconds".
> That would be about twice as long as what i experience.
>
>
On 2020-07-24 14:35, Thomas Schmitt wrote:
Hi,
Hello. :-)
David Christensen wrote:
https://en.wikipedia.org/wiki/Click_of_death
But that's a different technology (and 20 years ago).
I have a few Zip drives on the shelf, but only rarely used them back
when. My recent "Click of death"
On Fri, 2020-07-24 at 12:06 -0700, David Christensen wrote:
> On 2020-07-24 11:49, Thomas Schmitt wrote:
> > Hi,
> >
> > i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0)
> > and
> > observe a strange behavior with a provisory Debian 10 LXDE
> > installation.
> >
> > If the drive
ou might not have read the entire article.
>
Having experienced this phenomenon multiple times on both Zip disks (!) and
hard drives, I can say that my experience (YMMV) is that 100% of the drives
that exhibit this phenomenon have failed sometime not long after the
phenomenon began -- I recently had a
On 25/7/20 4:49 am, Thomas Schmitt wrote:
Hi,
i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
observe a strange behavior with a provisory Debian 10 LXDE installation.
If the drive has power then i makes a plonking noise every 3 to 5
seconds. The plonk is louder when Deb
On Friday, July 24, 2020 05:35:34 PM Thomas Schmitt wrote:
> David Christensen wrote:
> > https://en.wikipedia.org/wiki/Click_of_death
>
> But that's a different technology (and 20 years ago).
You might not have read the entire article.
Hi,
David Christensen wrote:
> https://en.wikipedia.org/wiki/Click_of_death
But that's a different technology (and 20 years ago).
> If you cannot return the drive, I would download, install, and run
> "Data Lifeguard Diagnostic for Windows":
> https://support.wdc.com/downloads.aspx?DL#downloads
On 2020-07-24 12:14, Reco wrote:
Hi.
On Fri, Jul 24, 2020 at 08:49:42PM +0200, Thomas Schmitt wrote:
Hi,
i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
observe a strange behavior with a provisory Debian 10 LXDE installation.
If the drive has power then i makes
Hi.
On Fri, Jul 24, 2020 at 08:49:42PM +0200, Thomas Schmitt wrote:
> Hi,
>
> i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
> observe a strange behavior with a provisory Debian 10 LXDE installation.
>
> If the drive has power then i makes a plonking noise every 3
Thomas Schmitt wrote:
> If the drive has power then i makes a plonking noise every 3 to 5
> seconds. The plonk is louder when Debian runs, but can also be
> heard (and felt by direct finger contact with the disk) if only EFI
> is running. The sound is not really loud but well hearable when the
> r
On 2020-07-24 11:49, Thomas Schmitt wrote:
Hi,
i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
observe a strange behavior with a provisory Debian 10 LXDE installation.
If the drive has power then i makes a plonking noise every 3 to 5
seconds. The plonk is louder when Debi
Hi,
i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
observe a strange behavior with a provisory Debian 10 LXDE installation.
If the drive has power then i makes a plonking noise every 3 to 5
seconds. The plonk is louder when Debian runs, but can also be
heard (and felt by d
writing the
email above as far as I remember. I just didn't know how long would it
take until it is approved :)
>>
> Thanks for all this help, guys. Does anyone have any thoughts on why one
> generation of an external disk cage wouldn't require this and just spun
> down the
> See man hd-idle for the details.
>
> One could also write to debian-backports, CC: the maintainer and ask
> nicely for a backport ;)
>
Thanks for all this help, guys. Does anyone have any thoughts on why one
generation of an external disk cage wouldn't require this and just
On Ma, 01 oct 19, 15:49:57, Alex Mestiashvili wrote:
>
> You may want to try hd-idle, it is not yet available in stable, but one
> can install it from testing (it is not advisable in general, but the
> divergence between buster and testing is not that big right now)
> wget it from
> http://ftp.de.
On 9/29/19 1:30 PM, Mark Fletcher wrote:
> Since a fresh install of buster, an external USB3 hard disk cage from
> Terramaster that I own is not automatically spinning down the disks in
> it when they go unused for a time.
>
> I used a previous generation of the cage with Str
> logger "Setting spindown on disk drive: $DISK_DEV"
> sdparm --flexible -6 --set SCT=4000 $DISK_DEV
> sdparm --flexible -6 --set STANDBY=1 $DISK_DEV
I found sdparm inscrutable so far so I'm really curious how you came up
with the above incantation (`sdparm -al /dev/sdb` do
On Mon, Sep 30, 2019 at 01:41:37AM -0700, B wrote:
>
>
> On 9/29/19 4:30 AM, Mark Fletcher wrote:
> > Any thoughts on where I might look to find settings that can be tweaked
> > to make it spin down when idle?
>
>
> See sdparm and hdparm tools. hdparm is probably the wrong tool because it's
> f
On 9/29/19 4:30 AM, Mark Fletcher wrote:
Any thoughts on where I might look to find settings that can be tweaked
to make it spin down when idle?
See sdparm and hdparm tools. hdparm is probably the wrong tool because
it's for internal drives connected to IDE/ATA/SATA busses. The reason
sdp
On Fri, Sep 27, 2019 at 01:41:58PM +0100, Jonathan Dowland wrote:
> On Mon, Sep 23, 2019 at 03:11:07PM +0500, Alexander V. Makartsev wrote:
> > If I understood this right, you have two disks with data and they were
> > previously configured as RAID1 volume.
> > What make\mod
Since a fresh install of buster, an external USB3 hard disk cage from
Terramaster that I own is not automatically spinning down the disks in
it when they go unused for a time.
I used a previous generation of the cage with Stretch previously, it
spun down the disks when they were not in use
On Mon, Sep 23, 2019 at 03:11:07PM +0500, Alexander V. Makartsev wrote:
If I understood this right, you have two disks with data and they were
previously configured as RAID1 volume.
What make\model RAID-controller do you use? Because "cages" by
themselves offer only SATA\SAS ports fo
On 9/24/19 7:00 AM, David wrote:
On Tue, 24 Sep 2019 at 07:50, Mark Fletcher wrote:
On Mon, Sep 23, 2019 at 03:07:15AM -, Debian Buster wrote:
2. create the parttion exactly as it was.
system. I recognise that was only that easy to do because I knew that
the original partition arrange
On Tue, 24 Sep 2019 at 07:50, Mark Fletcher wrote:
> On Mon, Sep 23, 2019 at 03:07:15AM -, Debian Buster wrote:
> > 2. create the parttion exactly as it was.
> system. I recognise that was only that easy to do because I knew that
> the original partition arrangement was so simple. If it had
On Mon, Sep 23, 2019 at 03:07:15AM -, Debian Buster wrote:
>
> Posible Options:
> 1. if you use lilo, look for a copy of parttions table.
> 2. create the parttion exactly as it was.
I'm running GRUB not lilo -- used lilo back in the 90's but switched to
grub whenever Debian started prescribi
1 - 100 of 1235 matches
Mail list logo
