<div dir="ltr"><div style id="__af745f8f43-e961-4b88-8424-80b67790c964__"></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 19, 2014 at 11:22 PM, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com" target="_blank">lists@colorremedies.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><br>
On Mar 19, 2014, at 9:08 PM, pgaltieri . <<a href="mailto:pgaltieri@gmail.com">pgaltieri@gmail.com</a>> wrote:<br>
<br>
><br>
><br>
> On Wed, Mar 19, 2014 at 11:12 AM, Chris Murphy <<a href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>> wrote:<br>
><br>
</div><div class="">> What do you get for<br>
> smartctl -x /dev/sda<br>
><br>
><br>
> Here's the link<br>
><br>
> <a href="https://www.amazon.com/clouddrive/share?s=K76mJvZKSG0mr5pSoDGM7k" target="_blank">https://www.amazon.com/clouddrive/share?s=K76mJvZKSG0mr5pSoDGM7k</a><br>
<br>
</div>No obvious problems there. I'm suspicious about the many device ready not ready transitions in the phy event counter.<br>
<div class="">><br>
> So I unplugged the hub after making sure no drives were mounted and rebooted. Guess what? I'm now back to the emergency mode prompt. If I boot off an older kernel I again get the emergency mode prompt. What was working fine earlier no longer works.<br>
><br>
> Here's the shutdown log<br>
><br>
> <a href="https://www.amazon.com/clouddrive/share?s=-h_XGxyZT-ws_rNy16Jr0g" target="_blank">https://www.amazon.com/clouddrive/share?s=-h_XGxyZT-ws_rNy16Jr0g</a><br>
><br>
> This system has been running Linux since December and I've never had as much trouble with it as I have had these last few days. Arggggghhhhh!!!!!<br>
<br>
</div>1.<br>
[ 18.334181] systemd[1]: boot-efi.mount mount process exited, code=exited status=0<br>
[ 18.334187] systemd[1]: boot-efi.mount changed mounting -> mounted<br>
<br>
OK so you re-enabled the mounting of /boot/efi and no longer get unknown filesystem type 'vfat' apparently.<br>
<br></blockquote><div><br><br></div><div>The latest kernel loads the fat and vfat modules.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2.<br>
<br>
Like I said before this device has major file system problems. Because it's in your fstab, and fails to mount, you are dropped to emergency shell. *Any* volume in fstab that fails to mount at boot time causes the system to behave this way. Use nofail mount option otherwise.<br>
<br>
<br></blockquote><div><br></div><div>When I run fsck on the disk it comes back clean. I think the problem may have been the entry in fstab. The entry is:<br><br></div><div>labeL=NEWDATA2 /media/NEWDATA2 ext4 defaults,nodev.noexec,nosuid,.....<br>
<br></div><div>it should be:<br><br></div><div>LABEL=NEWDATA2 /media/NEWDATA2 ext4 defaults,nodev.noexec,nosuid,.....</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
[ 19.400333] systemd[1]: Child 382 died (code=exited, status=1/FAILURE)<br>
[ 19.400335] systemd[1]: Child 382 belongs to media-NEWDATA2.mount<br>
[ 19.400340] systemd[1]: media-NEWDATA2.mount mount process exited, code=exited status=1<br>
[ 19.401392] systemd[1]: media-NEWDATA2.mount changed mounting -> failed<br>
<br>
<br></blockquote><div><br></div><div>I fixed the fstab entry and mounted it, I get:<br><br></div><div>EXT4-fs (sdb1) mounted filesystem with ordered data mode. Opts (null)<br><br></div><div>When I do <br><br></div><div>umount /media/NEWDATA2<br>
<br></div><div>I get<br><br></div><div>systemd[1]: Unit media-NEWDATA2.mount entered failed state.<br><br></div><div>It does unmount the disk<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
3.<br>
<br>
What is this watchdog?<br>
[ 54.033972] systemd[1]: Shutting down.<br>
[ 54.050617] systemd[1]: Hardware watchdog 'iTCO_wdt', version 0<br>
[ 54.052299] systemd[1]: Set hardware watchdog to 10min.<br>
[ 54.054024] watchdog watchdog0: watchdog did not stop!<br>
<div class=""><div class="h5"><br>
<br>
<br></div></div></blockquote><div><br></div><div>I have no idea. But I'm starting to suspect hardware issues with the usb ports. If I plug my usb 3.0 hub in two of the usb ports the system only sees one of the 4 drives plugged into the hub. If I plug it into a third usb port then it sees all 4 drives. Then there's the issue with the usb mouse constantly disconnecting and reconnecting.<br>
<br></div><div>The system dual boots windows 8.1 and Linux, though by default it boots to Linux. When I try the same experiment with the usb hub under Windows I see the same behaviour.<br><br></div><div>So I booted the system without any drives attached and the system came up fine. I plugged the usb hub in with 4 drives and all 4 drives were mounted. What's strange, and this does not happen on any other F19 system I have, when I right click on any of the drive icons on the desktop and select "Safely Remove Drive" the system unmounts the drive and then immediately remounts it. And 3 of these drives are not in /etc/fstab.<br>
<br></div><div>Here's the relevant lines from /var/log/messages<br><br>Mar 20 16:52:28 peglaptopnew udisksd[3362]: Cleaning up mount point /run/media/pgaltieri/OLDSYSBACKUPS2 (device 8:65 is not mounted) <== I don't understand this message<br>
Mar 20 16:52:28 peglaptopnew ntfs-3g[5276]: Unmounting /dev/sde1 (OLDSYSBACKUPS2)<br>Mar 20 16:52:28 peglaptopnew udisksd[3362]: Unmounted /dev/sde1 on behalf of uid 1000<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.569779] sd 14:0:0:0: [sde] Synchronizing SCSI cache<br>
Mar 20 16:52:29 peglaptopnew kernel: [ 659.573672] usb 3-2.1.2: USB disconnect, device number 14<br>Mar 20 16:52:29 peglaptopnew systemd-udevd[6431]: inotify_add_watch(7, /dev/sde1, 10) failed: No such file or directory<br>
Mar 20 16:52:29 peglaptopnew kernel: [ 659.893887] usb 3-2.1.2: new SuperSpeed USB device number 15 using xhci_hcd<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.906021] usb 3-2.1.2: New USB device found, idVendor=0bc2, idProduct=2312<br>
Mar 20 16:52:29 peglaptopnew kernel: [ 659.906028] usb 3-2.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.906032] usb 3-2.1.2: Product: Expansion<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.906035] usb 3-2.1.2: Manufacturer: Seagate <br>
Mar 20 16:52:29 peglaptopnew kernel: [ 659.906038] usb 3-2.1.2: SerialNumber: NA47TGJ2<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.907974] usb-storage 3-2.1.2:1.0: USB Mass Storage device detected<br>Mar 20 16:52:29 peglaptopnew kernel: [ 659.908615] scsi15 : usb-storage 3-2.1.2:1.0<br>
Mar 20 16:52:29 peglaptopnew mtp-probe: checking bus 3, device 15: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.1/3-2.1.2"<br>Mar 20 16:52:29 peglaptopnew mtp-probe: bus: 3, device: 15 was not an MTP device<br>
Mar 20 16:52:30 peglaptopnew kernel: [ 660.911256] scsi 15:0:0:0: Direct-Access Seagate Expansion 0636 PQ: 0 ANSI: 6<br>Mar 20 16:52:30 peglaptopnew kernel: [ 660.911753] sd 15:0:0:0: Attached scsi generic sg4 type 0<br>
Mar 20 16:52:30 peglaptopnew kernel: [ 660.911777] sd 15:0:0:0: [sde] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)<br>Mar 20 16:52:30 peglaptopnew kernel: [ 660.912293] sd 15:0:0:0: [sde] Write Protect is off<br>
Mar 20 16:52:30 peglaptopnew kernel: [ 660.912809] sd 15:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA<br>Mar 20 16:52:30 peglaptopnew kernel: [ 660.936653] sde: sde1<br>Mar 20 16:52:30 peglaptopnew kernel: [ 660.938592] sd 15:0:0:0: [sde] Attached SCSI disk<br>
Mar 20 16:52:31 peglaptopnew ntfs-3g[6466]: Version 2013.1.13 integrated FUSE 27<br>Mar 20 16:52:31 peglaptopnew ntfs-3g[6466]: Mounted /dev/sde1 (Read-Write, label "OLDSYSBACKUPS2", NTFS 3.1)<br>Mar 20 16:52:31 peglaptopnew ntfs-3g[6466]: Cmdline options: rw,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177,uhelper=udisks2<br>
Mar 20 16:52:31 peglaptopnew ntfs-3g[6466]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sde1,blkdev,blksize=4096<br>Mar 20 16:52:31 peglaptopnew ntfs-3g[6466]: Global ownership and permissions enforced, configuration type 1<br>
Mar 20 16:52:31 peglaptopnew udisksd[3362]: Mounted /dev/sde1 at /run/media/pgaltieri/OLDSYSBACKUPS2 on behalf of uid 1000<br><br></div><div>The above is with an NTFS drive. The following is with a EXT4 drive<br><br>Mar 20 16:59:18 peglaptopnew udisksd[3362]: Cleaning up mount point /media/NEWDATA2 (device 8:49 is not mounted)<br>
Mar 20 16:59:18 peglaptopnew udisksd[3362]: Unmounted /dev/sdd1 on behalf of uid 1000<br>Mar 20 16:59:18 peglaptopnew kernel: [ 1069.020893] sd 16:0:0:0: [sdd] Synchronizing SCSI cache<br>Mar 20 16:59:18 peglaptopnew kernel: [ 1069.023310] usb 3-2.1.1: USB disconnect, device number 16<br>
Mar 20 16:59:19 peglaptopnew kernel: [ 1069.346875] usb 3-2.1.1: new SuperSpeed USB device number 17 using xhci_hcd<br>Mar 20 16:59:19 peglaptopnew kernel: [ 1069.358507] usb 3-2.1.1: New USB device found, idVendor=0bc2, idProduct=a013<br>
Mar 20 16:59:19 peglaptopnew kernel: [ 1069.358514] usb 3-2.1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1<br>Mar 20 16:59:19 peglaptopnew kernel: [ 1069.358518] usb 3-2.1.1: Product: Backup+ BL<br>Mar 20 16:59:19 peglaptopnew kernel: [ 1069.358521] usb 3-2.1.1: Manufacturer: Seagate<br>
Mar 20 16:59:19 peglaptopnew kernel: [ 1069.358524] usb 3-2.1.1: SerialNumber: NA51YTYZ<br>Mar 20 16:59:19 peglaptopnew kernel: [ 1069.359879] usb-storage 3-2.1.1:1.0: USB Mass Storage device detected<br>Mar 20 16:59:19 peglaptopnew kernel: [ 1069.359925] scsi17 : usb-storage 3-2.1.1:1.0<br>
Mar 20 16:59:19 peglaptopnew mtp-probe: checking bus 3, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2.1/3-2.1.1"<br>Mar 20 16:59:19 peglaptopnew mtp-probe: bus: 3, device: 17 was not an MTP device<br>
Mar 20 16:59:20 peglaptopnew kernel: [ 1070.362970] scsi 17:0:0:0: Direct-Access Seagate Backup+ BL 0409 PQ: 0 ANSI: 6<br>Mar 20 16:59:20 peglaptopnew kernel: [ 1070.363368] sd 17:0:0:0: [sdd] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)<br>
Mar 20 16:59:20 peglaptopnew kernel: [ 1070.363433] sd 17:0:0:0: Attached scsi generic sg3 type 0<br>Mar 20 16:59:20 peglaptopnew kernel: [ 1070.363617] sd 17:0:0:0: [sdd] Write Protect is off<br>Mar 20 16:59:20 peglaptopnew kernel: [ 1070.363874] sd 17:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA<br>
Mar 20 16:59:20 peglaptopnew kernel: [ 1070.397880] sdd: sdd1<br>Mar 20 16:59:20 peglaptopnew kernel: [ 1070.398893] sd 17:0:0:0: [sdd] Attached SCSI disk<br>Mar 20 16:59:21 peglaptopnew kernel: [ 1071.146659] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)<br>
Mar 20 16:59:21 peglaptopnew udisksd[3362]: Mounted /dev/sdd1 (system) at /media/NEWDATA2 on behalf of uid 1000<br><br></div><div>With the behaviour the way it is, there is no clean way to unmount these drives. <br><br></div>
<div>Now on my other F19 system I tried the same test, but instead of saying "Safely Remove Drive" it says "Unmount" and in this case it unmounts it and does not remount, here's the relevant lines from /var/log/messages. I was prompted for authentication when I unmounted it.<br>
<br>Mar 20 17:01:48 jackstraw dbus-daemon[637]: dbus[637]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'<br>Mar 20 17:01:48 jackstraw dbus[637]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'<br>
Mar 20 17:01:48 jackstraw systemd[1]: Starting Fingerprint Authentication Daemon...<br>Mar 20 17:01:48 jackstraw dbus-daemon[637]: dbus[637]: [system] Successfully activated service 'net.reactivated.Fprint'<br>Mar 20 17:01:48 jackstraw dbus[637]: [system] Successfully activated service 'net.reactivated.Fprint'<br>
Mar 20 17:01:48 jackstraw systemd[1]: Started Fingerprint Authentication Daemon.<br>Mar 20 17:01:48 jackstraw fprintd[27963]: Launching FprintObject<br>Mar 20 17:01:48 jackstraw fprintd[27963]: ** Message: D-Bus service launched with name: net.reactivated.Fprint<br>
Mar 20 17:01:48 jackstraw fprintd[27963]: ** Message: entering main loop<br>Mar 20 17:01:57 jackstraw udisksd[6600]: Unmounted /dev/sdc1 on behalf of uid 1000<br><br></div><div>So how does Linux decide if a drive can be safely removed versus unmounted?<br>
<br></div><div>Again Chris thank you very much for your help.<br><br></div><div>Paolo<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5">
<br>
<br>
Chris Murphy<br>
<br>
--<br>
users mailing list<br>
<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a><br>
To unsubscribe or change subscription options:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/users" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/users</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Mailing_list_guidelines" target="_blank">http://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
Have a question? Ask away: <a href="http://ask.fedoraproject.org" target="_blank">http://ask.fedoraproject.org</a><br>
</div></div></blockquote></div><br></div></div>