Are there any other steps I can take? btrfs is suggested as ideal for backups, but it is largely incompatible with any other filesystem, and
it is said to be overkill for a single workstation. In any case, that
is a question that arises only if I have to buy a new drive.
I have been saving my backups to an XFS partition on an external Seagate drive. I tried to do it with Ext4, but had too many failures.
Doug Laidlaw escreveu:
I have been saving my backups to an XFS partition on an external Seagate
drive. I tried to do it with Ext4, but had too many failures.
This does not make sense in my head. Use a different file system tool to repair your XFS partition.
Doug Laidlaw escreveu:
Are there any other steps I can take? btrfs is suggested as ideal for
backups, but it is largely incompatible with any other filesystem, and
it is said to be overkill for a single workstation. In any case, that
is a question that arises only if I have to buy a new drive.
External discs are fragile devices. I've heard from several people
complaints about it. One of my external discs stopped working suddenly.
I was able to recover some data using https://www.cgsecurity.org/wiki/testdisk
I have been saving my backups to an XFS partition on an external Seagate drive. I tried to do it with Ext4, but had too many failures.
For the past month or so, we have been experiencing very severe storms,
some with lightning. After the last one, my external disk became inaccessible. Looking around the Web, I find that this was a regular occurrence with CentOS 7, whose default filesystem was XFS. Usually, running xfs_repair is all that is needed, but this time, no primary or secondary superblocks can be found, and xfs_repair gives up. The
computer does not now recognize the device.
Are there any other steps I can take? btrfs is suggested as ideal for backups, but it is largely incompatible with any other filesystem, and
it is said to be overkill for a single workstation. In any case, that
is a question that arises only if I have to buy a new drive.
I have been saving my backups to an XFS partition on an external Seagate drive. I tried to do it with Ext4, but had too many failures.
For the past month or so, we have been experiencing very severe storms,
some with lightning. After the last one, my external disk became inaccessible. Looking around the Web, I find that this was a regular occurrence with CentOS 7, whose default filesystem was XFS. Usually, running xfs_repair is all that is needed, but this time, no primary or secondary superblocks can be found, and xfs_repair gives up. The
computer does not now recognize the device.
Are there any other steps I can take? btrfs is suggested as ideal for backups, but it is largely incompatible with any other filesystem, and
it is said to be overkill for a single workstation. In any case, that
is a question that arises only if I have to buy a new drive.
On 11/1/22 00:35, Gilberto F da Silva wrote:
Doug Laidlaw escreveu:I need to rephrase that. My initial filesystem for this partition was Ext4. Then I switched to XFS. fsck cannot handle XFS, although it is suggested that running fsck on it on boot-up is useful. XFS has is own tool, xfs_repair, but as its very name suggests, it is a tool for
I have been saving my backups to an XFS partition on an external Seagate >>> drive. I tried to do it with Ext4, but had too many failures.
This does not make sense in my head. Use a different file system tool to
repair your XFS partition.
repairs, not for ordinary checks on boot-up. I have used it in the
past, but this time, the damage was too great.
btrfs is suggested as ideal for backups, but it is largely
incompatible with any other filesystem [...
...] and it is said to be overkill for a single workstation.
Regarding the reliability of external disks.
Every use GSmartControl?
I used to determine the age and reliability of internal and External
disks. My external disks are much more reliable than the old disks
(all now replaced but one)on my used machines. And I had no problems
until after the middle of November 2021 with my backups via Timeshift.
I don't know if Mageia has this valuable tool or not.
A very few of my failures were hardware-related, heads crashing, bad
cable, lightning, etc. But the vast majority of my failures were my own
damn fault, caused by me doing something stupid when I knew better.
I have been saving my backups to an XFS partition on an external Seagate drive. I tried to do it with Ext4, but had too many failures.
On Mon, 10 Jan 2022 05:43:59 -0500, Doug Laidlaw
<laidlaws@hotkey.net.au> wrote:
I have been saving my backups to an XFS partition on an external Seagate
drive. I tried to do it with Ext4, but had too many failures.
The biggest problem I've seen in the past with external drives is using an enclosure that isn't well ventilated, causing the electronics to over heat, which will result in problems.
Regards, Dave Hodgins
I'm seeing that with external NVME enclosures. So I only plug those in
when needed, otherwise they get too frickin' hot.
On Mon, 10 Jan 2022 19:34:37 -0500, red floyd <no.spam.here@its.invalid> wrote:
I'm seeing that with external NVME enclosures. So I only plug those in
when needed, otherwise they get too frickin' hot.
It happens with spinning rust drives too, if they are left plugged into power for
too long.
Regards, Dave Hodgins
On 11/1/22 12:27, David W. Hodgins wrote:
On Mon, 10 Jan 2022 19:34:37 -0500, red floyd
<no.spam.here@its.invalid> wrote:
I'm seeing that with external NVME enclosures. So I only plug those in >>> when needed, otherwise they get too frickin' hot.
It happens with spinning rust drives too, if they are left plugged
into power for
too long.
Regards, Dave Hodgins
Good to see you are still around, Bits. I opted for a "WD Blue"
solid-state drive. Now I am in the usual vicious circle: the device
needs to be initialized to become visible, and it is not visible, so initialization is impossible. There is a tutorial on YouTube for this
very device, but it assumes that the drive can be found.
I hadn't heard of GsmartControl, but my mobo has SMART available.
Good to see you are still around, Bits. I opted for a "WD Blue"
solid-state drive. Now I am in the usual vicious circle: the device
needs to be initialized to become visible, and it is not visible, so initialization is impossible.
On 12/1/22 01:40, Doug Laidlaw wrote:
On 11/1/22 12:27, David W. Hodgins wrote:
On Mon, 10 Jan 2022 19:34:37 -0500, red floyd
<no.spam.here@its.invalid> wrote:
I'm seeing that with external NVME enclosures. So I only plug those in >>>> when needed, otherwise they get too frickin' hot.
It happens with spinning rust drives too, if they are left plugged
into power for
too long.
Regards, Dave Hodgins
Good to see you are still around, Bits. I opted for a "WD Blue"
solid-state drive. Now I am in the usual vicious circle: the device
needs to be initialized to become visible, and it is not visible, so
initialization is impossible. There is a tutorial on YouTube for this
very device, but it assumes that the drive can be found.
I hadn't heard of GsmartControl, but my mobo has SMART available.
GsmartControl is in the repos, but it didn't seem to help.
If it were me I would get/burn/load the latest systemrescue-8.07-amd64.iso Click gparted in the bottom tray icom and see if gparted can create a disk partition table, a partition and format it.
On 12/1/22 02:33, Bit Twister wrote:
If it were me I would get/burn/load the latest systemrescue-8.07-amd64.iso >> Click gparted in the bottom tray icom and see if gparted can create a disk >> partition table, a partition and format it.
Did that. I have a recent copy of system rescue. Also tried the one for Mageia. It can't find a drive either. I was thinking that once I have
a partition table, I would be set, but I can't get that far, even.
I still have Rescatux, but it seems to be pretty useless. Years ago, I
had a rescue disk with all the manufacturer's setup tools, but no
longer. Checking the cables next. A 2.5 inch CD is available for
laptops, but solid state makes no noise, and has no indicator light. A different SATA data cable that used to run a failed CD, made no difference.
Not sure what the sata cable is for for a solid state disk. They usually mount on the motherboard. Is this an external drive coming in through a
usb port?
On 12/1/22 02:33, Bit Twister wrote:
If it were me I would get/burn/load the latest systemrescue-8.07-amd64.iso >> Click gparted in the bottom tray icom and see if gparted can create a disk >> partition table, a partition and format it.
Did that. I have a recent copy of system rescue. Also tried the one for Mageia. It can't find a drive either. I was thinking that once I have
a partition table, I would be set, but I can't get that far, even.
I still have Rescatux, but it seems to be pretty useless. Years ago, I
had a rescue disk with all the manufacturer's setup tools, but no
longer. Checking the cables next. A 2.5 inch CD is available for
laptops, but solid state makes no noise, and has no indicator light. A different SATA data cable that used to run a failed CD, made no difference.
On 2022-01-12, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:
I still have Rescatux, but it seems to be pretty useless. Years ago, I
had a rescue disk with all the manufacturer's setup tools, but no
longer. Checking the cables next. A 2.5 inch CD is available for
laptops, but solid state makes no noise, and has no indicator light. A
different SATA data cable that used to run a failed CD, made no difference.
Not sure what the sata cable is for for a solid state disk. They usually mount on the motherboard. Is this an external drive coming in through a
usb port?
The other thing is, as suggested, you might just have a dud drive.
If the system does not recognize the disk, not even any entry under /dev/sd... or /dev/nvme.... then you have either installed it
incorrectly or you have a dead drive.
I probably missed it but what is the model and vendor name of the device?
I want to look at the user manual.
as root check for it with
hwinfo --short > hwinfo.short
and hwinfo > hwinfo.long
and look through the hwinfo,short and hwinfo,long files.
On 12/1/22 20:01, Bit Twister wrote:
I probably missed it but what is the model and vendor name of the device?It is a brand new Western Digital "WD Blue" series, using SATA
I want to look at the user manual.
as root check for it with
hwinfo --short > hwinfo.short
and hwinfo > hwinfo.long
and look through the hwinfo,short and hwinfo,long files.
connections. The current series seems to be "WD Purple." While it was connected, the Journal showed SATA errors, probably because it could not
be recognized. These stopped as soon as I unlinked the drive.
"Jan 13 11:39:45 dougshost.douglaidlaw.net kernel: ata4: SATA link down (SStatus 1 SControl 300)"
(A guy on a forum with the same issue was told to swap his cables around
-- on a laptop! I had already tried that.)
Quick google search on SStatus 1 SControl 300
says to swap cables to working drive to prove not a cable/wiring problem
then there is this link.
https://forum.armbian.com/topic/16030-ata1-sata-link-down-sstatus-0-scontrol-300/
On 13/1/22 13:30, Bit Twister wrote:
Quick google search on SStatus 1 SControl 300That was one of the first things I tried.
says to swap cables to working drive to prove not a cable/wiring problem
then there is this link.
https://forum.armbian.com/topic/16030-ata1-sata-link-down-sstatus-0-scontrol-300/
I can now see the Seagate drive in Windows. To keep Win 10 working, I
have installed a maintenance tool from IoBIT called "Advanced System Care." It has a full quiver of apps. It called a program called Disk Doctor,which blanked the disk and handed back an empty drive. Linux
still can't see it, but I can now get it working again. The backup data will change with time, and I can download the contents of the other two partitions again. But I am not counting my chickens, just yet.
Thanks everybody for your help.
I've seen the time, just recently in fact, where a drive wasn't
recognized by Mageia if hot-plugged while the system was running, but
was if the system was booted with the drive connected.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 60:37:31 |
| Calls: | 6,654 |
| Calls today: | 6 |
| Files: | 12,200 |
| Messages: | 5,331,394 |