Still want to know if there is some way to copy and paste these things
Try installing PuTTY on a Windows box. In an SSH terminal window to your server, the right click of the a mouse is the equivalent of "paste" or "Ctrl+V"
Still want to know if there is some way to copy and paste these things
Try installing PuTTY on a Windows box. In an SSH terminal window to your server, the right click of the a mouse is the equivalent of "paste" or "Ctrl+V"
dmesg -w| grep btrfs
This has been running a LONG time. Well over 18 hours. It's a 1TB drive. Should it take this long?
Dmesg should Take No longer than 10s.independent of the Drive size.
Try
dmesg |head
or
dmesg
or
dmesg > /dmesg.txt
dmesg |head
[ 0.000000] microcode: microcode updated early to revision 0x27, date = 2019-02-26
[ 0.000000] Linux version 4.19.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.28-2~bpo9+
1 (2019-03-27)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-0.bpo.4-amd64 root=UUID=673ed9a3-acc8-4039-b74f-72c5ce7d80bd ro quiet
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000917ff] usable
dmesg > /dmesg.txt
Nothing
dmesg
dmesg |head
[ 0.000000] microcode: microcode updated early to revision 0x27, date = 2019-02-26
[ 0.000000] Linux version 4.19.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.19.28-2~bpo9+
1 (2019-03-27)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-0.bpo.4-amd64 root=UUID=673ed9a3-acc8-4039-b74f-72c5ce7d80bd ro quiet
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000917ff] usable
dmesg > /dmesg.txt
Nothing
dmesg
attachment
cat /var/log/syslog | grep btrfs
Nothing for this
Nothing
You won't see any screen output for this. It was redirected to the file /dmesg.txt
You won't see any screen output for this. It was redirected to the file /dmesg.txt
Ah. So the attachment I had provided - https://forum.openmediavault.o…7-dmesg-19-1208-1530-txt/ - would be the same output.
Ah. So the attachment I had provided - https://forum.openmediavault.o…7-dmesg-19-1208-1530-txt/ - would be the same output.
I don't know. How was that attachment generated?
What is sda?
doesn't support DPO or FUA
[ 3.174710] sdc: sdc1 sdc2 < sdc5 >
[ 3.178748] sd 10:0:0:0: [sdc] Attached SCSI removable disk
[ 5.364048] ata1.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0
[ 5.364130] ata1.00: irq_stat 0x40000008
[ 5.364197] ata1.00: failed command: READ FPDMA QUEUED
[ 5.364278] ata1.00: cmd 60/80:20:80:08:00/01:00:00:00:00/40 tag 4 ncq dma 196608 in
res 41/40:80:85:08:00/00:01:00:00:00/00 Emask 0x409 (media error) <F>
[ 5.364385] ata1.00: status: { DRDY ERR }
[ 5.364450] ata1.00: error: { UNC }
[ 5.386922] ata1.00: configured for UDMA/133
[ 5.386956] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 5.386963] sd 0:0:0:0: [sda] tag#4 Sense Key : Medium Error [current]
[ 5.386968] sd 0:0:0:0: [sda] tag#4 Add. Sense: Unrecovered read error - auto reallocate failed
[ 5.386974] sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 08 80 00 01 80 00
[ 5.386978] print_req_error: I/O error, dev sda, sector 2181
[ 5.387093] ata1: EH complete
[ 8.111430] ata1.00: exception Emask 0x0 SAct 0x9800 SErr 0x0 action 0x0
[ 8.111504] ata1.00: irq_stat
Alles anzeigen
And where ist the raid6 coming from?
10.865135] print_req_error: I/O error, dev sda, sector 2181
[ 10.865223] Buffer I/O error on dev sda1, logical block 133, async page read
[ 10.865334] ata1: EH complete
[ 10.952498] raid6: sse2x1 gen() 11349 MB/s
[ 11.020496] raid6: sse2x1 xor() 8954 MB/s
[ 11.088494] raid6: sse2x2 gen() 14622 MB/s
[ 11.156495] raid6: sse2x2 xor() 9803 MB/s
[ 11.224498] raid6: sse2x4 gen() 16842 MB/s
[ 11.292495] raid6: sse2x4 xor() 11777 MB/s
[ 11.360497] raid6: avx2x1 gen() 22256 MB/s
[ 11.428495] raid6: avx2x1 xor() 16776 MB/s
[ 11.496495] raid6: avx2x2 gen() 26130 MB/s
[ 11.564495] raid6: avx2x2 xor() 17858 MB/s
[ 11.632496] raid6: avx2x4 gen() 29992 MB/s
[ 11.700495] raid6: avx2x4 xor() 21329 MB/s
[ 11.700496] raid6: using algorithm avx2x4 gen() 29992 MB/s
[ 11.700496] raid6: .... xor() 21329 MB/s, rmw enabled
[ 11.700497] raid6: using avx2x2 recovery algorithm
[ 11.701013] xor: automatically using best checksumming function avx
[ 11.701343] async_tx: api initialized (async)
Alles anzeigen
What is sda?
sda is the bad disk
And where ist the raid6 coming from?
No idea. The only thing I can think of is this item in my BIOS (the O's under SATA Operation are radio buttons and the only one selected is RAID On):
SATA Operation
O - Disabled
O - ATA
O - AHCIO - RAID On
This option configures the operating mode of the integrated SATA hard drive controller.
Disabled = The SATA controllers are hidden.
ATA = SATA is configured for ATA mode.
AHCI = SATA is configured for AHCI mode.
RAID On = SATA is configured to support RAID mode.
btrfs filesystem show
Ran the command, but it didn't return anything that I could see.
Hadn't yet run:
Should I do that first?
Hello,
I was now able to have a more indepth look at your log.
Please provide the output of
and the same for the other drive that also showed errors.
Then
(sorry, I should have written this in the first place. This will show all btrfs filesystems. Otherwise, you have to specifiy one)
Post that output.
Before we restore the data from the broken drive:
You had also other drives, that were not damaged. Have you saved/backed up that data to another safe place?
To now restore your data:
That will run a while. After it has finished you can check what was restored on /mnt/restoredrive or shutdown and check the content of the drive in windows.
Post the restorelog.txt.
If this does not bring the success, we have two other options (btrfs scrub and btrfsck). But this one for sure does not change any data, so it is the safest, if properly followed.
Greetings,
Hendrik
double post
smartctl -a /dev/sda
As attachment.
I will reinstall that other drive that was less "friendly" than the one in the attachment. Then I will provide the btrfs filesystem show -d that you instructed. I did not have any drives that were good, so I'm not sure what you are referring to here.
I will get to the rest of the instructions soon.
Stay tuned ...
smartctl -a /dev/sdb
This attachment is for the 'other' drive that I had set aside that mounts but can't be read.
BTW, we did not do a copy from this drive.
btrfs filesystem show -d
btrfs filesystem show -d
Label: none uuid: c81bf277-6ded-4e03-8bce-d4b25a690e27
Total devices 1 FS bytes used 384.00KiB
devid 1 size 1.82TiB used 2.02GiB path /dev/sda1
In this case, the "other" drive was installed. Results are showing our "copied" drive from ddrescue.
btrfs filesystem show -d
And this is with the one drive that we copied from. Again, only showing our 2TB copy drive.
btrfs filesystem show -d
Label: none uuid: c81bf277-6ded-4e03-8bce-d4b25a690e27
Total devices 1 FS bytes used 384.00KiB
devid 1 size 1.82TiB used 2.02GiB path /dev/sda1
So, now on to the next steps you outlined.
Alas, I cannot find where to format a drive from the WebGUI.
***********************************************************************************
Never mind, figured it out.
**************************************************
I must be seeing cross-eyed at this point.
Properly identify the restore target (e.g. the USB drive) format it with a filesystem you can read in windows and mount it. Remember the mount point (e.g. /media/restoredrive/)
I have formatted the restore drive to btrfs and mounted it. Is the mountpoint then /dev/sdb, which is what is showing in disks?
Storage | Filesystems press Create button, select device......................
To all,
I fear I may have to backup and start over at one of the levels. My 2TB drive that I ddrescue'd to will not mount. When I attempt to mount it in the GUI, I'm watching the command line output which indicates there is a BTRFS error - bad tree block starts, failed to read chunk root, open_ctree failed. The 1TB drive I ddrescue'd to (to fool around with in Windows) won't show up in the FileSystems list, and isn't recognized in my Windows system, which probably indicates that I did not format it correctly.
So, I'm going to reformat the 1TB drive and ddrescue to that again, in the hopes that I'll get it right this time. Not sure what to do with the 2TB ddrescue'd drive at this point.
Don't do stuff that I am not asking you to, please.
You have not understood the process.
Birds-eye view:
1) we make copies of the failed drive
2) these are copies. They are not expected to be any better. But we can mess around with them
3) we try to rescue (=mess around with the copies)
Everytime you ddrescue, you stress your "about to completely fail" drive another time. Don't do that.
You were (possibly) almost there. Just had to keep following my instructions from my last post.
Greetings,
HEndrik
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!