You are not logged in.
- Topics: Active | Unanswered
#1 2018-06-17 22:41:57
- probackup-nl
- Member
- From: Delft
- Registered: 2017-11-15
- Posts: 83
- Website
[Solved] Boot from stick: After pacman -Syu; reboot stops at rootfs
This Arch boots in UEFI from USB stick. There are 3 partitions on stick VFAT, and 2 times BTRFS.
pacman -Syu installed:
Packages (7) cryptsetup-2.0.3-2 gnupg-2.2.8-1 iproute2-4.17.0-1 json-c-0.13.1-1 libsystemd-238.133-2 systemd-238.133-2 systemd-sysvcompat-238.133-2
After that, the next reboot hangs at rootfs.
Kernel: 4.16.13-2
# parted -l /dev/sdb
Warning: Error fsyncing/closing /dev/sdd: Input/output error
Retry/Ignore? I
Model: Samsung Flash Drive FIT (scsi)
Disk /dev/sdd: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 1078MB 1074MB EFIboot boot, esp
2 1078MB 22.0GB 21.0GB root
3 22.0GB 32.0GB 9966MB homeDmesg shows:
...
scsi 0:0:0:0: Direct-Access Samsung Flash Drive FIT 1100 PQ: 0 ANSI: 6
sd 0:0:0:0: [sda] 62652416 512-byte logical blocks: (32.1 GB/29.9 GiB)
...
usb 2-1: Disable of device-initiated U1 failed.
usb 2-1: Disable of device-initiated U2 failed.
usb 2-1: USB disconnect, device number 2.
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 00 02 00 00 02 00 00
print_req_error: I/O error, dev sda, sector: 512
sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Buffer I/O error on dev sda, logical block 64, async page read
...This U1..U2 failed repeats five times.
Other sectors boot can't read: 8256, 8240, 8320, 8208.
Updates:
1.) plugging the USB stick into another computer and checking it with a computer program to recover data (SpinRite 6.0; level 2) returns 0 bad blocks.
2.) trying to mount the VFAT partition when running 4.16.13-2-ARCH from another bootable medium returns "mount: /mnt: special device /dev/sda1 does not exist."
3.)
# dd if=/dev/sda of=mbr.bin bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512B) copied, 0.001974 seconds, 253.3KB/s
/mnt # hexdump -C mbr.bin
00000000 18 fc 8c 78 54 ec 51 83 56 a8 65 68 81 8f b7 8e |...xT.Q.V.eh....|
00000010 6f 12 cc 52 8f 4c d6 ab 09 f9 16 91 43 5e a3 e8 |o..R.L......C^..|
00000020 72 1b e4 77 28 c7 48 fe 27 ff 97 9a 69 40 16 67 |r..w(.H.'...i@.g|
00000030 5c be e2 d6 ca 25 8e 3c 32 90 85 14 3c 85 d3 c1 |\....%.<2...<...|
00000040 04 60 fa 57 6e 55 77 58 ea c2 be 1f 33 95 ab 29 |.`.WnUwX....3..)|
00000050 0f 51 a0 6f da 00 b4 86 51 00 00 00 00 00 00 00 |.Q.o....Q.......|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff bb 03 00 00 |................|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
000002004. after running parted -l and ignoring the read error, corrupt device /dev/sda is renamed to /dev/sdc according to lsblk utility
5. ddrescue seems to copy fine:
# ddrescue -f -n /dev/sda /dev/sdb rescue.log
GNU ddrescue 1.23
Press Ctrl-C to interrupt
ipos: 32077 MB, non-trimmed: 0 B, current rate: 20643 kB/s
opos: 32077 MB, non-scraped: 0 B, average rate: 12893 kB/s
non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
rescued: 32078 MB, bad areas: 0, run time: 41m 27s
pct rescued: 100.00%, read errors: 0, remaining time: n/a
time since last successful read: n/a
Finished
ddrescue -f -n /dev/sda /dev/sdb rescue.log 4.04s user 141.74s system 5% cpu 41:48.91 totalAny suggestions how to fix this (corrupted sector 512) error?
Just copy the latest backup files over the corrupted VFAT Efiboot files?
Or is there more What is necessary to fix the corrupted sector 512?
ls -la /mntc2/Backups.backupdb/d2/Latest/boot
drwxr-xr-x 1 root 0 216 Jan 1 1970 .
drwxr-xr-x 1 root 0 166 Mar 12 21:26 ..
drwxr-xr-x 1 root 0 22 Mar 17 2017 EFI
-rwxr-xr-x 1 root 0 36687194 Jun 11 16:20 initramfs-linux-fallback.img
-rwxr-xr-x 1 root 0 6771101 Jun 11 16:19 initramfs-linux-tiny.img
-rwxr-xr-x 1 root 0 12701799 Jun 11 16:20 initramfs-linux.img
-rwxr-xr-x 1 root 0 1670656 May 7 21:11 intel-ucode.img
drwxr-xr-x 1 root 0 36 Mar 17 2017 loader
-rwxr-xr-x 1 root 0 5240688 Jun 1 18:45 vmlinuz-linuxLast edited by probackup-nl (2018-06-18 20:12:58)
Offline
#2 2018-06-18 10:09:31
- probackup-nl
- Member
- From: Delft
- Registered: 2017-11-15
- Posts: 83
- Website
Re: [Solved] Boot from stick: After pacman -Syu; reboot stops at rootfs
This seems to be a hardware failure. The new Samsung Slim Fit 32GB USB flash drive (8806086790833; MUF-32BB/EU) also runs at a much lower temperature in the same USB 3.0 slot. ddrescue did fix the issue; and possibly dd would also have fixed the issue because ddrescue did not detect any errors.
Strange is that a destructive badblocks run results in errors for the first run, and no errors for the second and third run.
Will ddrescue the new stick back to the faulty one, and see how this progresses...
Re-writing goes 50% quicker:
ipos: 32077 MB, non-trimmed: 0 B, current rate: 37683 kB/s
opos: 32077 MB, non-scraped: 0 B, average rate: 18021 kB/s
non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s
rescued: 32078 MB, bad areas: 0, run time: 29m 39s
pct rescued: 100.00%, read errors: 0, remaining time: n/aLast edited by probackup-nl (2018-06-18 21:57:51)
Offline
#3 2018-06-18 17:02:56
- SealsRock12
- Member
- Registered: 2018-04-03
- Posts: 83
Re: [Solved] Boot from stick: After pacman -Syu; reboot stops at rootfs
Please mark your post as solved since you fixed the issue.
-- SealsRock12
Offline
#4 2018-06-19 10:10:37
- probackup-nl
- Member
- From: Delft
- Registered: 2017-11-15
- Posts: 83
- Website
Re: [Solved] Boot from stick: After pacman -Syu; reboot stops at rootfs
and see how this progresses...
The I/O errors are back within 12 hours.
Offline